Medical information management method, system and equipment
By encoding and processing the patient's medical information and setting up the review permissions based on the permissions of medical staff, the problem of being deceived caused by patient information leakage is solved, and information protection and risk reduction is achieved.
Patent Information
- Application Number
- CN202411248800.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2025-02-14
AI Technical Summary
The prior art is difficult to effectively prevent patients and their families from being deceived due to the leakage of medical information, especially in the case of severe patients.
By encoding and processing the patient's medical information and setting their permissions to access patient information according to the responsibilities and authority of different medical staff, we ensure that medical staff can fully review the patient's condition information but hide the contact information. The permissions of auxiliary accounts do not include specific details The condition may hide some of the condition.
The protection of patient information is achieved, and the entire information is leaked is avoided, thus reducing the way criminals contact patients and their families, and reducing the risk of being deceived.
Smart Images

Figure CN119442214A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of information management technology, and in particular to a medical information management method, system and device. Background Art
[0002] A hospital is a medical institution that provides necessary medical examinations, treatments, nursing care, consultation services, rehabilitation equipment, and transportation services for patients in accordance with laws, regulations, and industry standards, with the primary purpose of saving lives and healing the wounded. Therefore, visiting a hospital for diagnosis and treatment is the primary path to recovery.
[0003] When a patient visits a hospital for treatment, the target treatment information will record the patient's identity information, contact information, basic medical information, etc. As the treatment process progresses, the patient's medical information will be continuously updated. When the patient's target treatment information is leaked, it is very likely to provide convenience to criminals and bring risks of fraud to patients and their families: for example, criminals pretend to be medical staff, or falsely claim to have special medicines, etc., taking advantage of the patients' and their families' desire for a quick recovery and defrauding them. In related technologies, hospitals usually post warning signs in hospital corridors, wards, and other places to prevent patients and their families from being deceived. However, simple signs cannot significantly increase the vigilance of patients and their families, especially for seriously ill patients. If their condition does not improve, they are easily deceived by fraudulent calls.
[0004] Therefore, how to prevent patients and their families from being deceived has become a technical problem that needs to be solved urgently in the existing technology. Summary of the Invention
[0005] In view of this, the purpose of the present invention is to provide a medical information management method, system and device to overcome the current problem of patient information leakage causing patients and their families to be deceived.
[0006] To achieve the above objectives, the present invention adopts the following technical solutions:
[0007] In one aspect, a medical information management method includes:
[0008] Obtaining the patient's medical information and processing the medical information according to a preset format processing rule to obtain target medical information, wherein the medical information includes the patient's personal information and registration information;
[0009] When the target medical information is a first standard code set, the outpatient doctor account in the registration information is configured to have access rights to the patient's target medical information excluding contact information; the outpatient doctor auxiliary account is configured to have access rights to the patient's target medical information excluding detailed medical conditions, wherein the detailed medical conditions are set by the outpatient doctor or automatically set according to the training model; according to the treatment plan of the outpatient treatment, the target medical information of the corresponding patient is updated; wherein the first standard code set requires outpatient treatment;
[0010] When the target medical information is the second standard code set, the resident doctor information and nurse information associated with the patient are determined, and the resident doctor account's permission to view the patient's target medical information is configured to not include contact information, and the nurse account's permission to view the patient's target medical information is configured to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is the target medical information that hides part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same; wherein, the second standard code set represents hospitalization.
[0011] Optionally, processing the medical information according to a preset format processing rule includes:
[0012] According to a preset table of correspondences between medical information and codes, and a preset position relationship, the medical information is encoded into a corresponding code set; wherein each code in the code set represents a setting object of a corresponding code position, and the preset position relationship is a position where each medical information is placed; encoding the medical information into a corresponding code set according to the preset table of correspondences between medical information and codes, and the preset position relationship, includes:
[0013] In the preset table of correspondence between medical information and codes, the code of each medical information item is determined, and the code is placed at a preset position according to the preset position relationship, and the placed codes are combined into a code set, which is used as the code set;
[0014] It also includes: adjusting the preset position relationship according to the position relationship adjustment instruction.
[0015] Optionally, processing the medical information according to a preset format processing rule includes:
[0016] Encoding the medical information through an encoding algorithm and generating multiple decoding keys; each of the decoding keys has different decoding permissions; wherein, encoding the medical information through the encoding algorithm includes: creating a set coding table for each decryption requirement based on the decryption permission requirement of each account; for any set coding table, determining the data bits and segmentation code of the set coding table, mapping the medical information to the set coding table, segmenting the medical information through the segmentation code of the set coding table, and determining the decoding key of the set coding table;
[0017] The method also includes: sending the decoding key to the corresponding account according to the decryption authority requirement, so that different accounts can decode the encoded medical information according to the received decoding key and remap it to the original medical information to obtain the medical information authorized by the account.
[0018] Optionally, it also includes:
[0019] In response to a target patient's target information search instruction, obtain a keyword in the target information search instruction and determine the user's target medical information access rights; search for synonyms of the keyword in a preset database and determine whether the user has access rights to the keyword or synonym; if the user does not have access rights to the keyword or synonym, record the number of non-authorized data searches by the user;
[0020] Within a preset time period, when the number of times the non-authorized data is viewed exceeds a threshold, an abnormal reminder is sent to the management account.
[0021] Optionally, the method further includes: when the user's account is abnormal, prohibiting the user from logging in and sending a password reset instruction to the user; or
[0022] When the user's account is abnormal, the user is prohibited from logging in for a preset period of time and a password reset instruction is sent to the user;
[0023] The method further includes: configuring the resident physician assistant account's access rights to the patient's target medical information to include the patient's contact information.
[0024] Optionally, before determining the resident doctor information and nurse information associated with the patient, the method further includes:
[0025] In response to a resident doctor configuration instruction, associating a target resident doctor with a patient; wherein the resident doctor configuration instruction carries information of the target resident doctor;
[0026] According to the bed information and nurse scheduling, target bed information and target nurse information are configured for the patient and associated.
[0027] Optionally, configure the nurse account's permission to access the patient's target medical information as the nurse's target medical information permission range, including:
[0028] According to each nurse's job responsibilities, configure the corresponding nurse account to have access to the patient's target medical information.
[0029] Optionally, the personal information is stored in a first storage area, and other target medical information is stored in a second storage area; the method further includes:
[0030] When the user's account is abnormal, a dummy data folder is constructed in the storage area where the non-authorization data is located, dummy data is generated according to the stored data in the storage area where the non-authorization data is located, and the dummy data is stored in the dummy data folder;
[0031] The pseudo data is sent to the user, and an abnormality reminder is sent according to the associated contact information of the user.
[0032] In yet another aspect, a medical information management system comprises:
[0033] An acquisition module is used to acquire the patient's medical information and process the target medical information according to a preset format processing rule to obtain the target medical information, wherein the target medical information includes the patient's personal information and registration information;
[0034] a configuration module configured to configure, when the target medical information is a first standard code set, the outpatient doctor account in the registration information to have access to the patient's target medical information so as not to include contact information; configure the outpatient doctor auxiliary account to have access to the patient's target medical information so as not to include detailed medical conditions, wherein the detailed medical conditions are set by the outpatient doctor or automatically set according to a training model; and update the target medical information corresponding to the patient according to the treatment plan for outpatient treatment, wherein the first standard code set requires outpatient treatment;
[0035] When the target medical information is the second standard code set, the resident doctor information and nurse information associated with the patient are determined, and the resident doctor account's permission to view the patient's target medical information is configured to not include contact information, and the nurse account's permission to view the patient's target medical information is configured to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is the target medical information that hides part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same; wherein, the second standard code set represents hospitalization.
[0036] In another aspect, a medical information management device includes a processor and a memory, wherein the processor is connected to the memory:
[0037] The processor is configured to call and execute the program stored in the memory;
[0038] The memory is used to store the program, and the program is at least used to execute any one of the medical information management methods described above.
[0039] The technical solution provided by the present invention has at least the following beneficial effects:
[0040] After obtaining patient information, by setting different target medical information access permissions for the doctor account and other accounts, the doctor can fully review the patient's medical information, while hiding the patient's contact information, preventing criminals from directly obtaining all patient information through the doctor account; the access permissions of other auxiliary accounts do not include specific medical details or hide part of the medical condition, which can achieve the auxiliary purpose while preventing information leakage. Therefore, the technical solution provided by the present invention first encodes the medical information and then performs secondary protection on the information, thus achieving the protection of patient information, preventing the complete leakage of patient information, reducing the information channels for criminals to contact patients and their families, and reducing the chances of patients and their families being deceived. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0042] Figure 1 A flowchart of a medical information management method provided by one embodiment of the present invention;
[0043] Figure 2 A schematic diagram of the structure of a medical information management system provided by one embodiment of the present invention;
[0044] Figure 3 A schematic structural diagram of a medical information management device provided in one embodiment of the present invention. DETAILED DESCRIPTION
[0045] To make the objectives, technical solutions, and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other implementations obtained by those of ordinary skill in the art without inventive effort are within the scope of protection of the present invention.
[0046] As described in the background art, when a patient visits a hospital for treatment, the patient's identification information, contact information, basic medical information, etc. will be recorded in the treatment information. As the treatment process progresses, the patient's medical information will be continuously updated. When the patient's treatment information is leaked, it is very likely to bring convenience to criminals and bring risks of being deceived to patients and their families: for example, criminals pretend to be medical staff, or falsely claim to have special medicines, etc., and take advantage of the patients and their families' desire for a quick recovery to defraud them. In related technologies, hospitals usually post slogans to prevent patients and their families from being deceived in hospital corridors, wards, etc. However, simple signs cannot significantly increase the vigilance of patients and their families, especially for seriously ill patients. If their condition does not improve, they are easily deceived by fraudulent calls.
[0047] Therefore, how to prevent patients and their families from being deceived has become a technical problem that needs to be solved urgently in the existing technology. Based on this, the embodiments of the present invention provide a medical information management method, system and device to fundamentally reduce the risk of patient information leakage, thereby preventing patients and their families from being deceived.
[0048] Figure 1 This is a flow chart of a medical information management method provided by an embodiment of the present invention. The method provided by this application can be applied to a server. Figure 1 , this embodiment may include the following steps:
[0049] Step S101: Acquire the patient's medical information and process the medical information according to a preset format processing rule to obtain target medical information, wherein the medical information includes the patient's personal information and registration information.
[0050] When a patient visits a doctor, they can register on-site, through a mini-program, or through other methods. Personal information includes basic patient information, such as name, gender, ID number, and contact information; registration information includes the patient's appointment doctor information.
[0051] Optionally, processing the target medical information according to a preset format processing rule includes:
[0052] According to the preset table of correspondence between medical information and codes, and the preset position relationship, the medical information is encoded into a corresponding code set;
[0053] Each code in the code set represents a setting object at the corresponding code position.
[0054] The preset position relationship is a position where each medical information is placed; encoding the medical information into a corresponding code set according to the preset medical information and code correspondence table and the preset position relationship, including: determining the code of each medical information item in the preset medical information and code correspondence table, and placing the code at the preset position according to the preset position relationship, forming a code set with the placed codes, and using the code set as the code set;
[0055] It also includes: adjusting the preset position relationship according to the position relationship adjustment instruction.
[0056] For example, a table of correspondence between medical information and codes can be pre-set. For example, if the gender of the patient's personal information is female, the code is 1, and if the gender is male, the code is 2; outpatient treatment is coded as 3, inpatient treatment is coded as 4, and the registered doctor is A. i (The set doctors are arranged according to serial number i) etc.
[0057] The preset position relationship may be [gender, registration information], and other preset position relationships may be set as required. For example, when the medical information is Xiao Ming, female, and registered with Doctor Wang, the encoding may be performed, and the obtained encoding set is [1, A3].
[0058] The preset position relationship can be adjusted according to needs to further improve confidentiality.
[0059] Step S102: When the target medical information is a first standard code set, the outpatient doctor account in the registration information is configured to have access to the patient's target medical information without contact information; the outpatient doctor's auxiliary account is configured to have access to the patient's target medical information without detailed medical conditions, where the detailed medical conditions are set by the outpatient doctor or automatically set based on a training model; and the target medical information of the corresponding patient is updated based on the outpatient treatment plan. The first standard code set represents outpatient treatment.
[0060] For example, the first standard coding set may be [X1, X2, 3], where X1 represents gender and X2 represents registration information.
[0061] After collecting the patient's target medical information, the identification in the target medical information can be used to distinguish whether the patient is receiving outpatient treatment or inpatient treatment. When the patient is receiving outpatient treatment for the first time, the outpatient doctor account is configured so that the patient's contact information cannot be accessed. When the outpatient doctor needs to contact the patient, he or she can contact the patient through the assistant of the auxiliary account. After seeing the patient, the outpatient doctor will update the patient's target medical information in real time. The access permission of the outpatient doctor's auxiliary account does not include detailed medical conditions, where detailed medical conditions can be key medical conditions, which can be set by the outpatient doctor or automatically set by the training model. The training model can be a deep learning model, and the training samples are collected from multiple labeled detailed medical conditions and medical condition information, and multiple iterative updates are performed to obtain the final training model.
[0062] It is understandable that by encoding the medical information and granting different access permissions to personnel with different functions, information leakage is doubly guaranteed.
[0063] For example, the second standard coding set may be [X1, X2, 4], where X1 represents gender and X2 represents registration information.
[0064] When this is not the first outpatient treatment for a patient, the outpatient doctor can check the patient's previous outpatient and hospitalization information.
[0065] Step S103: When the target medical information is hospitalization, determine the resident doctor information and nurse information associated with the patient, and configure the resident doctor account's permission to view the patient's target medical information to not include contact information, and the nurse account's permission to view the patient's target medical information to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is to hide the target medical information of part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same.
[0066] In some embodiments, it also includes: configuring the resident physician auxiliary account's access rights to the patient's target medical information to include the patient's contact information.
[0067] When a patient is hospitalized for the first time, the resident doctor's account can be configured to not be able to access the patient's contact information. When the resident doctor needs to contact the patient, he or she can contact the patient through the nurse account or other assistant account. After seeing the patient, the resident doctor will update the patient's target medical information in real time. The resident doctor's assistant account or the nurse's access permission is to hide the target medical information of some conditions. Among them, the hidden conditions can be more critical conditions that can be hidden, which can be set by the resident doctor or automatically set by the training model. Among them, the training model can be a deep learning model, and the training samples are collected from multiple labeled more critical conditions and condition information that can be hidden, and multiple iterative updates are performed to obtain the final training model.
[0068] When this is not the patient's first hospitalization, the previous resident doctors can be directly matched as the current resident doctors.
[0069] When criminals want to obtain patient information through doctor accounts or other auxiliary accounts, they cannot directly obtain the patient's contact information and detailed medical conditions, and cannot defraud patients and their families in a targeted manner, reducing the risk of patients and their families being deceived.
[0070] It is understandable that after obtaining patient information, by setting different target medical information access rights for the doctor account and other accounts, the doctor can fully review the patient's medical information, while hiding the patient's contact information, so that criminals cannot directly obtain all the patient's information through the doctor account; and the access rights of other auxiliary accounts do not include specific details of the medical condition or hide part of the medical condition, which can achieve the auxiliary purpose and avoid information leakage. Therefore, the technical solution provided by the present invention is adopted. After encoding the medical information, the information is then protected twice, which realizes the protection of patient information, avoids the complete leakage of patient information, reduces the ways for criminals to contact patients and their families, and reduces the chances of patients and their families being deceived.
[0071] In order to encode and protect the medical information, the embodiment of the present application also provides another encoding method. Optionally, the medical information is processed according to a preset format processing rule, including:
[0072] Encoding the medical information through an encoding algorithm and generating multiple decoding keys; each of the decoding keys has different decoding permissions; wherein, encoding the medical information through the encoding algorithm includes: creating a set coding table for each decryption requirement based on the decryption permission requirement of each account; for any set coding table, determining the data bits and segmentation code of the set coding table, mapping the medical information to the set coding table, segmenting the medical information through the segmentation code of the set coding table, and determining the decoding key of the set coding table;
[0073] The method also includes: sending the decoding key to the corresponding account according to the decryption authority requirement, so that different accounts can decode the encoded medical information according to the received decoding key and remap it to the original medical information to obtain the medical information authorized by the account.
[0074] During the encoding process, medical information can be encoded and decoded as network data. Accounts with different permissions (for example, doctors and nurses) are given different decoding permissions after encoding the information, so that each account can only use its own decoding key to decode the medical information that is appropriate for its permissions, thereby improving information security.
[0075] In some embodiments, further comprising:
[0076] In response to a target patient's target information search instruction, obtain a keyword in the target information search instruction and determine the user's target medical information access rights; search for synonyms of the keyword in a preset database and determine whether the user has access rights to the keyword or synonym; if the user does not have access rights to the keyword or synonym, record the number of times the user has searched for non-authorized data;
[0077] Within a preset time period, when the number of times the non-authorized data is viewed exceeds a threshold, an abnormal reminder is sent to the management account.
[0078] If criminals access patient information through users, that is, when sending a target patient (e.g., patient A) target information (e.g., contact information) access instruction, they check whether there are synonyms for "contact information" in the preset database, such as "telephone number," "WeChat ID," etc. After finding the synonyms, they determine whether the user has access rights to the contact information, telephone number, and WeChat ID. If not, the number of non-authorized data accesses by the user is recorded as 1. Each time a non-authorized data access occurs, the number of non-authorized data accesses is incremented by 1. When the number of non-authorized data accesses exceeds the threshold value (e.g., 5 times) within a preset time period, such as 5 minutes, an abnormal reminder is sent to the management account. Among them, the management account can be an account specifically for managing account anomalies.
[0079] It is understandable that by setting a limit on the number of accesses to all synonyms, multiple query operations by criminals can be discovered, and abnormal situations can be handled in a timely manner, such as changing passwords, to avoid leakage of patient information.
[0080] In some embodiments, the method further includes: when the user's account is abnormal, prohibiting the user from logging in and sending a password reset instruction to the user; or
[0081] When the user's account is abnormal, the user is prohibited from logging in within a preset period of time, and a password reset instruction is sent to the user.
[0082] It is understandable that when there is a possibility of illegal elements logging into the account, the user can be prohibited from logging in, a password reset instruction can be sent to the user, or the user can be prohibited from logging in for a preset period of time to avoid leakage of patient information.
[0083] In some embodiments, the personal information is stored in a first storage area, and other target medical information is stored in a second storage area; the method further includes:
[0084] When the user's account is abnormal, a dummy data folder is constructed in the storage area where the non-authorization data is located, dummy data is generated according to the stored data in the storage area where the non-authorization data is located, and the dummy data is stored in the dummy data folder;
[0085] The pseudo data is sent to the user, and an abnormality reminder is sent according to the associated contact information of the user.
[0086] When storing data, different storage areas can be set up, with personal information stored in the first storage area and other target medical information stored in the second storage area. When an account is abnormal, a pseudo-data folder is constructed in the storage area where non-authorized data is stored, pseudo-data is generated based on the stored data in the storage area where the non-authorized data is stored, and the pseudo-data is stored in the pseudo-data folder; the pseudo-data is sent to the user, and an abnormality reminder is sent based on the user's associated contact information.
[0087] It is understandable that with such a setting, managers can directly determine whether there is a risk by checking the pseudo-data folder, or they can handle exceptions through exception reminders, which provides double assurance and minimizes the leakage of patient information.
[0088] In some embodiments, optionally, before determining the resident physician information and nurse information associated with the patient, the method further includes:
[0089] In response to a resident doctor configuration instruction, associating a target resident doctor with a patient; wherein the resident doctor configuration instruction carries information of the target resident doctor;
[0090] According to the bed information and nurse scheduling, target bed information and target nurse information are configured for the patient and associated.
[0091] After obtaining the patient's hospitalization information, if the patient is hospitalized for the first time, the associated resident doctor can be configured based on the hospitalization information. For example, the resident doctor can be a doctor who sees patients in the outpatient clinic or an attending physician set in the hospital. The patient's bed number and the responsible nurse information can also be associated based on the current ward bed information and nurse schedule, and the responsible nurse information can be used as the target nurse information.
[0092] It is understandable that such a setting means that only the nurse responsible for the patient can view some of the patient's medical information, and not all nurses can view the patient's information, which improves the security of the information; similarly, only the resident doctor responsible for the patient can view the patient's target medical information, which improves the security of the information.
[0093] In some embodiments, configuring the nurse account's permission to view the patient's target medical information as the nurse's target medical information permission range includes: configuring the corresponding nurse account's permission to view the patient's target medical information according to each nurse's job responsibilities.
[0094] It is understandable that in order to further improve the security of patient information, the permissions of nurse accounts can be graded. For example, some accounts are only responsible for injections, and their account permissions are only visible to the name, bed number, and injection instructions; some accounts are only responsible for diet, and their account permissions are only visible to the diet list issued by the nutritionist and some information for verifying personal identity.
[0095] Based on a general inventive concept, an embodiment of the present invention further provides a medical information management system for implementing the above method embodiment. Figure 2 A schematic diagram of the structure of a medical information management system provided by an embodiment of the present invention, see Figure 2 The system provided by the embodiment of the present invention may include:
[0096] An acquisition module 21 is used to acquire the patient's target medical information, which includes the patient's personal information and registration information;
[0097] Configuration module 22 is used to configure, when the target medical information is for outpatient treatment, the outpatient doctor account in the registration information to have access to the patient's target medical information to exclude contact information; configure the outpatient doctor auxiliary account to have access to the patient's target medical information to exclude detailed medical conditions, wherein the detailed medical conditions are set by the outpatient doctor or automatically set according to the training model; and update the target medical information of the corresponding patient according to the treatment plan of the outpatient treatment;
[0098] When the target medical information is hospitalization, the resident doctor information and nurse information associated with the patient are determined, and the resident doctor account's permission to view the patient's target medical information is configured to exclude contact information, and the nurse account's permission to view the patient's target medical information is configured to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is to hide the target medical information of part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same.
[0099] In some embodiments, the configuration module is also used to respond to the target patient's target information retrieval instruction, obtain keywords in the target information retrieval instruction, and determine the user's target medical information access rights; search the synonyms of the keywords in the preset database, and determine whether the user has access rights to the keywords or synonyms; when the user does not have access rights to the keywords or synonyms, record the number of non-authorized data retrievals of the user; within a preset time period, when the number of non-authorized data retrievals is greater than a threshold number, send an abnormal reminder to the management account.
[0100] In some embodiments, the configuration module is further configured to prohibit the user from logging in and send a password reset instruction to the user when the user's account is abnormal; or
[0101] When the user's account is abnormal, the user is prohibited from logging in within a preset period of time, and a password reset instruction is sent to the user.
[0102] In some embodiments, the configuration module is further used to configure the resident physician assistant account's access rights to the patient's target medical information to include the patient's contact information.
[0103] In some embodiments, the configuration module is further configured to associate a target resident with a patient in response to a resident configuration instruction; wherein the resident configuration instruction carries information of the target resident;
[0104] According to the bed information and nurse scheduling, target bed information and target nurse information are configured for the patient and associated.
[0105] In some embodiments, personal information is stored in a first storage area, and other target medical information is stored in a second storage area. The configuration module is further configured to, when the user's account is abnormal, construct a dummy data folder in the storage area where the non-authorized data is located, generate dummy data based on the stored data in the storage area where the non-authorized data is located, and store the dummy data in the dummy data folder;
[0106] The pseudo data is sent to the user, and an abnormal reminder is sent according to the user's associated contact information.
[0107] Regarding the system in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0108] It is understandable that after obtaining patient information, by setting different target medical information access permissions for the doctor account and other accounts, the doctor can fully review the patient's medical information, while hiding the patient's contact information, so that criminals cannot directly obtain all patient information through the doctor account; the access permissions of other auxiliary accounts do not include specific medical details or hide part of the medical condition, which can achieve the auxiliary purpose while avoiding information leakage. Therefore, the technical solution provided by the present invention realizes the protection of patient information, avoids the complete leakage of patient information, reduces the information channels for criminals to contact patients and their families, and reduces the chances of patients and their families being deceived.
[0109] The present invention also provides a medical information management device for implementing the above method embodiment. Figure 3 This is a schematic diagram of the structure of a medical information management device provided by one embodiment of the present invention. Figure 3 As shown, the medical information management device of this embodiment includes a processor 31 and a memory 32, and the processor 31 is connected to the memory 32. The processor 31 is used to call and execute the program stored in the memory 32; the memory 32 is used to store the program, and the program is used to at least execute the medical information management method in the above embodiment.
[0110] The specific implementation scheme of the medical information management device provided in the embodiments of the present application can refer to the implementation scheme of the medical information management method in any of the above embodiments, and will not be repeated here.
[0111] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.
[0112] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" is at least two.
[0113] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.
[0114] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0115] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.
[0116] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.
[0117] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.
[0118] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
[0119] Although the embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and are not to be construed as limitations on the present invention. A person skilled in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.
Claims
1. A medical information management method, characterized in that: include: Obtaining the patient's medical information, and processing the medical information according to a preset format processing rule to obtain target medical information, wherein the medical information includes the patient's personal information and registration information; When the target medical information is a first standard code set, the outpatient doctor account in the registration information is configured to have access to the patient's target medical information without contact information; the outpatient doctor auxiliary account is configured to have access to the patient's target medical information without detailed medical conditions, wherein the detailed medical conditions are set by the outpatient doctor or automatically set according to the training model; according to the treatment plan for outpatient treatment, the target medical information of the corresponding patient is updated; wherein the first standard code set requires outpatient treatment; When the target medical information is a second standard code set, the resident doctor information and nurse information associated with the patient are determined, and the resident doctor account's permission to view the patient's target medical information is configured to exclude contact information, and the nurse account's permission to view the patient's target medical information is configured to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is the target medical information that hides part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same; wherein, the second standard code set represents hospitalization.
2. The method according to claim 1, characterized in that The processing of the medical information according to a preset format processing rule includes: According to the preset table of correspondence between medical information and codes, and the preset position relationship, the medical information is encoded into a corresponding code set; wherein each code in the code set represents a setting object of a corresponding code position, and the preset position relationship is a position where each medical information is placed; the encoding of the medical information into a corresponding code set according to the preset table of correspondence between medical information and codes, and the preset position relationship, includes: In the preset medical information and code correspondence table, determine the code of each medical information item, and place the code at the preset position according to the preset position relationship, form a code set with the codes after being placed at the position, and use the code set as the code set; It also includes: adjusting the preset position relationship according to the position relationship adjustment instruction.
3. The method according to claim 1, characterized in that The processing of the medical information according to a preset format processing rule includes: The medical information is encoded by a coding algorithm, and a plurality of decoding keys are generated; each of the decoding keys has a different decoding authority; wherein the medical information is encoded by a coding algorithm, including: creating a set coding table for each decryption requirement according to the decryption authority requirement of each account; for any set coding table, determining the data bits and segmentation codes of the set coding table, mapping the medical information to the set coding table, segmenting the medical information by the segmentation codes of the set coding table, and determining the decoding key of the set coding table; The method also includes: sending the decoding key to the corresponding account according to the decryption authority requirement, so that different accounts can decode the encoded medical information according to the received decoding key and remap it to the original medical information to obtain the medical information authorized by the account.
4. The method according to claim 1, characterized in that: Also includes: In response to a target information search instruction of a target patient, obtaining a keyword in the target information search instruction and determining a user's target medical information access permission; Searching for synonyms of the keyword in a preset database and determining whether the user has access rights to the keyword or synonym; when the user does not have access rights to the keyword or synonym, recording the number of times the user has searched non-authorized data; Within a preset time period, when the number of times the non-authorized data is consulted exceeds a threshold, an abnormal reminder is sent to the management account.
5. The method according to claim 3, characterized in that: Also includes: When the user's account is abnormal, the user is prohibited from logging in and a password reset instruction is sent to the user; or, When the user's account is abnormal, the user is prohibited from logging in within a preset period of time, and a password reset instruction is sent to the user; The method also includes: configuring the resident physician assistant account's access rights to the patient's target medical information to include the patient's contact information.
6. The method according to claim 1, characterized in that Before determining the resident doctor information and nurse information associated with the patient, the method further includes: In response to the resident doctor configuration instruction, associating the target resident doctor with the patient; wherein the resident doctor configuration instruction carries the information of the target resident doctor; According to the bed information and nurse scheduling, the target bed information and target nurse information are configured for the patient and associated.
7. The method according to claim 1, characterized in that Configure the nurse account's permission to view the patient's target medical information as the nurse's target medical information permission range, including: According to the job responsibilities of each nurse, configure the corresponding nurse account to have access to the patient's target medical information.
8. The method according to claim 3, characterized in that The personal information is stored in the first storage area, and other target medical information is stored in the second storage area; the method further includes: When the user's account is abnormal, a dummy data folder is constructed in the storage area where the non-authorization data is located, dummy data is generated according to the storage data in the storage area where the non-authorization data is located, and the dummy data is stored in the dummy data folder; The pseudo data is sent to the user, and an abnormal reminder is sent according to the associated contact information of the user.
9. A medical information management system, characterized in that: include: An acquisition module is used to acquire the patient's medical information and process the target medical information according to a preset format processing rule to obtain the target medical information, wherein the target medical information includes the patient's personal information and registration information; A configuration module is used to configure the outpatient doctor account in the registration information to have access to the patient's target medical information to exclude contact information when the target medical information is a first standard code set; configure the outpatient doctor auxiliary account to have access to the patient's target medical information to exclude detailed medical conditions, wherein the detailed medical conditions are set by the outpatient doctor or automatically set according to the training model; update the target medical information of the corresponding patient according to the treatment plan of outpatient treatment; wherein the first standard code set requires outpatient treatment; When the target medical information is a second standard code set, the resident doctor information and nurse information associated with the patient are determined, and the resident doctor account's permission to view the patient's target medical information is configured to exclude contact information, and the nurse account's permission to view the patient's target medical information is configured to be within the nurse's target medical information permission range; wherein, the nurse's target medical information permission range is the target medical information that hides part of the disease; the number of the resident doctors is at least one, and the number of the nurses is at least one; the target medical information permission of each nurse account is not exactly the same; wherein, the second standard code set represents hospitalization.
10. A medical information management device, characterized in that: The invention comprises a processor and a memory, wherein the processor is connected to the memory: Wherein, the processor is used to call and execute the program stored in the memory; The memory is used to store the program, and the program is at least used to execute the medical information management method described in any one of claims 1-8.