A patient identity binding method, system, device and storage medium

Abstract

The application discloses a patient identity binding method, system, device and storage medium, wherein the method comprises the following steps: obtaining first identity information of a first terminal application required by a user input target patient outpatient number; determining second identity information of a second terminal application that has been bound according to the target patient outpatient number; determining that the second identity information is different from the first identity information, and the target patient outpatient number is an outpatient number registered on the same day, unbinding the target patient outpatient number and the second identity information, and binding the target patient outpatient number and the first identity information of the first terminal application. The method can improve user experience. The application can be widely applied in the field of information processing technology.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information processing, and in particular to a patient identity binding method, system, device and storage medium. BACKGROUND

[0002] In today's Internet era, it is a very common means to use the authorization id identity of the mobile terminal application (such as the openid of WeChat, which is also referred to as openid below) for identity recognition and binding, especially in medical applications. Because many professional information and events make patients confused and disoriented, information technology means must be used for processing and notification, etc. Therefore, the identity of the patient must be confirmed through identity binding, and many private information of the patient must also be confirmed through identity binding to accurately process and convey. At present, the means in the process of identity binding are various, and the commonly used ones are: patient mobile phone verification, which sends a verification code to the service end through the patient's own mobile phone after pushing the verification code or requiring the patient to send the verification code to the service end, and then comparing the current mobile phone number and the mobile phone number in the registration information and comparing the verification code, so as to accurately bind the mobile phone number used by the patient, thereby associating the openid with the current outpatient number of the patient, and the identity binding is successful. However, the existing technology has the following defects: (1) the registration mobile phone number does not correspond (the registration staff inputs incorrectly, the mobile phone number is changed to that of another person after being disabled, etc.), which will cause many errors and troubles in the process. Therefore, a new patient identity binding method is urgently needed. SUMMARY

[0003] The present application aims to at least solve one of the technical problems existing in the prior art.

[0004] To this end, one purpose of the embodiments of the present application is to provide a patient identity binding method, system, device and storage medium, which can improve user experience.

[0005] In order to achieve the above technical purpose, the technical solutions adopted by the embodiments of the present application include:

[0006] acquire first identity information of a first terminal application required by a user to input a target patient clinic number; determine second identity information of a second terminal application that has been bound according to the target patient clinic number; determine that the second identity information is different from the first identity information, and that the target patient clinic number is a clinic number registered on the same day, unbind the target patient clinic number and the second identity information, and bind the target patient clinic number and the first identity information of the first terminal application; determine that the target patient clinic number is a first clinic number, and push service-type information to the target patient clinic number or the first terminal application; the first clinic number is used to represent a clinic number without sensitive information permission; the service-type information is used to represent information without sensitive content; determine that the target patient clinic number is a second clinic number; and push sensitive information to the target patient clinic number or the first terminal application; the second clinic number is used to represent a clinic number with sensitive information permission.

[0007] In addition, according to the patient identity binding method in the above-mentioned embodiment of the application, the following additional technical features can also be included:

[0008] Further, in the embodiment of the application, the first information is pushed to the first terminal application.

[0009] Further, in the embodiment of the application, the step of determining the second identity information of the second terminal application that has been bound according to the target patient clinic number specifically includes: acquiring the target patient clinic number input by a user on a front-end page and the clinic number input by the user on a front-end chat interface, monitoring interaction records of the target patient clinic number with a public account, and determining the second identity information of the second terminal application that has been bound to the target patient clinic number.

[0010] Further, in the embodiment of the application, the second information is pushed to the second terminal application that has been unbound.

[0011] Further, in the embodiment of the application, the target patient clinic number is determined to be a clinic number not registered on the same day, the first terminal application is bound for a number of times, and when the number of times is greater than a preset threshold, a third message is pushed to a background administrator.

[0012] On the other hand, the embodiment of the application also provides a patient identity binding system, which includes:

[0013] An acquisition unit is configured to acquire first identity information of a first terminal application required by a user to input a target patient clinic number;

[0014] A first processing unit is configured to determine second identity information of a second terminal application that has been bound according to the target patient clinic number;

[0015] A second processing unit is configured to determine that the second identity information is different from the first identity information and that the target patient clinic number is a clinic number registered on the same day, to unbind the second terminal application from the second identity information, and to bind the target patient clinic number to the first terminal application identity information.

[0016] Further, the embodiment of the present application further comprises a first pushing unit, which is configured to push first information to the first terminal application.

[0017] Further, the embodiment of the present application further comprises a second pushing unit, which is configured to push second information to the second terminal application which has been unbound.

[0018] In another aspect, the present application further provides a patient identity binding device, comprising:

[0019] at least one processor;

[0020] at least one memory configured to store at least one program;

[0021] When the at least one program is executed by the at least one processor, the at least one processor implements the patient identity binding method according to any one of the summary.

[0022] In addition, the present application further provides a storage medium, which stores processor-executable instructions, and the processor-executable instructions are used to execute the patient identity binding method according to any one of the above when executed by a processor.

[0023] The advantages and beneficial effects of the present application will be partially given in the following description, partially will become obvious from the following description, or will be learned through the practice of the present application:

[0024] The present application can complete the binding of patient identity through the clinic number input by the user and the registration record on the same day, can avoid using a mobile phone to bind the patient identity, simplifies the binding process, and improves the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0025] Figure 1 FIG. 1 is a schematic diagram of the steps of a patient identity binding method according to an embodiment of the present application;

[0026] Figure 2 FIG. 2 is a structural schematic diagram of a patient identity binding system according to an embodiment of the present application;

[0027] Figure 3 FIG. 3 is a structural schematic diagram of a patient identity binding device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] The principles and processes of the patient identity binding method, system, device and storage medium in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0029] Referring to Figure 1 The present application provides a patient identity binding method, comprising the following steps:

[0030] S1, obtaining first identity information of a first terminal application required by a user input target patient outpatient number;

[0031] S2, determining second identity information of a second terminal application that has been bound according to the target patient outpatient number;

[0032] S3, determining that the second identity information is different from the first identity information, and the target patient outpatient number is an outpatient number registered on the same day, unbinding the second terminal application and the second identity information, and binding the target patient outpatient number and the first terminal application identity information.

[0033] S4, determining that the target patient outpatient number is a first outpatient number, and pushing service type information to the target patient outpatient number or the first application terminal; the first outpatient number is used to represent an outpatient number without sensitive information permission; the service type information is used to represent information without sensitive content.

[0034] S5, determining that the target patient outpatient number is a second outpatient number, and pushing sensitive information to the target patient outpatient number or the first application terminal; the second outpatient number is used to represent an outpatient number with sensitive information permission.

[0035] Further, in some embodiments of the present application, it further comprises determining that the target patient outpatient number is a first outpatient number, and pushing service type information to the target patient outpatient number or the first application terminal; the first outpatient number is used to represent an outpatient number without sensitive information permission; the service type information is used to represent information without sensitive content; determining that the target patient outpatient number is a second outpatient number, and pushing sensitive information to the target patient outpatient number or the first application terminal; the second outpatient number is used to represent an outpatient number with sensitive information permission.

[0036] Specifically, in this step, the outpatient number and identity information are bound, and it can be determined whether the outpatient number of the target patient has the permission of sensitive information. When it is determined that the outpatient number does not have the permission of sensitive information, the sensitive information query (such as downloading of test report with name, modification of sensitive information with name, etc.) can be opened immediately after the accurate verification of the random code pushed during the registration is submitted by hand. If the user does not manually open it immediately, the sensitive information permission is automatically opened within a set time threshold (such as 1 day). Before the sensitive information is opened, a short message is pushed to inform that the identity is bound to the outpatient number. If it is determined that the user is the person himself / herself, the preset link pushed can be clicked to automatically open it. In particular, if the first identity information is empty, i.e., it has never been bound, the outpatient number and the second identity information can be directly bound without the need to determine whether the registration is successful or not.

[0037] After the binding is completed, the system can push service type information and access service type page to the mobile phone number corresponding to the second identity information of the target patient or the first application terminal. The service type information and the service type page are used to represent that there is no sensitive content and permission, such as a prompt information of successful registration.

[0038] In addition, when the user registers, the system can generate a first signature and push it to the mobile phone number of the second terminal application. After a first time threshold is exceeded, a first verification link is generated, and the first terminal application message can be pushed to the first identity. Through the first link and the first signature, further verification can be performed. After the verification, the system can push a designated message and an access real person association page to the first terminal application. The designated message and the access real person association page can represent that there is sensitive information content and permission, such as identity information or disease information.

[0039] Further, in some embodiments of the present application, the first information is a binding success information.

[0040] Further, in some embodiments of the present application, the second information is a binding failure information.

[0041] Further, in some embodiments of the present application, the first terminal application is bound for a plurality of times, and when the number of binding times is greater than a preset threshold, a third information is pushed to a background administrator. The third information is a binding abnormality or other notification information, which can be pushed through email or other ways.

[0042] Further, in some embodiments of the present application, the step of determining the second identity information of the second terminal application that has been bound according to the outpatient number of the target patient specifically includes:

[0043] By acquiring the target patient clinic number input by the user on the front-end page or by acquiring the clinic number input by the user on the front-end chat interface, the second identity information of the second terminal application that has bound the target patient clinic number is determined by monitoring the interaction record of the target patient clinic number with the public number.

[0044] The patient identity binding method of the present application will be described below in conjunction with specific embodiments.

[0045] After the patient is registered, open id binding can be performed immediately. Open id is a WeChat identity information. Each WeChat corresponds to an open id. Open id does not leak the personal privacy and personal WeChat number of WeChat. In the binding process, the patient can enter the authorization page through the front-end page to obtain the identity open id, then enter the binding page, input the user's clinic number according to the requirements, and submit it to complete the binding. Alternatively, the patient can directly input his / her own clinic number in the application through the chat interface. The identity open id and the clinic number can be obtained by monitoring the interaction record of the identity with the public number, and the binding is completed. After the binding is completed, the background will push the message of successful binding to the terminal corresponding to the open id. After the binding is completed, the user terminal or platform on the front-end can initially receive the targeted push. The sensitive information in the pushed message will be actively shielded by the system code, which can prevent others from seeing the information and causing the leakage of sensitive information.

[0046] Both of the above two methods can be bound successfully. However, if it is detected that the clinic number input by the user has been bound by the open id corresponding to the other application terminal, further automatic verification will be performed. The verification method is as follows: the clinic number can be the patient clinic number registered on the same day, which can be changed to bind other identities. After the change is completed, the background will push the message of successful binding to the terminal corresponding to the new open id. If there is no registration on the same day, the binding fails, and the clinic number and the originally bound open id are not switched. The background will monitor the number of binding failures. If the number of binding failures is greater than a certain preset threshold, such as 3 times, the user will be prompted to contact the administrator. Specifically, if the open id corresponding to the clinic number is abc at the beginning, the open id of the application is xyz when the user inputs the clinic number. Since abc has bound the clinic number 123 at the beginning, the identity of the open id xyz now wants to bind the same clinic number 123. At this time, abnormal binding is triggered. By judging whether the clinic number has a registration record today, if there is a record, the binding of abc and 123 is triggered, and the binding of xyz and 123 is completed.

[0047] The hospital system at the time of registration will uniformly and fixedly push a random verification code to the mobile phone number reserved on the registration information through SMS, which can be used for identity verification on the official fixed page of the mobile front end; if the above-mentioned user binds the existing record with the open id with the outpatient number registered on the same day, the system will push a message to inform the owner of the original record that the openid has been replaced by a new binding identity, and if the user is unaware, the user can contact the official as soon as possible or further verify the reserved verification code to replace and lock; after successful verification, not only can the background push messages to the front-end platform and mobile phone, but also the user can actively query his own relevant information and sensitive information and test reports through the mobile phone or platform, in addition, in order to prevent malicious binding and verification of the user, within one hour (such as one hour, which can also be set to 0) after the above-mentioned binding is completed, the verification through the verification code is not allowed.

[0048] All events of identity replacement are pushed to the binding open id of the administrator in real time, and identity management and locking can be performed through the list, and for serious malicious behavior, legal channels can be reasonably held accountable;

[0049] The above-mentioned binding is only used for accepting service type non-adaptive information associated directional push (such as pushing test results, but without sensitive fields such as name), if sensitive information needs to be pushed, further permission needs to be opened, which can be accurately verified by manually submitting the random code pushed during the above-mentioned registration, and the sensitive information query (sensitive information such as name test report download, sensitive information modification with name, etc.) is opened immediately after submission, if the user does not manually open it immediately, the sensitive information permission is automatically opened within a set time threshold (such as 1 day), before the sensitive information is opened, a push message is sent to inform that the identity is bound to the outpatient number, if it is determined that the user is the person himself, the preset link can be clicked to automatically open. If it is determined that it is not the user himself, the identity can also be disabled through the link, if the registration mobile phone number cannot be delivered or the preset link has no click record, after exceeding the second time threshold such as 1 hour, the system informs the registration clerk through the next registration of the patient to inform the patient, at this time the registration clerk confirms and automatically opens the sensitive permission; the first threshold time is set to prevent someone from seeing the registration of a patient on the same day and maliciously binding, although the patient will receive a reminder that someone else has bound at this time, it may not be processed in time, so a threshold is set to delay verification to prevent malicious viewing of sensitive information.

[0050] In addition, with reference to Figure 2 , and Figure 1Corresponding to the method, the embodiments of the present application also provide a patient identity binding system, comprising: an acquisition unit 101, configured to acquire first identity information of a first terminal application required by a user input target patient outpatient number; a first processing unit 102, configured to determine second identity information of a second terminal application that has been bound according to the target patient outpatient number; a second processing unit 103, configured to determine that the second identity information is different from the first identity information, and the target patient outpatient number is an outpatient number registered on the same day, unbind the second terminal application from the second identity information, and bind the target patient outpatient number and the first terminal application identity information.

[0051] Further, in some embodiments of the present application, the patient identity binding system further comprises a first pushing unit; the first pushing unit is configured to push first information to the first terminal application.

[0052] Further, in some embodiments of the present application, the patient identity binding system further comprises a second pushing unit, and the second pushing unit is configured to push second information to the second terminal application that has been unbound.

[0053] Corresponding to the method, the embodiments of the present application also provide a patient identity binding device, and the specific structure can refer to the patient identity binding method Figure 1 Corresponding to the method, the embodiments of the present application also provide a patient identity binding device, and the specific structure can refer to the patient identity binding method Figure 3 , comprising:

[0054] at least one processor 1001;

[0055] at least one memory 1002, configured to store at least one program;

[0056] When the at least one program is executed by the at least one processor, the at least one processor implements the patient identity binding method.

[0057] The contents in the above method embodiments are all applicable to the device embodiments, the device embodiments specifically implement the functions same as those of the above method embodiments, and achieve the same beneficial effects as those of the above method embodiments.

[0058] Corresponding to the method, the embodiments of the present application also provide a patient identity binding device, and the specific structure can refer to the patient identity binding method Figure 1 Corresponding to the method, the embodiments of the present application also provide a storage medium, wherein the storage medium stores processor-executable instructions, and the processor-executable instructions are used for executing the patient identity binding method when executed by a processor.

[0059] In some alternative embodiments, the function / operations described in the block diagrams can not occur in the order described in the operational illustrations. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality / operations involved. Also, although the embodiments presented in the flow diagrams are shown as a sequence of operations, it is to be understood that the logical flow is merely illustrative of alternative embodiments. The disclosed methods are not limited to the order of operations presented herein. Alternative embodiments can be contemplated where the order of operations is changed, and where sub operations described as part of a larger operation are executed in a different order, or are executed concurrently.

[0060] Further, while the present application has been described in the context of functional modules, it is to be understood that one or more of the functions and / or features can be integrated in a single physical device and / or software module, or one or more functions and / or features can be implemented in separate physical devices or software modules. It is also to be understood that detailed discussion of the actual implementation of each module is unnecessary to an understanding of the present application. Rather, the actual implementation is within the routine of an engineer's knowledge given the property, functionality and internal relationships of the various functional modules disclosed herein. Accordingly, the present application is not limited to the specific embodiments illustrated herein, but is amenable to any number of possible embodiments within the scope of the claims below. It is therefore to be understood that any alterations and / or modifications to the specifics of the illustrated embodiments, and those discussed in terms of the preferred embodiments, can be practiced within the scope of the claims below. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.

[0061] If the functions are implemented in software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes a number of programs used to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0062] The logic and / or steps represented in the flow diagrams or otherwise described herein, for example, can be embodied in non-transitory computer- readable media, executed by a program executing system, apparatus, or device, such as a computer-based system, a processor-based system, or other system that can fetch the program (from the system, apparatus, or device) and execute the program, or in conjunction with such a program executing system, apparatus, or device. For the purposes of this specification, a "computer-readable medium" can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the program executing system, apparatus, or device.

[0063] More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can also be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for example, via optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and stored in a computer memory.

[0064] It should be understood that aspects of the application can be implemented in hardware, software, firmware, or combinations thereof. In the above embodiments, various steps or methods can be implemented in software or firmware that is stored in memory and executed by a suitable

[0065] In the above description of the present specification, reference has been made to descriptive terms such as "one embodiment," "another embodiment," "some embodiments," or the like, which can describe specific features, structures, materials, or characteristics included in at least one embodiment of the application. The illustrative descriptions are not intended to exclude other embodiments or examples that execute the same, equivalent, or similar functions. Moreover, the described specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0066] While the embodiments of the application have been shown and described, it is to be understood that the embodiments can be varied, modified, substituted and changed by those skilled in the art without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.

[0067] The above is a specific description of the preferred embodiments of the application, but the application is not limited to the described embodiments, and those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the application, and these equivalent modifications or substitutions are all included in the scope defined by the claims of the application.

Claims

1. A method for binding patient identity, characterized in that, Includes the following steps: Obtain the first identity information of the first terminal application required for the user to input the outpatient number of the target patient; The first identity information is openid; Based on the target patient's outpatient number, determine the second identity information of the bound second terminal application; If it is determined that the second identity information is different from the first identity information, and the target patient's outpatient number is an outpatient number registered on the same day, the binding between the target patient's outpatient number and the second identity information is released, and the target patient's outpatient number is bound to the first identity information of the first terminal application; Once the target patient's outpatient number is identified as the first outpatient number, service information is pushed to the target patient's outpatient number or the first terminal application. The first outpatient number is used to identify outpatient numbers that do not have access to sensitive information. The service-type information is used to characterize information that does not contain sensitive content; The target patient's outpatient number was determined to be the second outpatient number; Push sensitive information to the target patient's outpatient number or the first terminal application; The second outpatient number is used to identify outpatient numbers with access to sensitive information.

2. The patient identity binding method according to claim 1, characterized in that, It also includes pushing the first information to the first terminal application.

3. The patient identity binding method according to claim 1, characterized in that, The step of determining the second identity information of the bound second terminal application based on the target patient's outpatient number specifically includes: By obtaining the target patient's outpatient number entered by the user on the front-end page and the outpatient number entered by the user in the front-end chat interface, and by monitoring the interaction records between the target patient's outpatient number and the official account, the second identity information of the second terminal application that has been bound to the target patient's outpatient number can be determined.

4. The patient identity binding method according to claim 1, characterized in that, It also includes pushing second information to a second terminal that has been unbound.

5. The patient identity binding method according to claim 1, characterized in that, It also includes determining that the target patient's outpatient number is not an outpatient number registered on the same day, monitoring the number of times the first terminal application is bound, and pushing a third message to the backend administrator when the number of bindings exceeds a preset threshold.

6. A patient identity binding system, characterized in that, include: The acquisition unit is used to acquire the first identity information of the first terminal application required for the user to input the outpatient number of the target patient; The first identity information is openid; The first processing unit is used to determine the second identity information of the bound second terminal application based on the outpatient number of the target patient; The second processing unit is used to determine that the second identity information is different from the first identity information, and that the target patient's outpatient number is an outpatient number registered on the same day, to unbind the second terminal application from the second identity information, and to bind the target patient's outpatient number to the identity information of the first terminal application.

7. A patient identity binding system according to claim 6, characterized in that, It also includes a first push unit; the first push unit is used to push first information to the first terminal application.

8. A patient identity binding system according to claim 6, characterized in that, It also includes a second push unit; the second push unit is used to push second information to the unbound second terminal.

9. A patient identity binding device, characterized in that... include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a patient identity binding method as described in any one of claims 1-5.

10. A storage medium storing processor-executable instructions, characterized in that, The processor-executable instructions, when executed by the processor, are used to perform a patient identity binding method as described in any one of claims 1-5.

Images