Service pushing method and device for medical scenario

Abstract

The embodiment of the present specification provides a service pushing method and device for a medical scene, wherein the service pushing method for a medical scene comprises the following steps: firstly, receiving a medical insurance code access request sent by a user terminal, and sending the request to a medical insurance platform; after the medical insurance platform queries the medical insurance code of the user and returns the medical insurance code information, receiving the medical insurance code information returned by the medical insurance platform, and sending the medical insurance code information to the user terminal to generate a medical insurance code according to the medical insurance code information and display the medical insurance code to a medical institution; after the medical institution obtains the medical insurance code and sends the medical insurance code to the medical insurance platform, obtaining the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution; querying the service pushing configuration of the medical scene of the medical institution according to the medical institution identifier, and generating the pushing content of the medical institution based on the service pushing configuration and sending the pushing content to the user terminal.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a service push method and device for a medical scenario. Background Technology

[0002] With the development of internet technology, electronic medical insurance vouchers have been widely used. Like ordinary paper medical insurance vouchers, electronic medical insurance vouchers have a unified code issued by medical insurance institutions, and therefore have the same validity. As a form of electronic medical insurance voucher, the medical insurance code allows users to verify their identity or settle medical insurance when seeking medical treatment or purchasing medicine offline. Improving the user experience when verifying identity or settling medical insurance at medical institutions is the direction for medical institutions to provide services. Summary of the Invention

[0003] This specification provides one or more embodiments of a service push method for a medical scenario, comprising: receiving a user's medical insurance code access request sent by a user terminal and sending it to a medical insurance platform; receiving medical insurance code information returned by the medical insurance platform and sending the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and displaying it to a medical institution; obtaining a medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution; querying the medical institution's service push configuration for the medical scenario based on the medical institution identifier, and generating push content for the medical institution based on the service push configuration and sending it to the user terminal.

[0004] This specification provides one or more embodiments of another service push method for a medical scenario, including: sending a user's medical insurance code access request to a server based on an access instruction submitted by the user through the medical insurance service; receiving the user's medical insurance code information obtained from the medical insurance platform from the server, generating a medical insurance code based on the medical insurance code information, and displaying it to a medical institution; receiving push content from the server for the medical institution; the push content is generated after the medical insurance platform decodes the medical insurance code information submitted by the medical institution, based on the service push configuration of the medical scenario corresponding to the medical institution identifier returned by the decoding.

[0005] This specification provides one or more embodiments of a service push device for a medical scenario, comprising: an access request sending module configured to receive a user's medical insurance code access request sent by a user terminal and send it to a medical insurance platform; an information sending module configured to receive medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to a medical institution; an identifier acquisition module configured to acquire a medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution; and a push content sending module configured to query the medical institution's service push configuration for the medical scenario based on the medical institution identifier, and generate push content for the medical institution based on the service push configuration and send it to the user terminal.

[0006] This specification provides one or more embodiments of a service push device for another medical scenario, comprising: an access request sending module configured to send a user's medical insurance code access request to a server based on an access instruction submitted by the user through the medical insurance service; a medical insurance code display module configured to receive the user's medical insurance code information obtained from the medical insurance platform and sent by the server, generate a medical insurance code based on the medical insurance code information, and display it to a medical institution; and a push content receiving module configured to receive push content from the medical institution sent by the server; the push content is generated after the medical insurance platform decodes the medical insurance code submitted by the medical institution, based on the service push configuration of the medical scenario corresponding to the medical institution identifier returned by the decoding.

[0007] This specification provides one or more embodiments of a service push device for a medical scenario, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive a user's medical insurance code access request sent by a user terminal and send it to a medical insurance platform; receive medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to a medical institution; obtain a medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution; query the medical institution's service push configuration for the medical scenario based on the medical institution identifier, and generate push content for the medical institution based on the service push configuration and send it to the user terminal.

[0008] This specification provides one or more embodiments of a service push device for another medical scenario, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: send a user's medical insurance code access request to a server based on an access instruction submitted by the user through a medical insurance service; receive the user's medical insurance code information obtained from a medical insurance platform and sent by the server, generate a medical insurance code based on the medical insurance code information, and display it to a medical institution; receive push content from the medical institution sent by the server; the push content is generated after the medical insurance platform decodes the medical insurance code submitted by the medical institution, based on the medical institution identifier returned by the decoding, and according to the service push configuration of the medical scenario for the medical institution.

[0009] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions. When executed by a processor, these computer-executable instructions implement the following process: receiving a user's medical insurance code access request sent by a user terminal and sending it to a medical insurance platform; receiving medical insurance code information returned by the medical insurance platform and sending the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and displaying it to a medical institution; obtaining a medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution; querying the service push configuration for the medical scenario of the medical institution based on the medical institution identifier, and generating push content for the medical institution based on the service push configuration and sending it to the user terminal.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: sending a user's medical insurance code access request to a server based on an access instruction submitted by the user through the medical insurance service; receiving the user's medical insurance code information obtained from the medical insurance platform from the server, generating a medical insurance code based on the medical insurance code information, and displaying it to a medical institution; receiving push content from the medical institution sent by the server; the push content is generated after the medical insurance platform decodes the medical insurance code submitted by the medical institution, based on the service push configuration of the medical scenario corresponding to the medical institution identifier returned by the decoding. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 A schematic diagram illustrating an application scenario of a service push system for a medical setting, provided in one or more embodiments of this specification.

[0013] Figure 2 A flowchart illustrating a service push method for a medical scenario provided in one or more embodiments of this specification;

[0014] Figure 3 A timing diagram illustrating the processing of a service push method for a medical scenario applied to hospital payment, provided by one or more embodiments of this specification.

[0015] Figure 4 A timing diagram illustrating the processing of a service push method for a medical scenario applied to hospital identity verification, provided in one or more embodiments of this specification.

[0016] Figure 5 A flowchart illustrating a service push method for another medical scenario provided in one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram of an embodiment of a service push device for a medical scenario provided by one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of another embodiment of a service push device for a medical scenario provided by one or more embodiments of this specification;

[0019] Figure 8 A schematic diagram of the structure of a service push device for a medical scenario provided in one or more embodiments of this specification;

[0020] Figure 9 This is a schematic diagram of the structure of a service push device for another medical scenario provided in one or more embodiments of this specification. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0022] Figure 1This is a schematic diagram illustrating the application scenario of the service push system for medical scenarios provided in one or more embodiments of this specification, such as... Figure 1 As shown, the system includes: server 102, user terminal 104, medical institution terminal 106, and medical insurance platform 108;

[0023] Server 102 can be a standalone server or a server cluster consisting of multiple servers. Server 102 is used to interact with medical institution terminals and medical insurance platform servers to provide medical insurance payment or identity verification services to clients.

[0024] User terminal 104 can be a smartphone, tablet computer, e-book reader, VR-based information interaction device, laptop computer, desktop computer, etc. User terminal 102 can have an application client or a browser installed, and access the web client of the application through the browser. In this embodiment of the invention, the application client and the web client are collectively referred to as the client, and will not be specifically stated below. The client can be a client with electronic redemption function, or a client with both electronic redemption and social functions, or a client with both electronic redemption and game functions, or a client with both electronic redemption and email functions, or a client with both electronic redemption and financial management functions, or a client with both electronic redemption and information query services. When the client is a client with both electronic redemption and other functions, the user's electronic redemption account and other electronic accounts are mutually bound or associated. Merchant subroutines can run in the client, and the user's account in the merchant subroutines can be mutually bound or associated with the user's account in the client.

[0025] The medical institution terminal 106 can be a service terminal for medical services designated by medical insurance, such as hospitals and pharmacies. Specifically, the medical institution terminal 106 can be a self-service payment terminal in a hospital or a cash register computer in a pharmacy.

[0026] The medical insurance platform 108 can include platforms corresponding to the National Healthcare Security Administration, the Ministry of Human Resources and Social Security, local medical insurance bureaus, and local human resources and social security departments. Specifically, the medical insurance platform 108 can include a medical insurance settlement system and a medical insurance card system. The medical insurance settlement system can have functional modules such as medical insurance pre-settlement, medical insurance settlement, settlement inquiry, medical insurance cancellation, cancellation inquiry, medical insurance pre-refund, medical insurance refund, refund inquiry, and reconciliation. The medical insurance card system can specifically include functional modules such as account login, medical insurance card binding, account registration, and medical insurance unbinding.

[0027] In the application of the service push system in the medical scenario, the user sends a medical insurance code access request to the server 102 through the user terminal 104. The server 102 forwards the medical insurance code access request to the medical insurance platform 108. The medical insurance platform 108 queries the medical insurance code information according to the medical insurance code access request and returns the medical insurance code information to the server 102. The server 102 sends the medical insurance code information to the user terminal 104 to display the medical insurance code. The medical institution terminal 106 collects the medical insurance code displayed by the user terminal 104 and sends the medical insurance code information to the medical insurance platform 108 for user payment or verification.

[0028] This specification provides an example of a service push method in a medical scenario:

[0029] The service push method for medical scenarios provided in this application determines the service push configuration of a medical institution in a medical scenario through a medical institution identifier, and generates push content corresponding to the medical institution based on the service push configuration of the medical scenario. Specifically, after receiving a user's medical insurance code access request sent by the user terminal, a medical insurance code access request is sent to the medical insurance platform, the medical insurance platform returns the medical insurance code information, and the medical insurance code information is sent to the user terminal so that the user terminal generates a medical insurance code based on the medical insurance code information and displays it to the medical institution. The method obtains the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution, queries the medical institution's service push configuration for the medical scenario based on the medical institution identifier, and generates push content for the medical institution based on the service push configuration of the medical scenario and sends it to the user terminal. This satisfies the medical institution's need to target push content to users using medical insurance codes, improves the convenience of service push in medical scenarios, and further meets the diverse needs of users.

[0030] Reference Figure 2 The service push method for medical scenarios provided in this embodiment specifically includes steps S202 to S208.

[0031] Step S202: Receive the user's medical insurance code access request sent by the user terminal and send it to the medical insurance platform.

[0032] The implementation process of the service push method in a medical scenario provided in this embodiment can be executed by the server. The implementation process of the service push method in a medical scenario provided in another embodiment of the medical scenario provided below can be executed by the user terminal. The two can cooperate with each other during execution. Therefore, when reading the above implementation process, you can refer to the corresponding content of the following method embodiment. Correspondingly, when reading the following implementation process, you can also refer to the corresponding content of the above method embodiment.

[0033] The medical insurance code described in this embodiment includes the barcode and / or QR code of the electronic medical insurance certificate. The electronic medical insurance certificate is an electronic credential for medical insurance payers to make medical insurance payments and participate in medical insurance services. It corresponds one-to-one with the payer's physical medical insurance certificate and can be activated and used by the payer through third-party applications or medical insurance service platforms. The activation and association process of the electronic medical insurance certificate requires data processing integration with the medical insurance system. The medical insurance platform maintains the user's medical insurance account and provides medical insurance settlement and identity verification capabilities. The medical insurance services include subroutines of third-party applications or medical insurance-related services provided by third-party applications, such as medical insurance information query services and medical insurance payment services. The user identity information includes the user's name and / or identity certificate number.

[0034] In practice, during the user's identity verification or payment process, the user terminal displays the medical insurance code for identity verification or payment. During the process of the user displaying the medical insurance code, the user terminal sends the user's medical insurance code access request according to the access instruction submitted by the user through the medical insurance service. Here, the system receives the user's medical insurance code access request sent by the user terminal and sends it to the medical insurance platform. The medical insurance platform receives the medical insurance code access request sent by the server and queries the user's medical insurance certificate.

[0035] Step S204: Receive the medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution.

[0036] The medical insurance code information includes information related to the medical insurance code. Optionally, the medical insurance code information includes the medical insurance code value. The medical institution includes institutions that provide medical services, such as hospitals and pharmacies.

[0037] In practice, the server receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal. After receiving the user's medical insurance code information obtained from the medical insurance platform from the server, the user terminal generates a medical insurance code based on the medical insurance code information and displays it to the medical institution for identity verification or payment.

[0038] Furthermore, in an optional implementation of this embodiment, after receiving the medical insurance code information returned by the medical insurance platform and sending the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution, an association relationship is established between the medical insurance code information and the user's user identity information. This allows the medical insurance platform to determine the user's identity information based on the association relationship after decoding the medical insurance code to obtain the medical insurance code information, and to issue the medical institution's identifier based on the user's identity information.

[0039] Step S206: Obtain the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution.

[0040] The medical institution identifier includes a unique institution code generated according to the coding standards specified by the National Healthcare Security Administration. The service push configuration for the medical scenario includes configuration of either the service push format or the service push content.

[0041] In this embodiment, the medical insurance code can be used for identity verification and medical expense payment. The following sections will describe these two processes in detail.

[0042] (1) The medical insurance code is used for identity verification.

[0043] In one optional implementation of this embodiment, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information and sends an identity verification request carrying the medical insurance code information to the medical insurance platform.

[0044] The medical insurance platform decodes the medical insurance code information to obtain the user's identity information and returns the user's identity information to the medical institution for identity verification.

[0045] Optionally, the medical insurance platform decodes the medical insurance code information to obtain user identity information, and after returning the user identity information to the medical institution, queries the medical institution's medical institution identifier and issues it.

[0046] Specifically, users present their medical insurance code to medical institutions via their user terminals; the medical institutions read the medical insurance information from the code and send a verification request carrying the code information to the medical insurance platform; the medical insurance platform decodes the code information to obtain the user's identity information and returns it to the medical institution; the medical institution receives the user's identity information and performs verification. For example, when a user registers at a medical institution, they present their medical insurance code to the institution via their user terminal. The medical institution reads the code value and sends a verification request carrying the code value to the medical insurance platform. The medical insurance platform decodes the code value to obtain the user's identity information and returns it to the medical institution, which then performs verification.

[0047] (2) The medical insurance code is used for medical expense payment.

[0048] In one optional implementation of this embodiment, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information and sends a payment request carrying the medical insurance code information to the medical insurance platform.

[0049] The medical insurance platform responds to the payment request by performing the following operations:

[0050] The user's identity information is obtained by decoding the medical insurance code information;

[0051] The bill amount carried in the payment request will be deducted from the medical insurance account corresponding to the user's identity information.

[0052] The payment result will be returned to the medical institution after payment is completed.

[0053] Specifically, the user presents their medical insurance code to the medical institution through their user terminal; the medical institution reads the medical insurance information from the medical insurance code and sends a payment request carrying the medical insurance code information to the medical insurance platform; the medical insurance platform decodes the medical insurance code information to obtain the user's identity information, and deducts the payment from the medical insurance account corresponding to the user's identity information based on the bill amount carried in the payment request, and returns the payment result to the medical institution after the payment is completed.

[0054] Step S208: Query the service push configuration of the medical institution's medical scenario based on the medical institution identifier, and generate push content for the medical institution based on the service push configuration and send it to the user terminal.

[0055] After obtaining the medical institution identifier issued by the medical insurance platform, in order to achieve the accuracy of service push in medical scenarios and realize targeted service delivery, that is, to push the services provided by the medical institution (the object to be displayed with the medical insurance code) to the user terminal, in this step, the service push configuration of the corresponding medical institution in medical scenarios is queried according to the medical institution identifier, and the push content of the medical institution is generated and sent to the user terminal based on the service push configuration of the medical scenario.

[0056] In the specific execution process, in order to ensure that the push content sent to the user terminal matches the medical institution, in an optional implementation method provided in this embodiment, the push content of the medical institution is generated in the following way:

[0057] Based on the configuration information in the service push configuration of the medical scenario, the configuration interface corresponding to the configuration information is called to generate the push content for the medical institution.

[0058] Specifically, in the process of generating push content for medical institutions, the server queries the service push configuration for the medical institution's medical scenario based on the medical institution's identifier, and then calls the corresponding configuration interface to generate the push content for the medical institution based on the configuration information in the service push configuration for the medical scenario.

[0059] In another optional implementation provided in this embodiment, the generation of push content for the medical institution based on the service push configuration of the medical scenario includes:

[0060] The configuration information in the service push configuration of the medical scenario is input into the configuration interface to generate the push content for the medical institution, and the push content returned by the configuration interface is received.

[0061] Specifically, in the process of generating push content for medical institutions, after the server queries the service push configuration of the medical institution's medical scenario based on the medical institution's identifier, it can also input the configuration information in the service push configuration of the medical scenario into a general configuration interface to generate push content for the medical institution. After the push content is generated, the server receives the push content returned by the configuration interface call.

[0062] Furthermore, push content for medical institutions can be generated based on the configuration type. In one optional implementation of this embodiment, generating push content for medical institutions based on the service push configuration of the medical scenario includes:

[0063] Based on the configuration type in the service push configuration of the medical scenario, obtain the push content of the medical institution under the corresponding configuration type.

[0064] Furthermore, if the configuration type is the first configuration type, such as a link type, in one optional implementation of this embodiment, the push content of the medical institution under the corresponding configuration type is obtained in the following way:

[0065] If the configuration type is the first configuration type, then a service access control for the medical institution is generated, and the service access control is bound to the access link of the registration service of the member registration of the medical institution;

[0066] An access point for the registered service is generated based on the access link and the service access control, and the access point is used as the push content.

[0067] If the configuration type is the second configuration type, such as the advertising type, in another optional implementation provided in this embodiment, the push content of the medical institution under the corresponding configuration type is obtained in the following way:

[0068] If the configuration type is the second configuration type, then the service push text and / or service push image of the medical scenario of the medical institution are generated, and the service push text and / or service push image of the medical scenario are used as the push content.

[0069] For example, link-type push content could be a link to a medical institution's mini-program, while advertising-type push content could be push copy related to medical institutions.

[0070] In the process of pushing medical services to users whose identities have been verified, in order to enhance the accuracy of the medical service push, the service push configuration of the medical institution is determined by querying the medical institution's identifier. Specifically, in an optional implementation method provided in this embodiment, the service push configuration of the medical institution is queried in the following way:

[0071] Search for the corresponding institution service identifier based on the issued medical institution identifier;

[0072] Query the service push configuration for medical scenarios of the medical institution corresponding to the service identifier of the institution.

[0073] For example, by querying the corresponding store ID through the hospital's national medical insurance code, the service push configuration for the corresponding cinema's medical scenarios can be determined based on the store ID.

[0074] It should be noted that for users who use medical insurance codes for payment, during the process of pushing medical services to users, the system queries the corresponding institution service identifier based on the issued medical institution identifier; queries the medical service push configuration of the medical institution corresponding to the institution service identifier; and generates the push content of the medical institution based on the service push configuration and sends it to the user terminal.

[0075] In practice, after the medical institution verifies the user's identity information, it returns the verification result to the medical insurance platform. The medical insurance platform updates the medical insurance code based on the verification result and sends the updated medical insurance code to the server.

[0076] In one optional implementation of this embodiment, the step of generating and sending push content from the medical institution to the user terminal based on the service push configuration includes:

[0077] The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario;

[0078] Receive the updated medical insurance code issued by the medical insurance platform after updating the medical insurance code based on the identity verification results returned by the medical institution;

[0079] Generate an identity verification result page containing the updated medical insurance code and the push content, and send it to the user terminal.

[0080] Specifically, after receiving the updated medical insurance code and medical institution identifier from the medical insurance platform, the server, based on the service push configuration for querying the medical institution according to the medical institution identifier, generates push content for the medical institution, and sends a verification result page containing the updated medical insurance code and the push content to the user terminal. For example, the generated push content is placed on the verification result page in the area where the updated medical insurance code is issued.

[0081] In the process of pushing medical services to users making payments, in order to save resources, the pushed content is loaded onto the payment results page for joint display. In one optional implementation of this embodiment, the step of generating the push content of the medical institution based on the service push configuration and sending it to the user terminal includes:

[0082] The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario;

[0083] A payment result page containing the payment result and the push content is generated and sent to the user terminal.

[0084] Specifically, the user displays their medical insurance code to the medical institution through their user terminal; the medical institution reads the medical insurance information from the medical insurance code and sends a payment request carrying the medical insurance code information to the medical insurance platform; the medical insurance platform decodes the medical insurance code information to obtain the user's identity information, and deducts the payment from the medical insurance account corresponding to the user's identity information based on the bill amount carried in the payment request, and returns the payment result to the medical institution after the payment is completed; the server obtains the payment result, generates push content for the medical institution based on the service push configuration of the medical scenario, and generates a payment result page containing the payment result and the push content, which is then sent to the user terminal.

[0085] Furthermore, after the server generates and sends the identity verification result page containing the updated medical insurance code and the push content to the user terminal, the user terminal receives the identity verification result page containing the updated medical insurance code and the push content sent by the server. In this embodiment, the user can present the updated medical insurance code on the identity verification result page to the medical institution for a second time to make medical payment. That is, the user who scanned the medical insurance code for identity verification scans the updated medical insurance code a second time to make payment. The specific payment process for medical expenses can be found in the aforementioned steps and will not be repeated here.

[0086] In summary, the service push method for medical scenarios provided in this embodiment receives a user's medical insurance code access request sent by the user terminal and sends it to the medical insurance platform. Subsequently, the medical insurance platform queries the user's medical insurance code and returns the medical insurance code information to the server. The method then receives the medical insurance code information returned by the medical insurance platform and sends it to the user terminal. After the user terminal generates a medical insurance code based on the medical insurance code information and displays it to the medical institution, the medical institution scans the medical insurance code and reads the medical insurance code information, sending a payment request or identity verification request carrying the medical insurance code information to the medical insurance platform. Finally, the method obtains the medical institution's identifier issued by the medical insurance platform, queries the medical institution's service push configuration for medical scenarios based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration for medical scenarios. This achieves targeted delivery of push content, meets the needs of medical institutions, and enriches the user experience.

[0087] Furthermore, during the generation of push content, the configuration interface corresponding to the configuration information in the service push configuration of the medical scenario is called to generate push content for medical institutions; or, the configuration information in the service push configuration of the medical scenario is input into the configuration interface to generate push content for medical institutions, and the push content returned by the configuration interface call is received, so that the push content meets the targeted delivery needs of medical institutions.

[0088] The above-described service push method for a medical scenario can be implemented by a server. The following method embodiment provides another implementation method for a medical scenario, which can be implemented by a user terminal. The two can cooperate with each other during execution. Therefore, the above implementation process can be read with reference to the corresponding content of the following method embodiment. Similarly, the following implementation process can also be read with reference to the corresponding content of the above method embodiment.

[0089] The following example uses a service push method for a medical scenario provided in this embodiment to illustrate its application in a hospital payment scenario. Figure 3 The service push method for medical scenarios provided in this embodiment will be further explained below. Figure 3 The service push method applied to medical scenarios in hospital payment scenarios includes the following steps.

[0090] Step S304: Receive the user's medical insurance code access request sent by the user terminal and send it to the medical insurance platform.

[0091] After that, the medical insurance platform queries the user's medical insurance code and returns the medical insurance code information to the server.

[0092] Step S306: Receive the medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal.

[0093] After that, the medical institution scans the medical insurance code displayed on the user's terminal and reads the medical insurance code information, and sends a payment request carrying the medical insurance code information to the medical insurance platform.

[0094] The medical insurance platform decodes the medical insurance code information to obtain the user's identity information, deducts the payment amount from the medical insurance account corresponding to the user's identity information based on the payment bill carried in the payment request, and returns the payment result to the server after the payment is completed.

[0095] Step S310: Receive the payment result sent by the medical insurance platform.

[0096] After that, the medical insurance platform sends the medical institution's identifier to the server.

[0097] Step S312: Obtain the medical institution identifier issued by the medical insurance platform.

[0098] Step S314: Query the service push configuration of the medical institution for medical scenarios based on the medical institution identifier, and generate the push content of the medical institution based on the service push configuration of the medical scenarios.

[0099] Step S316: Generate a payment result page containing the payment result and push content and send it to the user terminal.

[0100] Steps S304 to S306 and S310 to S316 provided in this embodiment are executed by the server. It should be noted that the server's execution of the above steps S304 to S306 and S310 to S316 can cooperate with the user terminal's execution of steps S302, S308, and S318 in the following embodiments. Therefore, when reading this embodiment, please refer to the corresponding content of steps S302, S308, and S318 provided in the following method embodiments.

[0101] The following example uses a service push method for a medical scenario provided in this embodiment, applied in a hospital identity verification scenario, as an example. Figure 4 The service push method for medical scenarios provided in this embodiment will be further explained below. Figure 4 The service push method applied to medical scenarios such as hospital identity verification includes the following steps.

[0102] Step S404: Receive the user's medical insurance code access request sent by the user terminal and send it to the medical insurance platform.

[0103] After that, the medical insurance platform queries the user's medical insurance code and returns the medical insurance code information to the server.

[0104] Step S406: Receive the medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal.

[0105] After that, the medical institution scans the medical insurance code displayed on the user's terminal and reads the medical insurance code information, and sends an identity verification request carrying the medical insurance code information to the medical insurance platform.

[0106] The medical insurance platform decodes the medical insurance code information to obtain the user's identity information and then returns the user's identity information to the medical institution.

[0107] Medical institutions verify users' identities based on their information and return the verification results to the medical insurance platform.

[0108] The medical insurance platform updates the medical insurance code based on the identity verification results and sends the updated medical insurance code to the server.

[0109] Step S410: Receive the updated medical insurance code sent by the medical insurance platform.

[0110] After that, the medical insurance platform queries the medical institution's medical institution identifier and issues it.

[0111] Step S412: Obtain the medical institution identifier issued by the medical insurance platform.

[0112] Step S414: Query the service push configuration of the medical institution for medical scenarios based on the medical institution identifier, and generate the push content of the medical institution based on the service push configuration of the medical scenarios.

[0113] Step S416: Generate an identity verification result page containing the updated medical insurance code and push content, and send it to the user terminal.

[0114] In this embodiment, steps S404 to S406 and S410 to S416 are executed by the server. It should be noted that the server's execution of steps S404 to S406 and S410 to S416 can cooperate with the user terminal's execution of steps S402, S408, and S418 in the following embodiments. Therefore, when reading this embodiment, please refer to the corresponding content of steps S402, S408, and S418 provided in the following method embodiments.

[0115] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0116] This manual provides another example of a service push method for a medical scenario:

[0117] The service push method for medical scenarios provided in this embodiment sends a user's medical insurance code access request to the server based on the access instruction submitted by the user through the medical insurance service; receives the user's medical insurance code information obtained from the medical insurance platform from the server, generates a medical insurance code based on the medical insurance code information and displays it to the medical institution; receives push content from the medical institution sent by the server; the push content is generated after the medical insurance platform decodes the medical insurance code information submitted by the medical institution, and generates the service push configuration for the medical scenario of the medical institution corresponding to the medical institution identifier returned by the decoding, which enriches the user's experience of using the medical insurance code for medical treatment, and at the same time meets the service push needs of medical institutions for medical scenarios.

[0118] Reference Figure 5 The service push method for medical scenarios provided in this embodiment specifically includes steps S502 to S506.

[0119] Step S502: Based on the access instruction submitted by the user through the medical insurance service, send the user's medical insurance code access request to the server.

[0120] The medical insurance code described in this embodiment includes the barcode and / or QR code of the electronic medical insurance certificate. The electronic medical insurance certificate is an electronic credential for medical insurance payers to make medical insurance payments and participate in medical insurance services. It corresponds one-to-one with the payer's physical medical insurance certificate and can be activated and used by the payer through third-party applications or medical insurance service platforms. The activation and association process of the electronic medical insurance certificate requires data processing integration with the medical insurance system. The medical insurance platform maintains the user's medical insurance account and provides medical insurance settlement and identity verification capabilities. The medical insurance services include subroutines of third-party applications or medical insurance-related services provided by third-party applications, such as medical insurance information query services and medical insurance payment services. The user identity information includes the user's name and / or identity certificate number.

[0121] In practice, during the user's identity verification or payment process, the user terminal displays the medical insurance code for identity verification or payment. During the process of the user displaying the medical insurance code, according to the access instruction submitted by the user through the medical insurance service, the user terminal sends the user's medical insurance code access request to the server; the server receives the user's medical insurance code access request sent by the user terminal and sends it to the medical insurance platform; the medical insurance platform receives the medical insurance code access request sent by the server, queries the user's medical insurance certificate and returns it to the server.

[0122] Step S504: Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution.

[0123] The medical insurance code information includes information related to the medical insurance code. Optionally, the medical insurance code information includes the medical insurance code value. The medical institution includes institutions that provide medical services, such as hospitals and pharmacies.

[0124] In practice, the server receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal. After receiving the user's medical insurance code information obtained from the medical insurance platform from the server, the user terminal generates a medical insurance code based on the medical insurance code information and displays it to the medical institution for identity verification or payment.

[0125] Furthermore, in an optional implementation of this embodiment, after receiving the medical insurance code information returned by the medical insurance platform and sending the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution, an association relationship is established between the medical insurance code information and the user's user identity information. This allows the medical insurance platform to determine the user's identity information based on the association relationship after decoding the medical insurance code to obtain the medical insurance code information, and to issue the medical institution's identifier based on the user's identity information.

[0126] Step S506: Receive the push content from the medical institution sent by the server.

[0127] The medical institution identifier includes a unique institution code generated according to the coding standards specified by the National Healthcare Security Administration. The service push configuration for the medical scenario includes configuration of either the service push format or the service push content.

[0128] In this embodiment, the medical insurance code can be used for identity verification and medical expense payment; the following describes these two processes in detail.

[0129] (1) The medical insurance code is used for identity verification.

[0130] In one optional implementation of this embodiment, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information and sends an identity verification request carrying the medical insurance code information to the medical insurance platform.

[0131] The medical insurance platform decodes the medical insurance code information to obtain the user's identity information and returns the user's identity information to the medical institution for identity verification.

[0132] Optionally, the medical insurance platform decodes the medical insurance code information to obtain user identity information, and after returning the user identity information to the medical institution, queries the medical institution's medical institution identifier and issues it.

[0133] Specifically, users present their medical insurance code to medical institutions via their user terminals; the medical institutions read the medical insurance information from the code and send a verification request carrying the code information to the medical insurance platform; the medical insurance platform decodes the code information to obtain the user's identity information and returns it to the medical institution; the medical institution receives the user's identity information and performs verification. For example, when a user registers at a medical institution, they present their medical insurance code to the institution via their user terminal. The medical institution reads the code value and sends a verification request carrying the code value to the medical insurance platform. The medical insurance platform decodes the code value to obtain the user's identity information and returns it to the medical institution, which then performs verification.

[0134] In the second optional implementation provided in this embodiment, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information and sends a payment request carrying the medical insurance code information to the medical insurance platform;

[0135] The medical insurance platform responds to the payment request by performing the following operations:

[0136] The user's identity information is obtained by decoding the medical insurance code information;

[0137] The bill amount carried in the payment request will be deducted from the medical insurance account corresponding to the user's identity information.

[0138] The payment result will be returned to the medical institution after payment is completed.

[0139] Specifically, the user presents their medical insurance code to the medical institution through their user terminal; the medical institution reads the medical insurance information from the medical insurance code and sends a payment request carrying the medical insurance code information to the medical insurance platform; the medical insurance platform decodes the medical insurance code information to obtain the user's identity information, and deducts the payment from the medical insurance account corresponding to the user's identity information based on the bill amount carried in the payment request, and returns the payment result to the medical institution after the payment is completed.

[0140] After obtaining the medical institution identifier issued by the medical insurance platform, in order to achieve the accuracy of service push in medical scenarios and realize targeted service delivery, that is, to push the services provided by the medical institution (the object to be displayed with the medical insurance code) to the user terminal, in this step, the service push configuration of the corresponding medical institution in medical scenarios is queried according to the medical institution identifier, and the push content of the medical institution is generated and sent to the user terminal based on the service push configuration of the medical scenario.

[0141] In the specific execution process, in order to ensure that the push content sent to the user terminal matches the medical institution, in an optional implementation method provided in this embodiment, the push content of the medical institution is generated in the following way:

[0142] Based on the configuration information in the service push configuration of the medical scenario, the configuration interface corresponding to the configuration information is called to generate the push content for the medical institution.

[0143] Specifically, in the process of generating push content for medical institutions, the server queries the service push configuration for the medical institution's medical scenario based on the medical institution's identifier, and then calls the corresponding configuration interface to generate the push content for the medical institution based on the configuration information in the service push configuration for the medical scenario.

[0144] In another optional implementation provided in this embodiment, the generation of push content for the medical institution based on the service push configuration of the medical scenario includes:

[0145] The configuration information in the service push configuration of the medical scenario is input into the configuration interface to generate the push content for the medical institution, and the push content returned by the configuration interface is received.

[0146] Specifically, in the process of generating push content for medical institutions, after the server queries the service push configuration of the medical institution's medical scenario based on the medical institution's identifier, it can also input the configuration information in the service push configuration of the medical scenario into a general configuration interface to generate push content for the medical institution. After the push content is generated, the server receives the push content returned by the configuration interface call.

[0147] Furthermore, push content for medical institutions can be generated based on the configuration type. In one optional implementation of this embodiment, generating push content for medical institutions based on the service push configuration of the medical scenario includes:

[0148] Based on the configuration type in the service push configuration of the medical scenario, obtain the push content of the medical institution under the corresponding configuration type.

[0149] Furthermore, if the matching type is the first configuration type, such as a link type, in one optional implementation of this embodiment, the push content of the medical institution under the corresponding configuration type is obtained in the following way:

[0150] If the configuration type is the first configuration type, then a service access control for the medical institution is generated, and the service access control is bound to the access link of the registration service of the member registration of the medical institution;

[0151] An access point for the registered service is generated based on the access link and the service access control, and the access point is used as the push content.

[0152] If the configuration type is the second configuration type, such as the advertising type, in another optional implementation provided in this embodiment, the push content of the medical institution under the corresponding configuration type is obtained in the following way:

[0153] If the configuration type is the second configuration type, then the service push text and / or service push image of the medical scenario of the medical institution are generated, and the service push text and / or service push image of the medical scenario are used as the push content.

[0154] For example, link-type push content could be a link to a medical institution's mini-program, while advertising-type push content could be push copy related to medical institutions.

[0155] In the process of pushing medical services to users whose identities have been verified, in order to enhance the accuracy of the medical service push, the service push configuration of the medical institution is determined by querying the medical institution's identifier. Specifically, in an optional implementation method provided in this embodiment, the service push configuration of the medical institution is queried in the following way:

[0156] Search for the corresponding institution service identifier based on the issued medical institution identifier;

[0157] Query the service push configuration for medical scenarios of the medical institution corresponding to the service identifier of the institution.

[0158] For example, by querying the corresponding store ID through the hospital's national medical insurance code, the service push configuration for the corresponding cinema's medical scenarios can be determined based on the store ID.

[0159] It should be noted that for users who use medical insurance codes for payment, during the process of pushing medical services to users, the system queries the corresponding institution service identifier based on the issued medical institution identifier; queries the medical service push configuration of the medical institution corresponding to the institution service identifier; and generates the push content of the medical institution based on the service push configuration and sends it to the user terminal.

[0160] In practice, after the medical institution verifies the user's identity information, it returns the verification result to the medical insurance platform. The medical insurance platform updates the medical insurance code based on the verification result and sends the updated medical insurance code to the server.

[0161] In one optional implementation of this embodiment, the step of generating and sending push content from the medical institution to the user terminal based on the service push configuration includes:

[0162] The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario;

[0163] Receive the updated medical insurance code issued by the medical insurance platform after updating the medical insurance code based on the identity verification results returned by the medical institution;

[0164] Generate an identity verification result page containing the updated medical insurance code and the push content, and send it to the user terminal.

[0165] Specifically, after receiving the updated medical insurance code and medical institution identifier from the medical insurance platform, the server, based on the service push configuration for querying the medical institution according to the medical institution identifier, generates push content for the medical institution, and sends a verification result page containing the updated medical insurance code and the push content to the user terminal. For example, the generated push content is placed on the verification result page in the area where the updated medical insurance code is issued.

[0166] In the process of pushing medical services to users making payments, in order to save resources, the pushed content is loaded onto the payment results page for joint display. In one optional implementation of this embodiment, the step of generating the push content of the medical institution based on the service push configuration and sending it to the user terminal includes:

[0167] The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario;

[0168] A payment result page containing the payment result and the push content is generated and sent to the user terminal.

[0169] Specifically, the user displays their medical insurance code to the medical institution through their user terminal; the medical institution reads the medical insurance information from the medical insurance code and sends a payment request carrying the medical insurance code information to the medical insurance platform; the medical insurance platform decodes the medical insurance code information to obtain the user's identity information, and deducts the payment from the medical insurance account corresponding to the user's identity information based on the bill amount carried in the payment request, and returns the payment result to the medical institution after the payment is completed; the server obtains the payment result, generates push content for the medical institution based on the service push configuration of the medical scenario, and generates a payment result page containing the payment result and the push content, which is then sent to the user terminal.

[0170] Furthermore, after the server generates and sends the identity verification result page containing the updated medical insurance code and the push content to the user terminal, the user terminal receives the identity verification result page containing the updated medical insurance code and the push content sent by the server. In this embodiment, the user can present the updated medical insurance code on the identity verification result page to the medical institution for a second time to make medical payment. That is, the user who scanned the medical insurance code for identity verification scans the updated medical insurance code a second time to make payment. The specific payment process for medical expenses can be found in the aforementioned steps and will not be repeated here.

[0171] In summary, the service push method for medical scenarios provided in this embodiment receives a user's medical insurance code access request sent by the user terminal and sends it to the medical insurance platform. Subsequently, the medical insurance platform queries the user's medical insurance code and returns the medical insurance code information to the server. The method then receives the medical insurance code information returned by the medical insurance platform and sends it to the user terminal. After the user terminal generates a medical insurance code based on the medical insurance code information and displays it to the medical institution, the medical institution scans the medical insurance code and reads the medical insurance code information, sending a payment request or identity verification request carrying the medical insurance code information to the medical insurance platform. Finally, the method obtains the medical institution's identifier issued by the medical insurance platform, queries the medical institution's service push configuration for medical scenarios based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration for medical scenarios. This achieves targeted delivery of push content, meets the needs of medical institutions, and enriches the user experience.

[0172] Furthermore, during the generation of push content, the configuration interface corresponding to the configuration information in the service push configuration of the medical scenario is called to generate push content for medical institutions; or, the configuration information in the service push configuration of the medical scenario is input into the configuration interface to generate push content for medical institutions, and the push content returned by the configuration interface call is received, so that the push content meets the targeted delivery needs of medical institutions.

[0173] The following example uses a service push method for a medical scenario provided in this embodiment to illustrate its application in a hospital payment scenario. Figure 3The service push method for medical scenarios provided in this embodiment will be further explained below. Figure 3 The service push method applied to medical scenarios in hospital payment scenarios includes the following steps.

[0174] Step S302: Based on the access instruction submitted by the user through the medical insurance service, send the user's medical insurance code access request to the server.

[0175] Step S308: Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution.

[0176] Step S318: Receive the payment result page sent by the server.

[0177] The following example uses a service push method for a medical scenario provided in this embodiment to illustrate its application in a hospital payment scenario. Figure 4 The service push method for medical scenarios provided in this embodiment will be further explained below. Figure 4 The service push method applied to medical scenarios in hospital payment scenarios includes the following steps.

[0178] Step S402: Based on the access instruction submitted by the user through the medical insurance service, send the user's medical insurance code access request to the server.

[0179] Step S408: Receive the user's medical insurance code information obtained from the medical insurance platform sent by the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution.

[0180] Step S418: Receive the identity verification result page sent by the server.

[0181] This manual provides an example of a service push device for a medical scenario, as follows:

[0182] In the above embodiments, a service push method for a medical scenario is provided, and correspondingly, a service push device for a medical scenario is also provided, which will be described below with reference to the accompanying drawings.

[0183] Reference Figure 6 The diagram illustrates a service push device for a medical scenario provided in this embodiment.

[0184] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0185] This embodiment provides a service push device for a medical scenario, including:

[0186] The access request sending module 602 is configured to receive the user's medical insurance code access request sent by the user terminal and send it to the medical insurance platform;

[0187] The information sending module 604 is configured to receive the medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal, so as to generate a medical insurance code based on the medical insurance code information and display it to the medical institution;

[0188] The identifier acquisition module 606 is configured to acquire the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution;

[0189] The push content sending module 608 is configured to query the service push configuration of the medical institution's medical scenario based on the medical institution's identifier, and generate push content for the medical institution based on the service push configuration and send it to the user terminal.

[0190] Another example of a service push device for a medical scenario provided in this manual is as follows:

[0191] In the above embodiments, another service push method for medical scenarios is provided, and correspondingly, another service push device for medical scenarios is also provided, which will be described below with reference to the accompanying drawings.

[0192] Reference Figure 7 The diagram illustrates a service push device for a medical scenario provided in this embodiment.

[0193] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0194] This embodiment provides a service push device for a medical scenario, including:

[0195] The access request sending module 702 is configured to send the user's medical insurance code access request to the server based on the access instruction submitted by the user through the medical insurance service;

[0196] The medical insurance code display module 704 is configured to receive the user's medical insurance code information obtained from the medical insurance platform sent by the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution.

[0197] The push content receiving module 706 is configured to receive push content from the medical institution sent by the server; the push content is generated by the medical insurance platform after decoding the medical insurance code submitted by the medical institution, based on the service push configuration of the medical institution's medical scenario corresponding to the medical institution identifier returned by the decoding.

[0198] This manual provides an example of a service push device for a medical scenario, as follows:

[0199] Corresponding to the service push method for a medical scenario described above, based on the same technical concept, one or more embodiments of this specification also provide a service push device for a medical scenario, which is used to execute the service push method for the medical scenario provided above. Figure 8 This is a schematic diagram of the structure of a service push device for a medical scenario provided in one or more embodiments of this specification.

[0200] This embodiment provides a service push device for a medical scenario, including:

[0201] like Figure 8 As shown, service delivery devices in medical scenarios can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memory 802, with memory 802 storing one or more applications or data. Memory 802 can be temporary or persistent storage. Applications stored in memory 802 may include one or more modules (not shown), each module comprising a series of computer-executable instructions for the service delivery device. Furthermore, processor 801 may be configured to communicate with memory 802, executing the series of computer-executable instructions in memory 802 on the service delivery device. The service delivery device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0202] In one specific embodiment, the service push device for medical scenarios includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the service push device for medical scenarios, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0203] Receive user's medical insurance code access request sent from user terminal and send it to medical insurance platform;

[0204] The system receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution.

[0205] Obtain the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution;

[0206] The system queries the service push configuration of the medical institution for the medical scenario based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration and sends it to the user terminal.

[0207] Another example of a service push device for a medical scenario provided in this manual is as follows:

[0208] Corresponding to the service push method for another medical scenario described above, based on the same technical concept, one or more embodiments of this specification also provide a service push device for another medical scenario, which is used to execute the service push method for another medical scenario provided above. Figure 9 This is a schematic diagram of the structure of a service push device for another medical scenario provided in one or more embodiments of this specification.

[0209] This embodiment provides a service push device for a medical scenario, including:

[0210] like Figure 9 As shown, service delivery devices in medical scenarios can vary significantly due to differences in configuration or performance. They may include one or more processors 901 and memory 902, with memory 902 storing one or more applications or data. Memory 902 can be temporary or persistent storage. Applications stored in memory 902 may include one or more modules (not shown), each module comprising a series of computer-executable instructions for the service delivery device. Furthermore, processor 901 may be configured to communicate with memory 902, executing the series of computer-executable instructions in memory 902 on the service delivery device. The service delivery device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.

[0211] In one specific embodiment, the service push device for medical scenarios includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the service push device for medical scenarios, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0212] Based on the access instruction submitted by the user through the medical insurance service, a medical insurance code access request for the user is sent to the server;

[0213] Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution;

[0214] The system receives push content from the medical institution sent by the server. The push content is generated by the medical insurance platform after decoding the medical insurance code submitted by the medical institution, based on the service push configuration of the medical institution's medical scenario corresponding to the medical institution identifier returned by the decoding.

[0215] This specification provides an example of a storage medium as follows:

[0216] Corresponding to the service push method for a medical scenario described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0217] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0218] Receive user's medical insurance code access request sent from user terminal and send it to medical insurance platform;

[0219] The system receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution.

[0220] Obtain the medical institution identifier issued by the medical insurance platform after decoding the medical insurance code information submitted by the medical institution;

[0221] The system queries the service push configuration of the medical institution for the medical scenario based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration and sends it to the user terminal.

[0222] It should be noted that the embodiment of a storage medium in this specification and the embodiment of a service push method in a medical scenario in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0223] Another embodiment of the storage medium provided in this specification is as follows:

[0224] In response to another service push method for a medical scenario described above, based on the same technical concept, one or more embodiments of this specification also provide another storage medium.

[0225] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0226] Based on the access instruction submitted by the user through the medical insurance service, a medical insurance code access request for the user is sent to the server;

[0227] Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution;

[0228] The system receives push content from the medical institution sent by the server. The push content is generated by the medical insurance platform after decoding the medical insurance code submitted by the medical institution, based on the service push configuration of the medical institution's medical scenario corresponding to the medical institution identifier returned by the decoding.

[0229] It should be noted that the embodiments of another storage medium in this specification and the embodiments of another service push method in a medical scenario in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0230] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0231] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, 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, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0232] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0234] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0235] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied 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.

[0236] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0237] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0238] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0240] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0241] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0242] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0243] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0244] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0245] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A service push method for a medical scenario, comprising: Receive user's medical insurance code access request sent from user terminal and send it to medical insurance platform; The system receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution. The medical insurance platform decodes the medical insurance code information submitted by the medical institution and returns the user identity information to the medical institution, and obtains the medical institution identifier of the medical institution obtained and issued by the medical insurance platform after querying; The system queries the service push configuration of the medical institution for the medical scenario based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration and sends it to the user terminal.

2. The service push method for a medical scenario according to claim 1, wherein generating the push content for the medical institution based on the service push configuration includes: Based on the configuration information in the service push configuration, the configuration interface corresponding to the configuration information is called to generate the push content for the medical institution; or, The configuration information in the service push configuration is input into the configuration interface to generate the push content for the medical institution, and the push content returned by the configuration interface is received.

3. The service push method for a medical scenario according to claim 1, wherein generating the push content for the medical institution based on the service push configuration includes: Based on the configuration type in the service push configuration of the medical scenario, the push content for the medical institution under the corresponding configuration type is generated.

4. The service push method for a medical scenario according to claim 3, wherein generating the push content for the medical institution under the corresponding configuration type according to the configuration type in the service push configuration of the medical scenario includes: If the configuration type is the first configuration type, then a service access control for the medical institution is generated, and the service access control is bound to the access link of the registration service of the member registration of the medical institution; An access point for the registered service is generated based on the access link and the service access control, and the access point is used as the push content.

5. The service push method for a medical scenario according to claim 3, wherein generating the push content for the medical institution under the corresponding configuration type according to the configuration type in the service push configuration of the medical scenario includes: If the configuration type is the second configuration type, then the service push text and / or service push image of the medical scenario of the medical institution are generated, and the service push text and / or service push image of the medical scenario are used as the push content.

6. The service push method for a medical scenario according to claim 1, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information of the medical insurance code and sends an identity verification request carrying the medical insurance code information to the medical insurance platform; The medical insurance platform decodes the medical insurance code information to obtain the user's identity information and returns the user's identity information to the medical institution for identity verification.

7. The service push method for medical scenarios according to claim 6, wherein the medical insurance platform decodes the medical insurance code information to obtain the user identity information, and after returning the user identity information to the medical institution, queries the medical institution's medical institution identifier and sends it to the server; Accordingly, the service push configuration for querying the medical scenario of the medical institution based on the medical institution identifier includes: The corresponding institution service identifier can be queried based on the medical institution identifier sent by the medical insurance platform; Query the service push configuration for medical scenarios of the medical institution corresponding to the service identifier of the institution.

8. The service push method for a medical scenario according to claim 6, wherein generating push content for the medical institution based on the service push configuration and sending it to the user terminal includes: The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario; Receive the updated medical insurance code issued by the medical insurance platform after updating the medical insurance code based on the identity verification results returned by the medical institution; Generate an identity verification result page containing the updated medical insurance code and the push content, and send it to the user terminal.

9. The service push method for a medical scenario according to claim 1, after the user terminal displays the medical insurance code to the medical institution, the medical institution reads the medical insurance code information of the medical insurance code and sends a payment request carrying the medical insurance code information to the medical insurance platform; The medical insurance platform responds to the payment request by performing the following operations: The user's identity information is obtained by decoding the medical insurance code information; The bill amount carried in the payment request will be deducted from the medical insurance account corresponding to the user's identity information.

10. The service push method for a medical scenario according to claim 9, wherein generating push content for the medical institution based on the service push configuration and sending it to the user terminal includes: Receive payment results sent by the medical insurance platform; The push content for the medical institution is generated based on the service push configuration of the aforementioned medical scenario; A payment result page containing the payment result and the push content is generated and sent to the user terminal.

11. The service push method for a medical scenario according to claim 1, after the steps of receiving the medical insurance code information returned by the medical insurance platform and sending the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and displaying it to the medical institution are executed, and before the steps of returning the user identity information obtained by the medical insurance platform from decoding the medical insurance code information submitted by the medical institution to the medical institution and obtaining the medical institution identifier obtained and issued by the medical insurance platform after querying, the method further includes: Establish the association between the medical insurance code information and the user's user identity information; Accordingly, after the medical insurance platform decodes the medical insurance code to obtain the medical insurance code information, it determines the user identity information based on the association relationship, and issues the medical institution identifier according to the user identity information.

12. A service push method for a medical scenario, comprising: Based on the access instruction submitted by the user through the medical insurance service, a medical insurance code access request for the user is sent to the server; Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution; The server receives push content from the medical institution; after the medical insurance platform decodes the medical insurance code information submitted by the medical institution to obtain user identity information and returns it to the medical institution, the server generates the service push configuration of the medical institution's medical scenario corresponding to the medical institution's medical institution identifier obtained and issued by the medical insurance platform after querying.

13. The service push method for a medical scenario according to claim 12, wherein the push content of the medical institution is generated in the following manner: Based on the configuration information in the service push configuration of the medical scenario, the configuration interface corresponding to the configuration information is called to generate the push content for the medical institution; or, The configuration information in the service push configuration of the medical scenario is input into the configuration interface to generate the push content for the medical institution, and the push content returned by the configuration interface is received.

14. The service push method for a medical scenario according to claim 12, wherein the push content of the medical institution is generated in the following manner: Based on the configuration type in the service push configuration of the medical scenario, obtain the push content of the medical institution under the corresponding configuration type.

15. The service push method for a medical scenario according to claim 14, wherein obtaining the push content of the medical institution under the corresponding configuration type according to the configuration type in the service push configuration of the medical scenario includes: If the configuration type is the first configuration type, then a service access control for the medical institution is generated, and the service access control is bound to the access link of the registration service of the member registration of the medical institution; An access point for the registered service is generated based on the access link and the service access control, and the access point is used as the push content.

16. The service push method for a medical scenario according to claim 14, wherein obtaining the push content of the medical institution under the corresponding configuration type according to the configuration type in the service push configuration of the medical scenario includes: If the configuration type is the second configuration type, then the service push text and / or service push image of the medical scenario of the medical institution are generated, and the service push text and / or service push image of the medical scenario are used as the push content.

17. The service push method for a medical scenario according to claim 12, wherein receiving the push content from the medical institution sent by the server includes: Receive the identity verification result page sent by the server, which includes the updated medical insurance code and the push content; The updated medical insurance code is returned after the medical insurance platform verifies the identity based on the medical insurance code information.

18. The service push method for a medical scenario according to claim 12, wherein receiving the push content from the medical institution sent by the server includes: Receive a payment result page sent by the server, which includes the payment result and the push content; The payment result is obtained by deducting the amount from the payment bill carried in the payment request sent by the medical insurance platform to the medical institution.

19. A service push device for a medical scenario, comprising: The access request sending module is configured to receive user medical insurance code access requests sent by user terminals and send them to the medical insurance platform; The information sending module is configured to receive the medical insurance code information returned by the medical insurance platform and send the medical insurance code information to the user terminal, so as to generate a medical insurance code based on the medical insurance code information and display it to the medical institution; The identifier acquisition module is configured to return the user identity information obtained by the medical insurance platform from decoding the medical insurance code information submitted by the medical institution to the medical institution, and to obtain the medical institution identifier of the medical institution obtained and issued by the medical insurance platform after querying. The push content sending module is configured to query the service push configuration of the medical institution's medical scenario based on the medical institution's identifier, and generate push content for the medical institution based on the service push configuration and send it to the user terminal.

20. A service push device for a medical scenario, comprising: The access request sending module is configured to send the user's medical insurance code access request to the server based on the access instruction submitted by the user through the medical insurance service; The medical insurance code display module is configured to receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution. The push content receiving module is configured to receive push content from the medical institution sent by the server. The push content is generated by the server based on the service push configuration of the medical institution's medical scenario corresponding to the medical institution's medical institution identifier obtained and issued by the medical institution platform after the medical insurance platform decodes the medical insurance code submitted by the medical institution to obtain user identity information and returns it to the medical institution.

21. A service push device for a medical scenario, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receive user's medical insurance code access request sent from user terminal and send it to medical insurance platform; The system receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution. The medical insurance platform decodes the medical insurance code information submitted by the medical institution and returns the user identity information to the medical institution, and obtains the medical institution identifier of the medical institution obtained and issued by the medical insurance platform after querying; The system queries the service push configuration of the medical institution for the medical scenario based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration and sends it to the user terminal.

22. A service push device for a medical scenario, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the access instruction submitted by the user through the medical insurance service, a medical insurance code access request for the user is sent to the server; Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution; The server receives push content from the medical institution; after the medical insurance platform decodes the medical insurance code submitted by the medical institution to obtain user identity information and returns it to the medical institution, the server generates the service push configuration of the medical institution's medical scenario corresponding to the medical institution's medical institution identifier obtained and issued by the medical insurance platform after querying.

23. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receive user's medical insurance code access request sent from user terminal and send it to medical insurance platform; The system receives the medical insurance code information returned by the medical insurance platform and sends the medical insurance code information to the user terminal to generate a medical insurance code based on the medical insurance code information and display it to the medical institution. The medical insurance platform decodes the medical insurance code information submitted by the medical institution and returns the user identity information to the medical institution, and obtains the medical institution identifier of the medical institution obtained and issued by the medical insurance platform after querying; The system queries the service push configuration of the medical institution for the medical scenario based on the medical institution's identifier, and generates push content for the medical institution based on the service push configuration and sends it to the user terminal.

24. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Based on the access instruction submitted by the user through the medical insurance service, a medical insurance code access request for the user is sent to the server; Receive the user's medical insurance code information obtained from the medical insurance platform from the server, generate a medical insurance code based on the medical insurance code information, and display it to the medical institution; The server receives push content from the medical institution; after the medical insurance platform decodes the medical insurance code submitted by the medical institution to obtain user identity information and returns it to the medical institution, the server generates the service push configuration of the medical institution's medical scenario corresponding to the medical institution's medical institution identifier obtained and issued by the medical insurance platform after querying.

Images