Patient information registration method and device, electronic equipment and storage medium

Abstract

The invention relates to a patient information registration method and apparatus, an electronic device and a storage medium. The method comprises the steps of obtaining identity information of a to-be-treated person through a target platform; if the to-be-treated person is not the person registered on the target platform, the identity type of the to-be-treated person is judged according to the identity information and a preset identity judgment rule, and the identity type is a new patient, a patient capable of being automatically combined or a suspected patient; if the identity type is a new patient or a suspected patient, generating a new registration identifier of the person to be treated according to the identity information and storing the new registration identifier; and if the identity type is a patient capable of being automatically merged, obtaining an original registration identifier of the patient to be treated according to the identity information and storing the original registration identifier. Through the method provided by the invention, the identity information intercommunication of the to-be-treated person in each hospital can be realized, the treatment efficiency can be improved, and the treatment experience of the patient can also be improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a patient information registration method, device, electronic device and storage medium. Background Art

[0002] In the existing technology, the registration information of patients in each hospital is independent of each other. That is, after a user registers in a hospital, if he changes to another hospital for treatment, he needs to register, check or inquire again, which will consume a lot of medical resources. Therefore, there is an urgent need in the existing technology for a solution that can improve the efficiency of medical treatment and enhance the patient's medical experience. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide a patient information registration method, device, electronic device and storage medium, aiming to solve at least one of the above technical problems.

[0004] In the first aspect, the technical solution of the present invention to solve the above technical problem is as follows: a patient information registration method, the method comprising:

[0005] Obtain the identity information of the patient to be treated through the target platform;

[0006] If the patient to be seen is not a person who has registered on the target platform, the identity type of the patient to be seen is determined according to the identity information and the preset identity determination rules, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient;

[0007] If the identity type is a new patient or a suspected patient, a new registration identifier of the patient to be treated is generated and saved according to the identity information;

[0008] If the identity type is that the patient can be automatically merged, the original registration identification of the person to be treated is obtained and saved based on the identity information.

[0009] The beneficial effects of the present invention are as follows: based on the identity information of the patient and the preset identity judgment rules, the identity type of the patient can be accurately judged first, and different registration processes can be performed based on the identity type to realize the registration of the patient, and based on the scheme of the present application, the identity information of the patient in various hospitals can be interoperable based on the identity type of the patient, which can not only improve the efficiency of medical treatment, but also enhance the patient's medical experience.

[0010] Based on the above technical solution, the present invention can also be improved as follows.

[0011] Furthermore, if the patient to be treated is not a person who has registered on the target platform, judging the identity type of the patient to be treated according to the identity information and the preset identity judgment rule includes:

[0012] If the patient is not a registered patient on the target platform, and there is no target identity information matching the identity information of the patient in the database, the patient is judged to be a new patient;

[0013] If the patient to be seen is not a person who has registered on the target platform, and the database contains target identity information that is the same as the identity information of the patient to be seen, then the identity type of the patient to be seen is determined to be a patient that can be automatically merged;

[0014] If the patient is not a registered patient on the target platform, and the database contains target identity information similar to the identity information of the patient, the identity type of the patient is determined to be a suspected patient.

[0015] The beneficial effect of adopting the above further solution is that, based on the preset identity judgment rules, the identity type of the person to be treated can be accurately judged.

[0016] Furthermore, if the identity type is a suspected patient, the method further includes:

[0017] The identity information of the patient to be treated and the new registration identifier are stored in a suspected patient list, and the suspected patient list is displayed.

[0018] The beneficial effect of adopting the above further scheme is that the suspected patients can be managed more easily through the suspected patients list.

[0019] Furthermore, the method further comprises:

[0020] According to the identity supplementary information of each suspected patient in the suspected patient list, determining whether there is a patient with the same identity information in the suspected patient list;

[0021] If so, the patient information of patients with the same identity information will be merged.

[0022] The beneficial effect of adopting the above further solution is that, based on the supplementary identity information of each suspected patient, it is possible to further accurately determine whether there are patients with the same identity information in the suspected patient list.

[0023] Furthermore, the patients with the same identity information are patients who have registered on the registration platforms of at least two hospitals.

[0024] The beneficial effect of adopting the above further solution is that, through this application solution, the information of patients registered on the registration platforms of different hospitals can be shared.

[0025] Furthermore, the method further comprises:

[0026] Obtaining a patient query request for a patient to be queried, wherein the patient query request includes an identity identifier of the patient to be queried;

[0027] According to the identity identifier, basic information of the patient to be queried is queried from the suspected patient list.

[0028] The beneficial effect of adopting the above further scheme is that a patient query request based on the patient to be queried in the suspected patient list can realize the query of the basic information of the patient to be queried, so that the identity of the patient to be queried can be further confirmed based on the basic information.

[0029] In a second aspect, in order to solve the above technical problem, the present invention also provides a patient information registration device, which includes:

[0030] An acquisition module is used to obtain the identity information of the patient to be treated through the target platform;

[0031] An identity type judgment module is used to judge the identity type of the patient to be seen according to the identity information and preset identity judgment rules when the patient to be seen is not a registered person, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient;

[0032] The registration module is used to generate and save a new registration identifier for the person to be treated based on the identity information when the identity type is a new patient or a suspected patient; and to obtain and save the original registration identifier of the person to be treated based on the identity information when the identity type is a patient that can be automatically merged.

[0033] In a third aspect, in order to solve the above-mentioned technical problem, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the patient information registration method of the present application is implemented.

[0034] In a fourth aspect, in order to solve the above-mentioned technical problem, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the patient information registration method of the present application is implemented.

[0035] Additional aspects and advantages of the present application will be partially given in the following description, which will become apparent from the following description, or will be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for describing the embodiments of the present invention are briefly introduced below.

[0037] Figure 1 A schematic diagram of a process of a patient information registration method provided by an embodiment of the present invention;

[0038] Figure 2 A flowchart of another patient information registration method provided by an embodiment of the present invention;

[0039] Figure 3 A schematic diagram of the structure of a patient information registration device provided by an embodiment of the present invention;

[0040] Figure 4 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0041] The principles and features of the present invention are described below. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention.

[0042] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.

[0043] The solution provided by the embodiment of the present invention can be applied to any application scenario where the identity registration of the patient is required. The solution provided by the embodiment of the present invention can be executed by any electronic device, for example, it can be a user's terminal device, and the terminal device can be any terminal device that can install an application and can perform identity registration through the application, including at least one of the following: a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, a smart TV, and a smart car device.

[0044] The embodiment of the present invention provides a possible implementation method, such as Figure 1 As shown, a flowchart of a patient information registration method is provided. The solution can be executed by any electronic device, for example, a terminal device, or a terminal device and a server. For the convenience of description, the method provided by the embodiment of the present invention will be described below by taking the terminal device as the execution subject as an example. Figure 1 The method may include the following steps:

[0045] S10, obtaining the identity information of the patient to be treated through the target platform;

[0046] S20, if the patient to be seen is not a person who has registered on the target platform, the identity type of the patient to be seen is determined according to the identity information and the preset identity determination rules, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient;

[0047] S30, if the identity type is a new patient or a suspected patient, generating and saving a new registration identifier of the patient according to the identity information;

[0048] S40: If the identity type is that the patient can be automatically merged, then the original registration identification of the patient to be treated is obtained and saved according to the identity information.

[0049] Through the method of the present invention, based on the identity information of the patient and the preset identity judgment rules, the identity type of the patient can be accurately judged first, and different registration processes can be performed based on the identity type to realize the registration of the patient. Moreover, based on the scheme of the present application, the identity information of the patient in various hospitals can be intercommunication based on the identity type of the patient, which can not only improve the medical treatment efficiency, but also enhance the patient's medical experience.

[0050] The solution of the present invention is further described below in conjunction with the following specific embodiments. In this embodiment, a patient information registration method provided may include the following steps:

[0051] S10, obtaining the identity information of the patient to be treated through the target platform;

[0052] Among them, the patient to be seen refers to the person who wants to register for medical treatment at the hospital corresponding to the target platform. One hospital can correspond to one target platform, which is used to manage the relevant information of patients registered for treatment at the hospital. Identity information refers to information that can represent the identity of the patient to be seen, such as name, ID number, mobile phone number and other information. Identity information can be one type of information representing identity, such as name, or it can be information composed of at least two types of information representing identity, such as a combination of name and mobile phone number.

[0053] Among them, the person waiting for treatment can register on the target platform with his or her medical card or ID card so that the target platform can obtain the identity information of the person waiting for treatment. The hospital staff can also obtain the identity information of the person waiting for treatment through inquiry and enter it into the target platform. This solution does not limit the method of obtaining identity information.

[0054] S20, if the patient to be seen is not a person who has registered on the target platform, the identity type of the patient to be seen is determined according to the identity information and the preset identity determination rules, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient;

[0055] Among them, new patients refer to patients who have not registered on the target platform, automatically merged patients refer to patients who have registered on at least one platform other than the target platform, and suspected patients refer to patients who are suspected of being registered on at least one platform other than the target platform.

[0056] S30, if the identity type is a new patient or a suspected patient, generating and saving a new registration identifier of the patient according to the identity information;

[0057] Among them, the new registration identifier refers to the identity identifier of the person to be treated on the target platform. The new registration identifier can be represented by a string of characters. The specific form of the new registration identifier is not limited in this application scheme.

[0058] Optionally, if the identity type is a new patient, the patient information of the person waiting to be seen can also be returned.

[0059] S40: If the identity type is that the patient can be automatically merged, then the original registration identification of the patient to be treated is obtained and saved according to the identity information.

[0060] Among them, the original registration ID refers to the registration ID of the patient on other platforms other than the target platform.

[0061] Optionally, in the above S20, if the patient to be treated is not a person who has registered on the target platform, judging the identity type of the patient to be treated according to the identity information and a preset identity judgment rule includes:

[0062] S201, if the patient to be seen is not a person who has registered on the target platform, and there is no target identity information matching the identity information of the patient to be seen in the database, then the patient to be seen is determined to be a new patient;

[0063] The database stores the identity information of patients in multiple platforms, including the target platform. The target identity information that does not match the identity information of the patient in the database means that there is no identity information that is the same as the identity information of the patient in the database.

[0064] S202, if the patient to be seen is not a person who has registered on the target platform, and the database contains target identity information that is the same as the identity information of the patient to be seen, then determining that the identity type of the patient to be seen is a patient that can be automatically merged;

[0065] S203: If the patient is not a registered patient on the target platform, and the database contains target identity information similar to the identity information of the patient, then the identity type of the patient is determined to be a suspected patient.

[0066] The existence of target identity information in the database that is similar to the identity information of the patient to be treated means that among all the identity information in the database, there is no identity information that is the same as the identity information to be treated, but there is identity information that is similar to the identity information to be treated. In the database, the registration identifier and identity information of each patient can be stored in an indexed manner.

[0067] In this application scheme, the platforms of various hospitals can also be managed in an indexed manner.

[0068] In the present application, the method further comprises:

[0069] Determine the similarity value between the identity information of each patient in the database and the identity information of the patient to be treated;

[0070] According to each of the similarity values ​​and the threshold values ​​corresponding to different identity types, it is determined whether there is target identity information in the database that is the same as the identity information to be treated.

[0071] Optionally, for patients who can be automatically merged, the corresponding threshold may be 80%. When the similarity value is greater than 80%, it indicates that the corresponding identity type is a patient who can be automatically merged, and further determines that there is target identity information in the database that is the same as the identity information of the patient to be treated.

[0072] For suspected patients, the corresponding threshold may be 60%. When the similarity value is greater than 60% and less than 80%, it indicates that the corresponding identity type is a suspected patient, and further determines that there is target identity information in the database that is similar to the identity information of the patient to be treated.

[0073] Optionally, if the identity type is a suspected patient, the method further includes:

[0074] The identity information of the patient to be treated and the new registration identifier are stored in a suspected patient list, and the suspected patient list is displayed.

[0075] The suspected patient list stores the registration identification and identity information of suspected patients.

[0076] Optionally, the method further comprises:

[0077] According to the identity supplementary information of each suspected patient in the suspected patient list, determining whether there is a patient with the same identity information in the suspected patient list;

[0078] If so, the patient information of the patients with the same identity information is merged. After the merger, the information in the suspected patient list can be automatically updated, and the patient information that is automatically merged successfully can be returned, or the information for updating the suspected patient list can be returned.

[0079] Furthermore, the patients with the same identity information are patients who have registered on the registration platforms of at least two hospitals.

[0080] Among them, each suspected patient in the suspected patient list corresponds to a registration identifier, and the information to be merged can be the patient's registration identifier, and at least two registration identifiers of a suspected patient can be merged into a target registration identifier, and the target registration identifier can be any one of the at least two registration identifiers of the suspected patient, or the registration identifier generated first in time. After merging, the other registration identifiers of the at least two registration identifiers of the suspected patient except the target registration identifier are deleted.

[0081] Among them, the identity supplement information refers to the information that further supplements the identity information previously provided by the patient. For example, if the patient only provides one type of identity information, more types of identity information can be supplemented based on the identity supplement information to more accurately determine the identity type of the patient. Therefore, the above-mentioned identity supplement information is the identity information other than the identity information of the patient obtained by the target platform.

[0082] Optionally, if the identity information of the patient to be seen is the first type of identity information, and the first type of identity information is not the unique identity information of the patient to be seen, that is, the first type of identity information cannot characterize the uniqueness of the identity of the patient to be seen, such as name, gender, age, etc., and multiple people may have the same name, then the second type of identity information of the patient to be seen can be obtained, and the second type of identity information can be used as the supplementary identity information of the patient to be seen, wherein the second type of identity information is the unique identity information of the patient to be seen, that is, the uniqueness of the identity of the patient to be seen can be characterized by the second type of identity information, such as ID number, mobile phone number, etc. In this way, based on the second type of identity information, the identity type of the patient to be seen can be more accurately determined, and then it can be more accurately determined whether there are patients with the same identity information in the list of suspected patients.

[0083] Then, judging whether there is a patient with the same identity information in the suspected patient list according to the identity supplementary information of each suspected patient in the suspected patient list includes:

[0084] For each suspected patient in the suspected patient list, obtain the second type of identity information of the suspected patient, and use the second type of identity information as supplementary identity information;

[0085] Based on the supplementary identity information of each suspected patient, it is determined whether there is a patient with the same identity information in the suspected patient list.

[0086] Further, for each suspected patient in the suspected patient list, if part of the identity supplementary information of the suspected patient is missing, for example, the identity supplementary information is an ID card number or a mobile phone number, and the part of the information is part of the characters in the ID card number or the mobile phone number, then one implementation method of judging whether there is a patient with the same identity information in the suspected patient list based on the identity supplementary information of each suspected patient is:

[0087] Determine the similarity between the identity supplementary information of each of the suspected patients, and use the suspected patients whose similarity is greater than a set threshold as a patient pair to be merged, wherein the patient pair to be merged includes two suspected patients;

[0088] For each patient pair to be merged, determine the difference information between the two suspected patients in the patient pair to be merged, where the difference information refers to information that characterizes different characteristics between the two suspected patients, such as different genders and different ages; if the difference information characterizes the difference between the identity information represented by the first category of identity information, then based on the first category of identity information of each suspected patient in the patient pair to be merged, determine whether the two suspected patients in the patient pair to be merged are patients with the same identity information in the suspected patient list.

[0089] Further, for each suspected patient in each patient pair to be merged, if the identity supplementary information of the suspected patient is not a mobile phone number, or, for each suspected patient in each patient pair to be merged, if the identity supplementary information of the suspected patient is not a mobile phone number, and the difference information corresponding to the patient pair to be merged does not represent the difference between the identity information represented by the first type of identity information, then the place of origin of the mobile phone number of the suspected patient can be determined based on the mobile phone number, and the place of origin can be used as the first type of identity information of the suspected patient;

[0090] Based on the location of the mobile phone number corresponding to each suspected patient in the patient pair to be merged, it can be determined whether the two suspected patients in the patient pair to be merged are patients with the same identity information in the suspected patient list.

[0091] The first type of identity information and the second type of identity information may be pre-stored in a database, so that when the first type of identity information or the second type of identity information is needed, it is not necessary to obtain it from the user, but it can be directly retrieved from the database.

[0092] Furthermore, for each suspected patient in the suspected patient list, if some information is missing in the identity supplementary information of the suspected patient, the method further includes:

[0093] Sending a prompt message to the terminal interface of the suspected patient to prompt the suspected patient to complete the identity supplementary information based on the prompt message, and obtaining the completed identity supplementary information,

[0094] Based on the supplementary identity information of each suspected patient, determining whether there is a patient with the same identity information in the suspected patient list includes:

[0095] Based on the completed identity supplementary information of each suspected patient, it is determined whether there is a patient with the same identity information in the suspected patient list.

[0096] Optionally, the method further comprises:

[0097] Obtaining a patient query request for a patient to be queried, wherein the patient query request includes an identity identifier of the patient to be queried;

[0098] According to the identity identifier, basic information of the patient to be queried is queried from the suspected patient list.

[0099] Among them, the patient query request refers to the query request of the hospital staff. After the hospital staff obtains the basic information of the patient to be queried based on the patient query request, the basic information may include the identity information and other information of the patient to be queried (for example, medical information). Based on the basic information, it can be determined whether the patient to be queried is a mergeable patient.

[0100] In order to better illustrate and understand the principle of the method provided by the present invention, the scheme of the present invention is described below in conjunction with an optional specific embodiment. It should be noted that the specific implementation of each step in the specific embodiment should not be understood as a limitation to the scheme of the present invention. On the basis of the principle of the scheme provided by the present invention, other implementations that can be thought of by those skilled in the art should also be considered within the scope of protection of the present invention.

[0101] See also Figure 2 As shown in the flowchart, a patient information registration method provided in this embodiment includes the following steps:

[0102] Step 1, card reading / entering patient information (identity information). When the patient goes to the hospital corresponding to the target platform for treatment, the target platform can obtain the patient's identity information, such as name, telephone number, etc., through the patient's health card or medical card; or obtain the patient's identity information by asking the operator of the target platform;

[0103] Step 2: In the HIS system corresponding to the target platform, query the local data (database) to determine whether the patient to be seen is a newly added patient (new patient). If the patient to be seen is not a newly added patient, determine whether the patient to be seen has a registration identifier (for example, EMPI number). If so, end the process. If there is no registration identifier, or the patient to be seen is a newly added patient, call the patient registration service in the integrated platform corresponding to the target platform for subsequent registration processing.

[0104] Step 3: In the patient master index system corresponding to the target platform, the identity type of the patient to be seen is determined according to the identity information of the patient to be seen and the preset identity judgment rules, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient; Figure 2 The rules shown in match;

[0105] Step 4: If the identity type is that the patient can be automatically merged, then according to the identity information, obtain the original registration identification of the patient to be treated and save it (corresponding to Figure 2 Return to original EMPI number as shown in ).

[0106] Step 5: If the identity type of the patient to be treated is a new patient or a suspected patient, a new registration identifier of the patient to be treated is generated and saved according to the identity information; Figure 2 New EMPI numbers are generated for new patients and suspected patients shown in . The new EMPI number of the new patient and the original EMPI number of the patient that can be automatically merged are both unique identifiers that can directly indicate the identity of the patient to be treated on the target platform. For the new patient or the patient that can be automatically merged, the patient EMPI can be returned and saved. The EMPI is the new EMPI number of the new patient or the original EMPI number of the patient that can be automatically merged.

[0107] Step 6: For the new EMPI number of the suspected patient, the identity information of the patient to be treated and the new registration identifier (new EMPI number) may be stored in a suspected patient list, and the suspected patient list may be displayed.

[0108] Step 7: For the suspected patient list, it can be determined based on the method described above whether there are patients that can be automatically merged in the suspected patient list. If not, the EMPI in the suspected patient list is saved. If yes, the patient merging interface is called based on the organizational parameters corresponding to the integration platform. The integration platform calls the merging function in the patient master index system to merge the patients that can be automatically merged in the suspected patient list, that is, merge the patient information and return the merged result to the integration platform. Finally, the merged result is saved through the HIS system (corresponding to Figure 2 Save EMPI in ).

[0109] The merged patient information refers to the registration identification of the merged patient, namely the EMPI number.

[0110] Based on Figure 1 Based on the same principle as the method shown in , the embodiment of the present invention also provides a patient information registration device 20, such as Figure 3 As shown in , the patient information registration device 20 may include an acquisition module 210, an identity type determination module 220 and a registration module 230, wherein:

[0111] An acquisition module 210 is used to acquire the identity information of the patient to be treated through the target platform;

[0112] The identity type determination module 220 is used to determine the identity type of the patient to be seen according to the identity information and preset identity determination rules when the patient to be seen is not a registered person, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient;

[0113] The registration module 230 is used to generate and save a new registration identifier of the patient to be treated based on the identity information when the identity type is a new patient or a suspected patient; when the identity type is a patient that can be automatically merged, obtain and save the original registration identifier of the patient to be treated based on the identity information.

[0114] Optionally, when the patient to be seen is not a registered person, the identity type determination module 220 determines the identity type of the patient to be seen according to the identity information and a preset identity determination rule, specifically for:

[0115] If the patient is not a registered patient on the target platform, and there is no target identity information matching the identity information of the patient in the database, the patient is judged to be a new patient;

[0116] If the patient to be seen is not a person who has registered on the target platform, and the database contains target identity information that is the same as the identity information of the patient to be seen, then the identity type of the patient to be seen is determined to be a patient that can be automatically merged;

[0117] If the patient is not a registered patient on the target platform, and the database contains target identity information similar to the identity information of the patient, the identity type of the patient is determined to be a suspected patient.

[0118] Optionally, if the identity type is a suspected patient, the device further includes:

[0119] The list display module is used to store the identity information of the patient to be treated and the new registration identifier in the suspected patient list, and display the suspected patient list.

[0120] Optionally, the device further comprises:

[0121] The merging module is used to determine whether there are patients with the same identity information in the suspected patient list according to the identity supplementary information of each suspected patient in the suspected patient list; if so, the patient information of the patients with the same identity information is merged.

[0122] Optionally, the patients with the same identity information are patients who have registered on the registration platforms of at least two hospitals.

[0123] Optionally, the device further comprises:

[0124] The query module is used to obtain a patient query request for a patient to be queried, wherein the patient query request includes an identity identifier of the patient to be queried; and based on the identity identifier, query basic information of the patient to be queried from the suspected patient list.

[0125] The patient information registration device of the embodiment of the present invention can execute the patient information registration method provided by the embodiment of the present invention. The implementation principle is similar. The actions performed by each module and unit in the patient information registration device in each embodiment of the present invention correspond to the steps in the patient information registration method in each embodiment of the present invention. For the detailed functional description of each module of the patient information registration device, please refer to the description in the corresponding patient information registration method shown in the previous text, which will not be repeated here.

[0126] Among them, the above-mentioned patient information registration device can be a computer program (including program code) running in a computer device, for example, the patient information registration device is an application software; the device can be used to execute the corresponding steps in the method provided in the embodiment of the present invention.

[0127] In some embodiments, the patient information registration device provided by the embodiment of the present invention can be implemented in a combination of software and hardware. As an example, the patient information registration device provided by the embodiment of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the patient information registration method provided by the embodiment of the present invention. For example, the processor in the form of a hardware decoding processor can adopt one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.

[0128] In other embodiments, the patient information registration device provided by the embodiment of the present invention can be implemented in software. Figure 3 A patient information registration device stored in a memory is shown, which may be software in the form of a program and a plug-in, and includes a series of modules, including an acquisition module 210, an identity type determination module 220 and a registration module 230, for implementing the patient information registration method provided in an embodiment of the present invention.

[0129] The modules involved in the embodiments of the present invention may be implemented by software or hardware, wherein the name of a module does not limit the module itself in some cases.

[0130] Based on the same principle as the method shown in the embodiments of the present invention, an electronic device is also provided in the embodiments of the present invention, which may include but is not limited to: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the method shown in any embodiment of the present invention by calling the computer program.

[0131] In an alternative embodiment, an electronic device is provided, such as Figure 4 As shown, Figure 4 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present invention.

[0132] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of the present invention. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0133] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0134] The memory 4003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0135] The memory 4003 is used to store the application code (computer program) for executing the solution of the present invention, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the application code stored in the memory 4003 to implement the content shown in the above method embodiment.

[0136] The electronic device may also be a terminal device. Figure 4 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0137] An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer can execute the corresponding contents of the aforementioned method embodiment.

[0138] According to another aspect of the present invention, a computer program product or a computer program is also provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the implementation modes of the above-mentioned various embodiments.

[0139] Computer program code for performing the operations of the present invention may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0140] It should be understood that the flow charts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the module, the program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0141] The computer-readable storage medium provided by the embodiment of the present invention may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0142] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method shown in the above embodiment.

[0143] The above description is only a preferred embodiment of the present invention and an explanation of the technical principles used. Those skilled in the art should understand that the disclosure scope involved in the present invention is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present invention (but not limited to) by each other.

Claims

1. A patient information registration method, characterized in that: The following steps are involved: Obtain the identity information of the patient to be treated through the target platform; If the patient to be seen is not a person who has registered on the target platform, the identity type of the patient to be seen is determined according to the identity information and the preset identity determination rules, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient; If the identity type is a new patient or a suspected patient, a new registration identifier of the patient to be treated is generated and saved according to the identity information; If the identity type is that the patient can be automatically merged, the original registration identification of the person to be treated is obtained and saved based on the identity information.

2. The method according to claim 1, characterized in that If the patient to be treated is not a person who has registered on the target platform, judging the identity type of the patient to be treated according to the identity information and a preset identity judgment rule, including: If the patient is not a registered patient on the target platform, and there is no target identity information matching the identity information of the patient in the database, the patient is judged to be a new patient; If the patient to be seen is not a person who has registered on the target platform, and the database contains target identity information that is the same as the identity information of the patient to be seen, then the identity type of the patient to be seen is determined to be a patient that can be automatically merged; If the patient is not a registered patient on the target platform, and the database contains target identity information similar to the identity information of the patient, the identity type of the patient is determined to be a suspected patient.

3. The method according to claim 1, characterized in that If the identity type is a suspected patient, the method further includes: The identity information of the patient to be treated and the new registration identifier are stored in a suspected patient list, and the suspected patient list is displayed.

4. The method according to claim 3, characterized in that The method further comprises: According to the identity supplementary information of each suspected patient in the suspected patient list, determining whether there is a patient with the same identity information in the suspected patient list; If so, the patient information of patients with the same identity information will be merged.

5. The method according to claim 4, characterized in that The patients with the same identity information are patients who have registered on the registration platforms of at least two hospitals.

6. The method according to claim 3, characterized in that The method further comprises: Obtaining a patient query request for a patient to be queried, wherein the patient query request includes an identity identifier of the patient to be queried; According to the identity identifier, basic information of the patient to be queried is queried from the suspected patient list.

7. A patient information registration device, characterized in that: include: An acquisition module is used to obtain the identity information of the patient to be treated through the target platform; An identity type judgment module is used to judge the identity type of the patient to be seen according to the identity information and preset identity judgment rules when the patient to be seen is not a registered person, and the identity type is a new patient, a patient that can be automatically merged, or a suspected patient; The registration module is used to generate and save a new registration identifier for the person to be treated based on the identity information when the identity type is a new patient or a suspected patient; and to obtain and save the original registration identifier of the person to be treated based on the identity information when the identity type is a patient that can be automatically merged.

8. The device according to claim 7, characterized in that When the patient to be seen is not a registered person, the identity type determination module determines the identity type of the patient to be seen according to the identity information and the preset identity determination rule, specifically for: If the patient is not a registered patient on the target platform, and there is no target identity information matching the identity information of the patient in the database, the patient is judged to be a new patient; If the patient to be seen is not a person who has registered on the target platform, and the database contains target identity information that is the same as the identity information of the patient to be seen, then the identity type of the patient to be seen is determined to be a patient that can be automatically merged; If the patient is not a registered patient on the target platform, and the database contains target identity information similar to the identity information of the patient, the identity type of the patient is determined to be a suspected patient.

9. An electronic device, characterized in that: The method comprises 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 1 to 6 when executing the computer program.

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

Images