Medical information management system, method and device, storage medium and equipment

Abstract

The embodiment of the invention discloses a medical information management system, method and device, a storage medium and equipment.The basic information of a user is collected and stored through a medical information management center, the medical information management center serves as a unified information management center of different hospitals, the user does not need to repeatedly input the basic information when seeing a doctor in the different hospitals, and the user experience is improved. A hospital only needs to inquire and obtain the basic information of the user from the medical information management center, and the process of seeing a doctor by the user can be effectively simplified. Moreover, when the medical information management center provides the basic information of the user to the hospital system, the basic information of the user is provided after desensitization processing, and privacy leakage of the user is also avoided.

Description

Technical Field

[0001] The present specification relates to the field of computer technology, and in particular to a medical information management system, method, apparatus, storage medium and device. Background Art

[0002] Medical treatment is an indispensable part of people's daily life. When users go to the hospital for medical treatment, they often need to enter their basic information according to the hospital's requirements, including personal information, medical records, etc., for the purpose of file creation.

[0003] At present, different hospitals require users to enter different basic information in different contents and formats. Moreover, users need to repeatedly enter basic information every time they go to different hospitals for medical treatment, which makes the medical treatment process more complicated.

[0004] Moreover, the basic information entered by users is generally stored in the hospital system in plain text, which also poses a security risk to the user's privacy. Summary of the invention

[0005] The embodiments of this specification provide a medical information management system, method, device, storage medium and electronic device to partially solve the problems existing in the above-mentioned prior art.

[0006] The embodiments of this specification adopt the following technical solutions:

[0007] This specification provides a medical information management system, the system comprising: a medical information management center, and hospital systems corresponding to multiple hospitals;

[0008] The medical information management center is used to receive the first information acquisition request sent by the hospital system, extract the pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request, desensitize the extracted basic information, and return the desensitized basic information to the hospital system;

[0009] The hospital system is used to send a first information acquisition request carrying the user identifier to the medical information management center, and receive the desensitized basic information returned by the medical information management center.

[0010] Optionally, the medical information management center is also used to receive basic information uploaded by the user, and store the user identification of the user in association with the basic information.

[0011] Optionally, the medical information management center is specifically used to receive a first authorization acquisition request sent by a user, generate first authorization information carrying a user identifier and first authentication information of the user according to the first authorization acquisition request, and return the first authorization information to the user;

[0012] The hospital system is specifically used to generate a first information acquisition request carrying the user identifier and the first authentication information based on the first authorization information provided by the user, and send the request to the medical information management center;

[0013] The medical information management center is also used to determine whether the authentication of the hospital system is passed according to the first authentication information carried in the first information acquisition request before returning the desensitized basic information to the hospital system.

[0014] Optionally, the basic information includes multiple types of user information;

[0015] The medical information management center is specifically used to desensitize each type of user information in the basic information according to the desensitization rules pre-set for each type of user information.

[0016] Optionally, the medical information management center is further used to receive a second authorization acquisition request sent by a user, generate second authorization information carrying a user identifier and second authentication information of the user according to the second authorization acquisition request, and return the second authorization information to the user;

[0017] The hospital system is further used to generate a second information acquisition request carrying the user identification and the second authentication information based on the second authorization information provided by the user, and send the request to the medical information management center;

[0018] The medical information management center is also used to, based on the second authentication information carried in the second information acquisition request, determine that after the authentication of the hospital system is passed, extract the basic information corresponding to the pre-stored user identifier based on the user identifier carried in the second information acquisition request, and return the extracted basic information to the hospital system.

[0019] Optionally, the medical information management center is also used to, after returning the extracted basic information to the hospital system, record a sensitive information query log according to the account used by the hospital system to log into the medical information management center, and when preset conditions are met, identify whether the account is abnormal based on the sensitive information query log.

[0020] This specification provides a medical information management method, the method comprising:

[0021] Receiving a first information acquisition request sent by a hospital system;

[0022] Extracting pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request;

[0023] Desensitizing the extracted basic information;

[0024] The desensitized basic information is returned to the hospital system.

[0025] Optionally, before extracting the pre-stored basic information corresponding to the user identifier, the method further includes:

[0026] Receive basic information uploaded by users;

[0027] The user identification of the user and the basic information are associated and stored.

[0028] Optionally, receiving a first information acquisition request sent by a hospital system specifically includes:

[0029] Receive a first authorization request sent by a user;

[0030] Generate first authorization information carrying the user identifier and first authentication information of the user according to the first authorization acquisition request, and return the first authorization information to the user;

[0031] Receiving a first information acquisition request generated by the hospital system based on the first authorization information provided by the user, wherein the first information acquisition request carries the user identifier and the first authentication information;

[0032] Before returning the desensitized basic information to the hospital system, the method further includes:

[0033] According to the first authentication information carried in the first information acquisition request, it is determined that the authentication of the hospital system is passed.

[0034] Optionally, the basic information includes multiple types of user information;

[0035] Desensitizing the extracted basic information, specifically including:

[0036] Each type of user information in the basic information is desensitized according to the desensitization rules pre-set for each type of user information.

[0037] Optionally, the method further comprises:

[0038] Receive a second authorization acquisition request sent by the user;

[0039] Generate, according to the second authorization acquisition request, second authorization information carrying the user identifier and second authentication information of the user, and return the second authorization information to the user;

[0040] receiving a second information acquisition request generated by the hospital system based on the second authorization information provided by the user, wherein the second information acquisition request carries the user identifier and the second authentication information;

[0041] According to the second authentication information carried in the second information acquisition request, after determining that the authentication of the hospital system is passed, according to the user identifier carried in the second information acquisition request, the basic information corresponding to the pre-stored user identifier is extracted, and the extracted basic information is returned to the hospital system.

[0042] Optionally, after returning the extracted basic information to the hospital system, the method further includes:

[0043] Record sensitive information query logs according to the account used by the hospital system to log into the medical information management center;

[0044] When the preset conditions are met, the sensitive information query log is used to identify whether the account is abnormal.

[0045] This specification provides a medical information management device, the device comprising:

[0046] A receiving module, used for receiving a first information acquisition request sent by a hospital system;

[0047] A query module, configured to extract the pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request;

[0048] A desensitization module, used for desensitizing the extracted basic information;

[0049] The sending module is used to return the desensitized basic information to the hospital system.

[0050] This specification provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned medical information management method is implemented.

[0051] This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned medical information management method when executing the program.

[0052] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0053] The embodiments of this specification disclose a medical information management method, which uses a medical information management center to collect and store basic information of users. As a unified information management center for different hospitals, users do not need to repeatedly input their basic information when seeking medical treatment in different hospitals. The hospital only needs to query and obtain the basic information of the user from the medical information management center, which can effectively simplify the process of users seeking medical treatment. In addition, when the medical information management center provides the basic information of the user to the hospital system, it also needs to desensitize the basic information of the user before providing it, which also avoids the leakage of the user's privacy. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The drawings described herein are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation on this specification. In the drawings:

[0055] Figure 1 A schematic diagram of a medical information management process provided in an embodiment of this specification;

[0056] Figure 2 A schematic diagram of an upload page provided in an embodiment of this specification;

[0057] Figure 3 A schematic diagram of a medical information management device provided in an embodiment of this specification;

[0058] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0060] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0061] The embodiments of this specification provide a medical information management system, including a medical information management center and hospital systems corresponding to multiple hospitals. The medical information management center is used to uniformly manage the basic information of users for multiple hospitals. That is, when the hospital system needs the basic information of the user, it is uniformly provided by the medical information management center. In addition, the medical information management center also needs to desensitize the basic information of the user before providing it to the hospital system, so that the user only needs to upload the basic information to the medical information management center once, without the need to repeatedly enter it in different hospitals, and also eliminates the security risks of user privacy leakage.

[0062] Based on the above system, the embodiment of this specification provides a method for medical information management, such as Figure 1 shown.

[0063] Figure 1 A flowchart of medical information management provided in this specification may include the following steps:

[0064] S100: The medical information management center receives the basic information uploaded by the user, and associates the user ID and the basic information for storage.

[0065] In the embodiments of this specification, users can use their own terminals (including personal computers, mobile phones, etc.) to upload their basic information to the medical information management center. The basic information of the user may include the user's personal information and medical records, and the personal information may include but is not limited to the user's name, ID number, contact information, address, etc.

[0066] Specifically, the user may first register his or her personal account at the medical information management center, and then upload his or her basic information through the personal account. The medical information management center will then use the user's personal account as the user's user ID and store it in association with the basic information uploaded by the user.

[0067] S102: The medical information management center receives a first authorization request sent by a user.

[0068] When a user goes to the hospital for medical treatment, the user's basic information may be needed to provide medical services to the user. At this time, the hospital system can directly send a first information acquisition request carrying the user's user ID to the medical information management center, so that the medical information management center returns the basic information corresponding to the user ID.

[0069] In order to prevent the basic information of the user from being easily obtained by criminals, the hospital system can obtain the basic information of the user from the medical information management center only after obtaining the authorization of the user. Specifically, the user can first send a first authorization acquisition request to the medical information management center through his terminal, and the first authorization acquisition request also carries the personal account used by the user, that is, the user ID.

[0070] S104: Generate first authorization information carrying the user identification and first authentication information of the user, and return it to the user.

[0071] After receiving the first authorization request sent by the user, the medical information management center can generate first authentication information, associate and cache the first authentication information with the user's user ID, and then return the user's user ID and first authentication information to the user in the first authorization information.

[0072] The first authentication information described in the embodiments of this specification may be a string of random characters, an authentication code of a specified number of digits, or a QR code encoded from a string of random characters.

[0073] After the user obtains the first authorization information, the user can provide the first authorization information, especially the first authentication information therein, to the hospital system. If the first authentication information is an authentication code of a specified number of digits, the user can manually input the authentication code into the hospital system; if the first authentication information is a QR code, the user can provide the QR code to the hospital system for scanning, so that the hospital system can obtain the random characters carried in the QR code.

[0074] S106: Based on the first authorization information provided by the user, the hospital system generates a first information acquisition request carrying the user identification and the first authentication information.

[0075] After the hospital system obtains the first authentication information in the first authorization information, it can generate a first information acquisition request, carry the user identifier of the user and the first authentication information provided by the user in the first information acquisition request, and then send the first information acquisition request to the medical information management center.

[0076] S108: The medical information management center receives the first information acquisition request sent by the hospital system.

[0077] S110: Determine, based on the first authentication information carried in the first information acquisition request, whether the hospital system authentication is successful.

[0078] After receiving the first information acquisition request, the medical information management center may first query the cached first authentication information associated with the user identifier according to the user identifier carried in the first information acquisition request, and then compare the queried first authentication information with the first authentication information carried in the first information acquisition request to authenticate the hospital system. If the comparison result is that the two are consistent, the authentication is passed, otherwise the authentication is not passed.

[0079] S112: Extracting pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request.

[0080] When the medical information management center passes the hospital system authentication, it can extract the pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request.

[0081] Furthermore, since the user's basic information includes various types of user information such as the user's name, ID number, contact information, address, medical history, etc., the first information acquisition request sent by the hospital system may also carry the type of basic information required by the hospital system. The medical information management system can then extract user information corresponding to the type from the basic information associated with the user identifier based on the type of basic information carried in the first information acquisition request.

[0082] S114: Desensitizing the extracted basic information, and returning the desensitized basic information to the hospital system.

[0083] Since some user information included in the user's basic information is actually the user's private information, in the embodiment of this specification, after the medical information management center extracts the basic information, it is necessary to desensitize the user information that is private information in the basic information, and then return the desensitized basic information to the hospital system.

[0084] Specifically, in step S100, when the user uploads basic information to the medical information management center through his / her terminal, the upload page displayed to the user by the medical information management center may include privacy options for the user to set. The upload page includes a place to fill in all types of user information in the basic information, as well as options for setting whether each type of user information is private information, such as Figure 2 shown.

[0085] exist Figure 2 The upload page shown contains filling boxes for various types of user information such as name, ID number, contact information, address, medical history, etc. After each filling box, there is also a check box indicating whether the corresponding type of user information is private information. If checked, it means that the information of this type is private information, and if unchecked, it means that the information of this type is not private information.

[0086] The medical information management center can also set corresponding desensitization rules for each type of user information. When desensitizing the basic information, for each type of user information in the basic information, the user information of that type can be desensitized according to the pre-set desensitization rules corresponding to the user information of that type. For example, the desensitization rule set for the mobile phone number can be to hide the 4th to 7th digits in the mobile phone number, and the hidden digits are replaced by asterisks. The desensitization rule set for the ID card number can be to hide the 7th to 14th digits in the ID card number, and the hidden digits are replaced by asterisks. The specific desensitization rules are not limited in the embodiments of this specification, as long as the security of private information can be guaranteed.

[0087] Through the above method, the medical information management center is used to collect and store the basic information of users. As a unified information management center for different hospitals, users do not need to repeatedly enter their basic information when seeking medical treatment in different hospitals. The hospital only needs to query and obtain the basic information of the user from the medical information management center, which can effectively simplify the process of users seeking medical treatment. In addition, when the medical information management center provides the basic information of the user to the hospital system, it also needs to desensitize the basic information of the user before providing it, which also avoids the leakage of the user's privacy.

[0088] In addition, considering that in actual application scenarios, when hospitals provide medical services to users, the user's privacy information may indeed be used in some special circumstances. At this time, the user needs to send a second authorization acquisition request carrying the user's user ID to the medical information management center. The medical information management center can generate second authorization information carrying the user's user ID and second authentication information based on the second authorization acquisition request, and return it to the user, so that the user provides the second authorization information to the hospital system. The hospital system gives the second authorization information provided by the user, generates a second information acquisition request carrying the user ID and the second authentication information, and sends it to the medical information management center. The medical information management center determines that the authentication of the hospital system is passed based on the second authentication information carried in the second information acquisition request, and then extracts the pre-stored basic information corresponding to the user ID based on the user ID carried in the second information acquisition request. The extracted basic information is not desensitized and is directly returned to the hospital system.

[0089] Among them, the above-mentioned second authentication information is similar to the first authentication information, and will not be repeated here. The distinction between the first information acquisition request and the second information acquisition request can be distinguished by the content of the preset fields in the two requests. For example, after receiving an information acquisition request, the medical information management center can identify whether the content of the preset field in the information acquisition request is the specified content (such as 1). If it is the specified content, it is determined that the information acquisition request is the second information acquisition request, which is used to obtain non-desensitized basic information. Otherwise, it is determined that the information acquisition request is the first information acquisition request, which is used to obtain desensitized basic information.

[0090] Of course, when the hospital system generates the second information acquisition request, it can also carry the type of non-massified user information required in the basic information in the above preset field. In this case, the medical information management center will not perform any masking on the extracted user information of this type and directly return it to the hospital system. Other basic information and Figure 1 The method shown also performs desensitization and then returns to the hospital system.

[0091] Furthermore, the hospital system also needs to use the hospital account pre-registered in the medical information management center to obtain the user's basic information. Since the hospital system in the embodiment of this specification can obtain both the user's desensitized basic information and the user's non-desensitized basic information, in order to facilitate the management of hospital accounts, the medical information management center can set different permissions for each hospital account, for example, setting high access rights and low access rights. Hospital accounts with high access rights can obtain both the user's desensitized basic information and the user's non-desensitized basic information, and hospital accounts with only low access rights can only obtain the user's desensitized basic information. Correspondingly, when the medical information management center receives a second information acquisition request for querying non-desensitized basic information, it can first determine whether the hospital account that sent the second information acquisition request has the authority to obtain non-desensitized basic information. If it does, then execute the subsequent process, that is, authenticate according to the second authentication information carried in the second information acquisition request, otherwise directly reject the second information acquisition request.

[0092] Correspondingly, after returning the non-desensitized basic information to the hospital system, the medical information management center can also record the sensitive information query log based on the hospital account used by the hospital system to log in to the medical information management center. The recorded log may include the hospital account used for the current query of the non-desensitized basic information, the user ID associated with the basic information being queried, the time of this query, etc. When the preset conditions are met, the sensitive information query log is used to identify whether the hospital account is abnormal. For example, when the preset cycle end time arrives, it is determined that the preset conditions are met, and all records in the sensitive information query log can be used to identify whether there are abnormal hospital accounts. This is to prevent criminals from stealing users' privacy information through hospital accounts with high access rights.

[0093] The specific method for identifying abnormal hospital accounts can be through manual auditing, by using preset identification rules, or by using pre-trained machine learning models to identify whether there are abnormal hospital accounts.

[0094] The above is a medical information management method and system provided in the embodiments of this specification. Based on the same idea, this specification also provides corresponding devices, storage media and electronic devices.

[0095] Figure 3 A schematic diagram of a medical information management device provided in an embodiment of this specification, the medical information management device may be located in a medical information management center, and the device includes:

[0096] A receiving module 301 is used to receive a first information acquisition request sent by a hospital system;

[0097] A query module 302, configured to extract pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request;

[0098] A desensitization module 303, used for desensitizing the extracted basic information;

[0099] The sending module 304 is used to return the desensitized basic information to the hospital system.

[0100] Optionally, the receiving module 301 is further configured to receive basic information uploaded by a user before extracting the pre-stored basic information corresponding to the user identifier, and store the user identifier of the user in association with the basic information.

[0101] Optionally, the receiving module 301 is specifically used to receive a first authorization acquisition request sent by a user, generate first authorization information carrying a user identifier and first authentication information of the user according to the first authorization acquisition request, and return the first authorization information to the user, and receive a first information acquisition request generated by the hospital system based on the first authorization information provided by the user, wherein the first information acquisition request carries the user identifier and the first authentication information;

[0102] The sending module 304 is also used to determine whether the authentication of the hospital system is passed according to the first authentication information carried in the first information acquisition request before returning the desensitized basic information to the hospital system.

[0103] Optionally, the basic information includes multiple types of user information;

[0104] The desensitization module 303 is specifically configured to desensitize each type of user information in the basic information according to a desensitization rule pre-set for each type of user information.

[0105] Optionally, the receiving module 301 is further used to receive a second authorization acquisition request sent by the user, generate second authorization information carrying the user identifier and second authentication information of the user according to the second authorization acquisition request, and return the second authorization information to the user, and receive a second information acquisition request generated by the hospital system based on the second authorization information provided by the user, wherein the second information acquisition request carries the user identifier and the second authentication information;

[0106] The query module 302 is further configured to extract the pre-stored basic information corresponding to the user identifier according to the user identifier carried in the second information acquisition request;

[0107] The sending module 304 is further configured to return the basic information extracted by the query module 302 to the hospital system after determining that the hospital system has been authenticated according to the second authentication information carried in the second information acquisition request.

[0108] Optionally, the device further comprises:

[0109] The log module 305 is used to record the sensitive information query log according to the account used by the hospital system to log in to the medical information management center after the sending module 304 returns the extracted basic information to the hospital system, and when the preset conditions are met, identify whether the account is abnormal based on the sensitive information query log.

[0110] This specification also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, it can be used to perform the above Figure 1 Provides methods for managing medical information.

[0111] based on Figure 1 Based on the Figure 1 The medical information management method shown in the present specification also provides Figure 4 The structural diagram of the electronic device shown in FIG. Figure 4 At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include other hardware required for the business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to achieve the above Figure 1 The medical information management method described.

[0112] Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the executor of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0113] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0114] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0115] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0116] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0117] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0118] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0119] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0120] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0121] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0122] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0123] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0124] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0125] It will be appreciated by those skilled in the art that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0126] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0127] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0128] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A medical information management system, the system comprising: Medical information management center and hospital systems corresponding to multiple hospitals; The medical information management center is used to receive the first information acquisition request sent by the hospital system, extract the pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request, desensitize the extracted basic information, and return the desensitized basic information to the hospital system; The hospital system is used to send a first information acquisition request carrying the user identifier to the medical information management center, and receive the desensitized basic information returned by the medical information management center.

2. According to the medical information management system as described in claim 1, the medical information management center is also used to receive basic information uploaded by the user, and store the user identification of the user in association with the basic information.

3. The medical information management system according to claim 1, wherein the medical information management center is specifically used to receive a first authorization acquisition request sent by a user, generate first authorization information carrying a user identifier and first authentication information of the user according to the first authorization acquisition request, and return the first authorization information to the user; The hospital system is specifically used to generate a first information acquisition request carrying the user identifier and the first authentication information based on the first authorization information provided by the user, and send the request to the medical information management center; The medical information management center is also used to determine whether the authentication of the hospital system is passed according to the first authentication information carried in the first information acquisition request before returning the desensitized basic information to the hospital system.

4. The medical information management system according to claim 1, wherein the basic information includes multiple types of user information; The medical information management center is specifically used to desensitize each type of user information in the basic information according to the desensitization rules pre-set for each type of user information.

5. The medical information management system according to claim 1, wherein the medical information management center is further used to receive a second authorization acquisition request sent by a user, generate second authorization information carrying a user identifier and second authentication information of the user according to the second authorization acquisition request, and return the second authorization information to the user; The hospital system is further used to generate a second information acquisition request carrying the user identification and the second authentication information based on the second authorization information provided by the user, and send the request to the medical information management center; The medical information management center is also used to, based on the second authentication information carried in the second information acquisition request, determine that after the authentication of the hospital system is passed, extract the basic information corresponding to the pre-stored user identifier based on the user identifier carried in the second information acquisition request, and return the extracted basic information to the hospital system.

6. The medical information management system as described in claim 5, wherein the medical information management center is also used to, after returning the extracted basic information to the hospital system, record a sensitive information query log according to the account used by the hospital system to log in to the medical information management center, and when preset conditions are met, identify whether the account is abnormal based on the sensitive information query log.

7. A medical information management method, the method being applied to a medical information management center, the method comprising: Receiving a first information acquisition request sent by a hospital system; Extracting pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request; Desensitizing the extracted basic information; The desensitized basic information is returned to the hospital system.

8. The method according to claim 7, before extracting the pre-stored basic information corresponding to the user identification, the method further comprises: Receive basic information uploaded by users; The user identification of the user and the basic information are associated and stored.

9. The method according to claim 7, receiving a first information acquisition request sent by a hospital system, specifically comprising: Receive a first authorization request sent by a user; Generate first authorization information carrying the user identifier and first authentication information of the user according to the first authorization acquisition request, and return the first authorization information to the user; Receiving a first information acquisition request generated by the hospital system based on the first authorization information provided by the user, wherein the first information acquisition request carries the user identifier and the first authentication information; Before returning the desensitized basic information to the hospital system, the method further includes: According to the first authentication information carried in the first information acquisition request, it is determined that the authentication of the hospital system is passed.

10. The method according to claim 7, wherein the basic information includes multiple types of user information; Desensitizing the extracted basic information, specifically including: Each type of user information in the basic information is desensitized according to the desensitization rules pre-set for each type of user information.

11. The method of claim 7, further comprising: Receive a second authorization acquisition request sent by the user; Generate, according to the second authorization acquisition request, second authorization information carrying the user identifier and second authentication information of the user, and return the second authorization information to the user; receiving a second information acquisition request generated by the hospital system based on the second authorization information provided by the user, wherein the second information acquisition request carries the user identifier and the second authentication information; According to the second authentication information carried in the second information acquisition request, after determining that the authentication of the hospital system is passed, according to the user identifier carried in the second information acquisition request, the basic information corresponding to the pre-stored user identifier is extracted, and the extracted basic information is returned to the hospital system.

12. The method according to claim 11, after returning the extracted basic information to the hospital system, the method further comprises: Record sensitive information query logs according to the account used by the hospital system to log into the medical information management center; When the preset conditions are met, the sensitive information query log is used to identify whether the account is abnormal.

13. A medical information management device, comprising: A receiving module, used for receiving a first information acquisition request sent by a hospital system; A query module, configured to extract pre-stored basic information corresponding to the user identifier according to the user identifier carried in the first information acquisition request; A desensitization module, used for desensitizing the extracted basic information; The sending module is used to return the desensitized basic information to the hospital system.

14. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 7 to 12.

15. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 7 to 12 when executing the program.

Images