Progress information pushing method and device, computer device and readable storage medium

Abstract

The application discloses a progress information pushing method and device, computer equipment and a readable storage medium, relates to the Internet field and the digital medical field, and through a mode of system active contact and manual service promotion, service timeliness is improved, human cost is reduced, the response efficiency of the whole service process is improved, and user experience is improved. The method comprises the following steps: in response to a service performance start instruction, determining a service right and interest indicated by the service performance start instruction, acquiring a service link of the service right and interest, and multiple service nodes constituting the service link; according to the order of the multiple service nodes on the service link, service reminders are pushed to service personnel corresponding to the multiple service nodes; when service progress information is received based on a service node in the multiple service nodes, the service progress information is labeled by using a node identifier, and the labeled service progress information is pushed to a user initiating the service performance start instruction.

Description

Technical Field

[0001] This application relates to the Internet and digital healthcare fields, and in particular to a method, apparatus, computer device, and readable storage medium for pushing progress information. Background Technology

[0002] With the widespread application of internet technology in medical institutions, more convenient medical services have been provided to users. However, due to the scarcity of social medical resources, a series of problems have arisen, such as large hospital patient volume, long appointment times for famous doctors and hospitals, difficulty in registering and queuing for appointments, long waiting times, users being unfamiliar with the medical process, not knowing the location of hospital departments leading to duplicate registrations, and missing appointment times due to delayed visits. These issues have caused users to experience difficulties in seeing a doctor, long queues, and slow treatment.

[0003] In related technologies, online medical services address these issues by offering corresponding benefit packages, such as general physical examinations, manual appointment booking, and manual escort services. After purchasing designated benefits, users are provided with designated customer service representatives and health managers to facilitate appointments and access to medical services. However, the applicant recognizes that manually tracking the entire medical service process and its effectiveness requires continuous human intervention, consuming significant manpower and incurring delays, resulting in low overall service efficiency. Summary of the Invention

[0004] In view of this, this application provides a method, apparatus, computer device and readable storage medium for pushing progress information. The main purpose is to solve the problem that tracking the entire medical service performance process and effectiveness manually requires continuous manual intervention, consumes a lot of human resources, and causes delays in service timeliness, resulting in low response efficiency of the entire service process.

[0005] According to a first aspect of this application, a method for pushing progress information is provided, the method comprising:

[0006] In response to a service fulfillment commencement instruction, determine the service rights indicated by the service fulfillment commencement instruction, the service link for acquiring the service rights, and the multiple service nodes constituting the service link;

[0007] According to the order of the multiple service nodes on the service link, service reminders are pushed to the service personnel corresponding to the multiple service nodes so that the service personnel can perform the service content indicated by the corresponding service node.

[0008] When a service node receives service progress information uploaded by a service personnel, the service progress information is marked using the node identifier of the service node, and the marked service progress information is pushed to the user who initiated the service fulfillment start command.

[0009] Optionally, the step of pushing service reminders to the service personnel corresponding to the plurality of service nodes in the order of the plurality of service nodes on the service link includes:

[0010] For each of the plurality of service nodes, query the service content indicated by the service node in the service rights;

[0011] Obtain multiple candidate service personnel with the ability to execute the service content, and select one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the service node, wherein the selected candidate service personnel is either a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed.

[0012] By utilizing the service content indicated by each service node, a service reminder carrying the service content is generated for each service node, resulting in multiple service reminders;

[0013] According to the order of the multiple service nodes on the service link, the service reminders generated for the service nodes are pushed to the service personnel corresponding to each service node in sequence.

[0014] Optionally, the method further includes:

[0015] If a service node is detected as an associated service node, then the previous service node of the associated service node is determined on the service link, wherein the service content of the associated service node indicates that the service content of the associated service node is executed according to the service progress information of the previous service node.

[0016] Continuously detect whether the uploaded service progress information has been received from the previous service node;

[0017] When it is detected that service progress information has been received based on the previous service node, the service content indicated by the associated service node in the service rights is queried, and a service reminder carrying the service content indicated by the associated service node and the service progress information received by the previous service node is generated for the associated service node.

[0018] A plurality of candidate service personnel with the ability to execute the service content indicated by the associated service node are obtained, and one candidate service personnel is selected from the plurality of candidate service personnel as the service personnel corresponding to the associated service node, wherein the selected candidate service personnel is either a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed.

[0019] The service reminders generated for the associated service nodes will be pushed to the service personnel corresponding to the associated service nodes.

[0020] Optionally, the step of annotating the service progress information using the node identifier of the service node when one of the plurality of service nodes receives the service progress information uploaded by the service personnel, and pushing the annotated service progress information to the user who initiated the service fulfillment start command, includes:

[0021] For each of the plurality of service nodes, continuously detect whether each service node has received the uploaded service progress information;

[0022] When a service node is detected to have received uploaded service progress information, the node identifier of the service node is obtained, and the service progress information is marked using the node identifier.

[0023] The system queries the user who initiated the service fulfillment start command, obtains the user's preset reminder recipient, and pushes the marked service progress information to the reminder recipient. The reminder recipient is one or more of the following: email address, in-application account, and personal terminal information.

[0024] Optionally, the method further includes:

[0025] When a service node is detected to have not received the uploaded service progress information within a preset service time range, the first node identifier and the first service content of the service node are obtained.

[0026] The service content is labeled using the first node identifier, and a service timeout reminder carrying the labeled first service content is generated.

[0027] The service personnel corresponding to the service node are identified, and the service timeout reminder is pushed to the service personnel so that the service personnel's terminal displays the service timeout reminder in a preset reminder manner, wherein the preset reminder manner includes a red highlight reminder and a flashing reminder.

[0028] Optionally, the method further includes:

[0029] When a service failure feedback is received based on a service node, the second node identifier and the second service content of the service node are obtained;

[0030] The second service content is labeled using the second node identifier, and a service failure notification carrying the labeled second service content is generated;

[0031] Multiple candidate communicators are obtained, and one candidate communicator is selected from the multiple candidate communicators as the target communicator. The target communicator is either a candidate communicator that is currently idle or a candidate communicator with the fewest pending communication tasks currently associated with it.

[0032] Query the user who initiated the service fulfillment start command and obtain the user's user identifier;

[0033] The user identifier and the service failure notification are pushed to the target communication personnel so that the target communication personnel can identify the user indicated by the user identifier and display the service failure notification to the user according to a preset communication method, which is any one of telephone communication, online conversation communication, email communication, SMS communication, and robot communication.

[0034] Optionally, the method further includes:

[0035] In response to a service cancellation instruction, the service rights indicated by the service cancellation instruction are determined, and the service node that received the service cancellation instruction is identified among a plurality of service nodes included in the service rights, and the service node is designated as a service node to be cancelled.

[0036] Obtain the specified node identifier of the service node to be cancelled, and generate a service cancellation reminder carrying the specified node identifier;

[0037] The system queries the historical service personnel who performed the service content of the service node to be cancelled, and sends the service cancellation reminder to the historical service personnel so that they can perform the service cancellation operation on the service node to be cancelled.

[0038] According to a second aspect of this application, a progress information push device is provided, the device comprising:

[0039] The acquisition module is used to, in response to a service fulfillment start instruction, determine the service rights indicated by the service fulfillment start instruction, as well as the service link for acquiring the service rights and the multiple service nodes constituting the service link;

[0040] The push module is used to push service reminders to the service personnel corresponding to the multiple service nodes in the order of the multiple service nodes on the service link, so that the service personnel can perform the service content indicated by the corresponding service node;

[0041] The annotation module is used to annotate the service progress information using the node identifier of the service node when one of the multiple service nodes receives the service progress information uploaded by the service personnel, and to push the annotated service progress information to the user who initiated the service fulfillment start command.

[0042] Optionally, the push module is further configured to: query the service content indicated by the service node in the service rights for each of the plurality of service nodes; obtain a plurality of candidate service personnel capable of executing the service content; and select one candidate service personnel from the plurality of candidate service personnel as the service personnel corresponding to the service node, wherein the selected candidate service personnel is either a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed; generate service reminders carrying service content for each service node using the service content indicated by each service node, thereby obtaining a plurality of service reminders; and push the service reminders generated for the service nodes to the service personnel corresponding to each service node in sequence according to the order of the plurality of service nodes on the service link.

[0043] Optionally, the push module is further configured to: if a service node is detected as an associated service node, determine the previous service node of the associated service node on the service link, wherein the service content of the associated service node indicates that the service content of the associated service node is executed according to the service progress information of the previous service node; continuously detect whether the uploaded service progress information is received based on the previous service node; when it is detected that the service progress information is received based on the previous service node, query the service content indicated by the associated service node in the service rights, generate a service reminder for the associated service node carrying the service content indicated by the associated service node and the service progress information received by the previous service node; obtain multiple candidate service personnel with the ability to execute the service content indicated by the associated service node, and select one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the associated service node, wherein the selected candidate service personnel is a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed; and push the service reminder generated for the associated service node to the service personnel corresponding to the associated service node.

[0044] Optionally, the annotation module is further configured to continuously detect whether each of the plurality of service nodes has received the uploaded service progress information; when a service node is detected to have received the uploaded service progress information, obtain the node identifier of the service node, and use the node identifier to annotate the service progress information; query the user who initiated the service fulfillment start command, obtain the user's preset reminder recipient, and push the annotated service progress information to the reminder recipient, wherein the reminder recipient is one or more of email address, in-application account, and personal terminal information.

[0045] Optionally, the device further includes:

[0046] The service reminder module is used to, when a service node is detected to have not received uploaded service progress information within a preset service time range, obtain the first node identifier and first service content of the service node; mark the service content using the first node identifier to generate a service timeout reminder carrying the marked first service content; determine the service personnel corresponding to the service node, and push the service timeout reminder to the service personnel so that the service personnel's terminal displays the service timeout reminder according to a preset reminder method, wherein the preset reminder method includes a red highlight reminder and a flashing reminder.

[0047] Optionally, the device further includes:

[0048] The service failure module is used to, when a service failure feedback is received based on a service node, obtain the second node identifier and second service content of the service node; mark the second service content using the second node identifier to generate a service failure reminder carrying the marked second service content; obtain multiple candidate communication personnel, select one candidate communication personnel as the target communication personnel, wherein the target communication personnel is the candidate communication personnel currently in an idle state or the candidate communication personnel with the fewest pending communication tasks currently associated with; query the user who initiated the service fulfillment start command and obtain the user's user identifier; push the user identifier and the service failure reminder to the target communication personnel, so that the target communication personnel can identify the user indicated by the user identifier and display the service failure reminder to the user according to a preset communication method, wherein the preset communication method is any one of telephone communication, online conversation communication, email communication, SMS communication, and robot communication.

[0049] Optionally, the device further includes:

[0050] The service cancellation module is used to respond to a service cancellation instruction, determine the service rights indicated by the service cancellation instruction, identify the service node that received the service cancellation instruction from among multiple service nodes included in the service rights, and designate the service node as a service node to be cancelled; obtain a designated node identifier of the service node to be cancelled, generate a service cancellation reminder carrying the designated node identifier; query the historical service personnel who performed the service content of the service node to be cancelled, and send the service cancellation reminder to the historical service personnel so that the historical service personnel can perform a service cancellation operation on the service node to be cancelled.

[0051] According to a third aspect of this application, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in any of the first aspects above.

[0052] According to a fourth aspect of this application, a readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in any one of the first aspects above.

[0053] By employing the above technical solutions, this application provides a method, apparatus, computer device, and readable storage medium for pushing progress information. In response to a service fulfillment commencement command, this application determines the service rights indicated by the command, the service link for acquiring those rights, and multiple service nodes constituting the service link. Following the order of these service nodes on the service link, service reminders are pushed to the service personnel corresponding to each service node, enabling them to execute the service content indicated by the corresponding service node. When a service node receives service progress information uploaded by a service personnel, it marks the progress information using the node identifier and pushes the marked progress information to the user who initiated the service fulfillment commencement command. This system combines proactive outreach with manual service, improving service timeliness, reducing labor costs, enhancing the overall service process response efficiency, and improving user experience.

[0054] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0055] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0056] Figure 1 This illustration shows a flowchart of a progress information push method provided in an embodiment of this application;

[0057] Figure 2 This illustration shows a flowchart of a progress information push method provided in an embodiment of this application;

[0058] Figure 3A This illustration shows a structural diagram of a progress information push method provided in an embodiment of this application;

[0059] Figure 3B This illustration shows a structural diagram of a progress information push method provided in an embodiment of this application;

[0060] Figure 4 A schematic diagram of the device structure of a computer device provided in an embodiment of this application is shown. Detailed Implementation

[0061] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0062] This application provides a method for pushing progress information, such as... Figure 1 As shown, the method includes:

[0063] 101. In response to a service fulfillment commencement instruction, determine the service rights indicated by the service fulfillment commencement instruction, the service link for obtaining the service rights, and the multiple service nodes constituting the service link.

[0064] Online medical services address the difficulties users face in accessing medical care, long waiting times, and slow consultations by offering corresponding benefit service packages. However, current benefit service packages require designated staff to manually track the entire service process, incurring significant manpower costs and resulting in low service efficiency. Therefore, to solve this problem, this application proposes a method for pushing progress information. The implementing entity of this application can be a medical service platform, which provides services to users based on the computing power of its servers. The servers can be independent servers or servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. This allows the browser to directly load code packages, enabling it to run new features and provide users with services such as physical examinations, online medical consultations, and medical record viewing. The medical service platform offers a variety of benefits, such as physical examinations, manual registration, and personal escort services. It also has a service fulfillment process for these benefits. For example, the manual registration process involves the user submitting a registration request, the platform matching the request with a designated person, the person completing the registration offline, uploading the information to the platform, and finally notifying the user.

[0065] In this embodiment, after a user purchases service rights and applies for service fulfillment on a medical service platform, the platform receives a service fulfillment commencement request from the user. In response to the service fulfillment commencement instruction, the platform determines the service rights indicated by the instruction. These service rights define the service process for the medical service, such as the process for a physical examination or a manual appointment booking service. Next, the platform obtains the service link for the service rights and the multiple service nodes constituting that link. The service process for the service rights is implemented through the service link, and each service node indicates which steps are required to complete the entire service process. For example, if the service right is a physical examination, the service nodes on the service link could include appointment booking, queuing, obtaining the examination report, and report interpretation. This allows for the subsequent allocation of personnel to assist users with appointment booking, queuing, and report retrieval through the service nodes on the service link. It also enables doctors to interpret examination reports online, improving service efficiency and the overall response efficiency of the service process.

[0066] 102. According to the order of multiple service nodes in the service chain, push service reminders to the service personnel corresponding to the multiple service nodes so that the service personnel can execute the service content indicated by the corresponding service node.

[0067] In this embodiment, after responding to a service fulfillment commencement instruction, the medical service platform sends reminders to service nodes along the service chain according to the service process. Upon receiving the reminders, the service personnel corresponding to each service node complete the service content for that node. This online-offline service model can reduce labor costs and provide users with efficient services. Specifically, when sending service reminders, they can be pushed to service personnel corresponding to multiple service nodes in the order they appear on the service chain, enabling them to execute the service content instructed by the corresponding service node.

[0068] 103. When a service node receives service progress information uploaded by a service personnel from among multiple service nodes, the service progress information is marked with the node identifier of the service node, and the marked service progress information is pushed to the user who initiated the service fulfillment start command.

[0069] The medical service platform continuously monitors the service nodes in the service chain and tracks the fulfillment of service rights in real time. When it detects that a service node has received service progress information, it updates the service fulfillment status. This model, which combines proactive system outreach with manual service advancement, changes the previous approach where service status was entirely driven by manual intervention, improving service timeliness and overall service response efficiency.

[0070] When a service node receives service progress information uploaded by a service worker, it indicates that the service worker corresponding to that service node has completed the service content instructed by that service node. This service progress information can be registration information, physical examination information, etc. To ensure that users know which service node the information was uploaded to, the medical service platform uses a node identifier to mark the service progress information and updates the status of the service node on the platform. The node identifier can be the name of the service provided by that node. Subsequently, the medical service platform pushes the marked service progress information to the user who initiated the service fulfillment start command, allowing the user to receive timely feedback from the service node without having to return offline, thus providing convenience.

[0071] The method provided in this application embodiment, in response to a service fulfillment commencement command, determines the service rights indicated by the service fulfillment commencement command, the service link for obtaining the service rights, and multiple service nodes constituting the service link. According to the order of the multiple service nodes on the service link, service reminders are pushed to the service personnel corresponding to the multiple service nodes, so that the service personnel can execute the service content indicated by the corresponding service node. When a service node receives service progress information uploaded by a service personnel, the service progress information is marked using the node identifier of the service node, and the marked service progress information is pushed to the user who initiated the service fulfillment commencement command. Through a model of proactive system outreach combined with manual service promotion, service timeliness is improved, labor costs are reduced, and the response efficiency of the entire service process is increased, thereby enhancing the user experience.

[0072] Furthermore, as a refinement and extension of the specific implementation methods of the above embodiments, in order to fully illustrate the specific implementation process of this embodiment, this application provides another method for pushing progress information, such as... Figure 2 As shown, the method includes:

[0073] 201. In response to the service performance commencement instruction, determine the service rights indicated by the service performance commencement instruction, obtain the service link of the service rights, and the multiple service nodes constituting the service link.

[0074] Considering that relying on manual, continuous tracking of the entire medical service fulfillment process would lead to delays in service timeliness and low overall service response efficiency, this application uses a medical service platform to monitor the entire service fulfillment process, update the service fulfillment status in real time, and push the service fulfillment status to the user. In this embodiment, the medical service platform may include multiple service benefits. The user selects one service benefit, confirms the purchase, and applies for service fulfillment. For example, the user purchases a manual registration service on the medical service platform and submits a registration request for a specified hospital on a specified date. Therefore, the medical service platform receives a service fulfillment start instruction, determines the service benefit indicated by the instruction, obtains the service link of the service benefit, determines the service fulfillment process of the service benefit through the service link, and then obtains multiple service nodes constituting the service link from the service benefit to determine the steps required for the entire service process of the service benefit. Through the service nodes, the user can know which stage of the service fulfillment has been completed and the corresponding service progress information. Simultaneously, the medical service platform can monitor each step of the service benefit, promptly detect and handle abnormal feedback information, and improve the quality of medical services.

[0075] 202. For each of the multiple service nodes, query the service content indicated by the service node in the service rights, obtain multiple candidate service personnel with the ability to execute the service content, and select one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the service node.

[0076] In this embodiment, the service rights include not only the service chain and the multiple service nodes constituting the service chain, but also the service content of each service node. For example, if a service node is for a physical examination appointment, then the service content of that service node could be the appointment of a person to a designated hospital for a physical examination. In this way, the medical service platform can filter out multiple candidate service personnel according to the service content of the service node and quickly assign a service personnel to that node. Therefore, for each of the multiple service nodes, firstly, the service content indicated by the service node in the service rights is queried to determine the service content for each service node to execute the service rights. Next, multiple candidate service personnel with the ability to execute the service content are obtained, and one candidate service personnel is selected from among the multiple service candidates as the service personnel corresponding to the service node. The selected candidate service personnel is either currently idle or has the fewest currently associated service contents to be executed. For example, after a user purchases a manual appointment booking service on a medical service platform and submits a request for an appointment at a specified hospital on a specified date, the platform filters multiple booking agents within that hospital based on the request. It then selects the agent with no booking duties or the fewest available duties to book the appointment. This eliminates the need for offline processing, saving users significant time and effort. Simultaneously, the medical service platform, through both online and offline services, meets diverse user needs and improves service quality.

[0077] 203. Using the service content indicated by each service node, generate a service reminder carrying the service content for each service node, resulting in multiple service reminders. In accordance with the order of the multiple service nodes on the service link, push the service reminders generated for the service nodes to the service personnel corresponding to each service node in sequence.

[0078] To reduce the time spent on manual follow-up of service fulfillment, the medical service platform proactively contacts users to inform them of the service fulfillment status, allowing them to stay informed about the progress. Furthermore, it generates service reminders for each service node and pushes them to the relevant staff, promptly reminding them to perform the corresponding service tasks. This eliminates the need for continuous manual follow-up of service fulfillment progress; the medical service platform monitors the entire service chain and promptly sends reminders to service personnel, improving their service efficiency.

[0079] Therefore, in this embodiment, service reminders carrying service content are generated for each service node using the service content indicated by each service node, resulting in multiple service reminders. Examples include registration reminders for manual registration services, item testing reminders for physical examination services, and information approval reminders. Then, according to the order of the multiple service nodes in the service chain, the service reminders generated for each service node are pushed sequentially to the service personnel corresponding to each service node. For example, after a user purchases a manual registration service on a medical service platform and submits a registration request for a specified hospital and date, the medical service platform assigns a registration personnel based on the registration request and notifies the registration personnel of the corresponding registration information via message or SMS. The registration personnel receive the service reminder, understand the need to make an appointment, and then use the received registration information to complete the registration at the designated hospital's registration window. Therefore, by having the medical service platform proactively push service reminders to service personnel, informing them of the service content to be performed, without requiring service personnel to communicate with users to obtain service content, the service efficiency of service personnel can be improved, further enhancing service timeliness.

[0080] In an optional implementation, if a service worker at a service node in a service chain needs service progress information uploaded by a service worker at the previous service node when performing service content, that is, if the service node is detected as an associated service node, then the service worker at this service node must wait for the service worker at the previous service node to complete the service and upload the service progress information before the service worker at this service node can perform the corresponding service content. Therefore, the specific process of pushing the service reminder generated for the associated service node to the service worker at the associated service node is as follows:

[0081] First, if a service node is detected as an associated service node, the previous service node of the associated service node is determined on the service chain. The service content of the associated service node is executed according to the service progress information of the previous service node. For example, the service nodes of a physical examination service include physical examination appointment, test items, obtaining physical examination report, report interpretation, etc. When the doctor interprets the report, he needs the physical examination report. That is, the service personnel of the service node of obtaining physical examination report need to upload the user's physical examination report to the medical service platform before the doctor can perform the report interpretation service node.

[0082] Next, it continuously checks whether the service progress information uploaded by the previous service node has been received. That is, it checks whether the medical service platform has received the service progress information uploaded by the service personnel of the previous service node. When it is detected that the service progress information has been received by the previous service node, it means that the medical service platform has received the service progress information uploaded by the service personnel of the previous service node. It then queries the service content indicated by the related service node in the service rights and generates a service reminder for the related service node, which carries the service content indicated by the related service node and the service progress information received by the previous service node. For example, after a user purchases a physical examination service and completes the test, according to the service chain of the physical examination service, the service content indicated by the next service node is that the service personnel obtain the user's physical examination report. Therefore, it is necessary to wait for the test personnel of the previous service node to upload the user's physical examination information. The medical service platform will then generate a service reminder together with the information of the uploaded physical examination information and the information of the physical examination report to be obtained.

[0083] Subsequently, multiple candidate service personnel capable of executing the service content instructed by the associated service node are identified. One candidate service personnel is selected from these candidates as the service personnel corresponding to the associated service node. The selected candidate service personnel is either currently idle or has the fewest associated services pending execution. Finally, the service reminder generated for the associated service node is pushed to the service personnel corresponding to the associated service node. For example, after a medical service platform selects a report retrieval agent, a service reminder including information that the physical examination information has been uploaded and that the physical examination report is yet to be retrieved is pushed to the report retrieval agent. After retrieving the report, the report retrieval agent uploads the physical examination report to the medical service platform.

[0084] In this way, the medical service platform continuously monitors the associated service nodes. When it detects service progress information uploaded by the service personnel of the previous service node, it then prompts the corresponding service personnel of the associated service node to execute the service content. This avoids interruptions in the service fulfillment process, preventing the service personnel of the associated service nodes from waiting continuously. It can promptly advance the service, form a good service work order, and further improve the response efficiency of the entire service process.

[0085] 204. For each of the multiple service nodes, continuously detect whether each service node has received the uploaded service progress information. When it is detected that a service node has received the uploaded service progress information, obtain the node identifier of the service node and use the node identifier to mark the service progress information.

[0086] In this embodiment of the application, in order to update the status of the service fulfillment process in real time, the medical service platform sets a node identifier for each service node in the service chain. Through the node identifier, users can query the fulfillment progress of service rights on the medical service platform and know which service node uploaded the received service progress information. At the same time, the medical service platform can also detect whether the service node has received the service progress information through the node identifier, so as to realize real-time monitoring of the fulfillment process.

[0087] Therefore, for each of the multiple service nodes, it is continuously monitored whether each service node has received the uploaded service progress information to determine whether the service content instructed by the service node has been completed. When a service node receives the uploaded service progress information, it indicates that the service content instructed by that service node has been completed. For example, after a person successfully registers for an appointment, they fill in the registration information into the medical service platform and upload the registration information by clicking the offline registration success button. Next, the node identifier of the service node is obtained, and the service progress information is marked using the node identifier, thereby synchronizing the service status of the offline service personnel to the online system and realizing the status update of the service fulfillment process.

[0088] 205. Query the user who initiated the service fulfillment start command, obtain the user's preset reminder recipients, and push the marked service progress information to the reminder recipients.

[0089] In this embodiment, to provide users with a better service experience and allow them to understand the real-time progress of service fulfillment, the medical service platform pushes the marked service progress information of each service node in the service chain to the user, enabling the user to know the service status and feedback results of each service node. Specifically, the medical service platform queries the user who initiated the service fulfillment start command, obtains the user's preset reminder recipient, which can be one or more of email address, in-application account, and personal terminal information. Then, the marked service progress information is pushed to the reminder recipient. For example, after a user purchases a manual registration service and submits a registration request, the medical service platform assigns a registration person according to the registration request and notifies the user of the assigned registration person and their information via in-application message. Once the registration person successfully registers and uploads the specific registration information, the medical service platform will notify the user of the successful registration and the specific registration information via in-application message or SMS. In this way, the medical service platform can promptly provide feedback on the status of the service fulfillment process to the user, so that the user can more clearly understand which stage of the service fulfillment process they are in and what the feedback information is at each stage, thus improving the user experience.

[0090] In practical applications, service fulfillment processes may experience interruptions, leading to timeouts in service progress information feedback. For example, a doctor may fail to review a user's medical examination information within the stipulated time, or a registration request posted by the medical service platform may not be accepted by any registration staff. Therefore, the medical service platform will send timeout reminders to the service personnel corresponding to the service nodes. Thus, in an optional implementation scheme, the following process can also be performed:

[0091] First, when a service node is detected to have not received the uploaded service progress information within a preset service time range, it is determined that the service progress information feedback of the service node has timed out. The first node identifier and the first service content of the service node are then obtained. The preset time range can be 30 minutes, 60 minutes, etc., and the first node identifier can be the name of the service provided by the service node, such as manual registration or physical examination information review. The first service content can be the service provided by the service node, such as manual registration or physical examination information review.

[0092] Next, the service content is labeled using a first-node identifier, generating a service timeout reminder carrying the labeled first-node service content. This allows service personnel to promptly complete the corresponding service upon seeing the reminder, preventing service fulfillment from stalling. Subsequently, the service personnel corresponding to the service node are identified, and the service timeout reminder is pushed to them. Their terminals then display the reminder according to preset reminder methods, including highlighted reminders and flashing reminders. It should be noted that the push method can be email, SMS, IM (Instant Messaging) message notifications, AI (Artificial Intelligence) calls, etc., and the medical service platform can proactively reach users, customer service, health managers, and service doctors based on service type. For example, after a user's physical examination information has been uploaded, if the medical service platform detects that the examining doctor has not approved the user's physical examination information within 30 minutes, the doctor platform will record the monitored user's physical examination information and display a pending item on the current examining doctor's workbench, while also highlighting the item in red to prompt the examining doctor to approve the user's physical examination information. After the examining doctor completes the approval, the next service node in the service chain will be moved, and the medical service platform will notify the health manager by email so that the health manager can communicate with the user.

[0093] Therefore, when the medical service platform detects a break in service fulfillment, it will notify the examining doctor, registration staff, and other business parties in a timely manner. This eliminates the need for health managers or customer service to continuously track the entire service fulfillment process. In this way, the medical service platform proactively informs the examining doctor of the current service status, actively promotes the progress of service fulfillment, reduces the time spent on manual follow-up of the service fulfillment process, frees up human resources costs, and improves the doctor's response speed.

[0094] In practical applications, service fulfillment processes may experience interruptions, leading to service failures. For example, if a person registers for an appointment offline but no appointments are available, the medical service platform needs to notify the corresponding customer service representative so that the representative can communicate with the user. Therefore, in one optional implementation scheme, the following process can also be performed:

[0095] First, when a service node receives a service failure feedback—for example, a user purchases a manual appointment booking service and submits an appointment booking request for a tertiary hospital outpatient clinic three days later on the medical service platform—but the booking agent finds that the clinic is already booked offline, and the appointment booking order fails to be submitted on the medical service platform, the medical service platform will receive a service failure feedback. Then, the medical service platform obtains the service node's second node identifier and second service content. The second node identifier can be the name of the service provided by that service node, such as appointment booking, and the second service content can be the service provided by that service node, such as making an appointment.

[0096] Next, the second service content is labeled using a second node identifier, generating a service failure notification carrying the labeled second service content. Users can then use the second node identifier to identify which stage of the service failed. Following this, multiple candidate communicators are retrieved, and one is selected as the target communicator. The target communicator is either currently idle or has the fewest pending communication tasks. Then, the medical service platform queries the user who initiated the service fulfillment start command and obtains the user's user identifier. This identifier can be the user's phone number, email address, in-app account, personal terminal information, etc. The user identifier enables the communicator to communicate with the user to handle service rights related to the service failure.

[0097] Finally, the healthcare service platform pushes user identification and service failure alerts to the target communication personnel, enabling them to identify the user indicated by the user identification. The platform then displays the service failure alert to the user according to a preset communication method, which can be any one of telephone, online chat, email, SMS, or chatbot communication. For example, upon receiving feedback about a failed appointment booking, the platform notifies the corresponding customer service representative via email and simultaneously pushes the user's relevant information to the representative, allowing them to communicate with the user to cancel the appointment or modify the booking time. This allows the platform to monitor the service fulfillment process in real time, promptly detect service failures, address service failures in a timely manner, improve the service process for fulfilling service rights, enhance user experience, and further increase user engagement.

[0098] In practical applications, users may cancel service fulfillment after the service fulfillment process is completed. For example, if a user purchases a manual registration service and successfully registers, but then applies to cancel the registration on the medical service platform, the platform needs to process the cancellation. Therefore, in one optional implementation, the following process can also be performed:

[0099] After a user submits a service cancellation request on the healthcare service platform, the platform responds to the cancellation instruction by identifying the service rights indicated in the instruction. Among the multiple service nodes included in these rights, the platform identifies the node that received the cancellation instruction and designates it as a pending cancellation node. This node is then assigned to service personnel to perform the cancellation. Next, the platform obtains the designated node identifier for the pending cancellation node and generates a cancellation notification carrying this identifier. This identifier informs the assigned service personnel that the service content for the pending cancellation node needs to be cancelled. Subsequently, the platform queries the historical service personnel who performed the service content for the pending cancellation node and sends cancellation notifications to them, enabling them to cancel the service. For example, when the platform receives a cancellation request for an appointment, it determines that the user needs to cancel at the hospital window. Therefore, the platform generates a cancellation notification and sends it to the user who completed the registration request, allowing them to cancel the appointment. This provides extended healthcare services, enhances the user experience, and improves the overall service fulfillment process.

[0100] The method provided in this application embodiment, in response to a service fulfillment commencement command, determines the service rights indicated by the service fulfillment commencement command, the service link for obtaining the service rights, and multiple service nodes constituting the service link. According to the order of the multiple service nodes on the service link, service reminders are pushed to the service personnel corresponding to the multiple service nodes, so that the service personnel can execute the service content indicated by the corresponding service node. When a service node receives service progress information uploaded by a service personnel, the service progress information is marked using the node identifier of the service node, and the marked service progress information is pushed to the user who initiated the service fulfillment commencement command. Through a model of proactive system outreach combined with manual service promotion, service timeliness is improved, labor costs are reduced, and the response efficiency of the entire service process is increased, thereby enhancing the user experience.

[0101] Furthermore, as Figure 1 To specifically implement the method, this application provides a progress information push device, such as... Figure 3A As shown, the device includes: an acquisition module 301, a push module 302, and a labeling module 303.

[0102] The acquisition module 301 is used to, in response to a service fulfillment start instruction, determine the service rights indicated by the service fulfillment start instruction, as well as the service link for acquiring the service rights and the multiple service nodes constituting the service link;

[0103] The push module 302 is used to push service reminders to the service personnel corresponding to the multiple service nodes in the order of the multiple service nodes on the service link, so that the service personnel can perform the service content indicated by the corresponding service node;

[0104] The annotation module 303 is used to annotate the service progress information using the node identifier of the service node when a service node receives the service progress information uploaded by the service personnel based on the service progress information of one of the plurality of service nodes, and to push the annotated service progress information to the user who initiated the service fulfillment start command.

[0105] In a specific application scenario, the push module 302 is further configured to: query the service content indicated by the service node in the service rights for each of the plurality of service nodes; obtain a plurality of candidate service personnel capable of executing the service content; and select one candidate service personnel from the plurality of candidate service personnel as the service personnel corresponding to the service node, wherein the selected candidate service personnel is either a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed; generate service reminders carrying service content for each service node using the service content indicated by each service node, thereby obtaining a plurality of service reminders; and push the service reminders generated for the service nodes to the service personnel corresponding to each service node in sequence according to the order of the plurality of service nodes on the service link.

[0106] In specific application scenarios, the push module 302 is further configured to: if a service node is detected as an associated service node, determine the previous service node of the associated service node on the service link, wherein the service content of the associated service node indicates that the service content of the associated service node is executed according to the service progress information of the previous service node; continuously detect whether the uploaded service progress information is received based on the previous service node; when it is detected that the service progress information is received based on the previous service node, query the service content indicated by the associated service node in the service rights, generate a service reminder for the associated service node carrying the service content indicated by the associated service node and the service progress information received by the previous service node; obtain multiple candidate service personnel with the ability to execute the service content indicated by the associated service node, and select one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the associated service node, wherein the selected candidate service personnel is a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed; and push the service reminder generated for the associated service node to the service personnel corresponding to the associated service node.

[0107] In specific application scenarios, the annotation module 303 is also used to continuously detect whether each of the multiple service nodes has received the uploaded service progress information; when a service node is detected to have received the uploaded service progress information, the node identifier of the service node is obtained, and the service progress information is annotated using the node identifier; the user who initiated the service fulfillment start command is queried, the user's preset reminder recipient is obtained, and the annotated service progress information is pushed to the reminder recipient, wherein the reminder recipient is one or more of the following: email address, in-application account, and personal terminal information.

[0108] In specific application scenarios, such as Figure 3B As shown, the device also includes: a service reminder module 304, a service failure module 305, and a service cancellation module 306.

[0109] The service reminder module 304 is used to, when it is detected that a service node has not received uploaded service progress information within a preset service time range, obtain the first node identifier and the first service content of the service node; mark the service content with the first node identifier to generate a service timeout reminder carrying the marked first service content; determine the service personnel corresponding to the service node, and push the service timeout reminder to the service personnel so that the service personnel's terminal displays the service timeout reminder in a preset reminder mode, wherein the preset reminder mode includes a red highlight reminder and a flashing reminder;

[0110] The service failure module 305 is used to, when receiving service failure feedback based on a service node, obtain the second node identifier and second service content of the service node; mark the second service content using the second node identifier to generate a service failure reminder carrying the marked second service content; obtain multiple candidate communication personnel, select one candidate communication personnel as the target communication personnel, wherein the target communication personnel is the candidate communication personnel currently in an idle state or the candidate communication personnel with the fewest currently associated pending communication tasks; query the user who initiated the service fulfillment start command and obtain the user's user identifier; push the user identifier and the service failure reminder to the target communication personnel, so that the target communication personnel can identify the user indicated by the user identifier and display the service failure reminder to the user according to a preset communication method, wherein the preset communication method is any one of telephone communication, online conversation communication, email communication, SMS communication, and robot communication;

[0111] The service cancellation module 306 is configured to respond to a service cancellation instruction, determine the service rights indicated by the service cancellation instruction, identify the service node that received the service cancellation instruction from among a plurality of service nodes included in the service rights, and designate the service node as a service node to be cancelled; obtain a designated node identifier of the service node to be cancelled, generate a service cancellation reminder carrying the designated node identifier; query the historical service personnel who performed the service content of the service node to be cancelled, and send the service cancellation reminder to the historical service personnel so that the historical service personnel can perform a service cancellation operation on the service node to be cancelled.

[0112] The apparatus provided in this application embodiment, in response to a service fulfillment start command, determines the service rights indicated by the service fulfillment start command, the service link for obtaining the service rights, and multiple service nodes constituting the service link. According to the order of the multiple service nodes on the service link, it pushes service reminders to the service personnel corresponding to the multiple service nodes, so that the service personnel can execute the service content indicated by the corresponding service node. When a service node receives service progress information uploaded by a service personnel, it marks the service progress information using the node identifier of the service node, and pushes the marked service progress information to the user who initiated the service fulfillment start command. Through a model of proactive system outreach combined with manual service promotion, it improves service timeliness, reduces labor costs, and simultaneously improves the response efficiency of the entire service process, thereby enhancing the user experience.

[0113] It should be noted that other corresponding descriptions of the functional units involved in the progress information push device provided in this application embodiment can be found in the following references. Figure 1 and Figure 2 The corresponding descriptions in [the document] will not be repeated here.

[0114] In an exemplary embodiment, see Figure 4 The invention also provides a computer device including a bus, a processor, a memory, and a communication interface. It may also include an input / output interface and a display device, wherein the various functional units can communicate with each other via the bus. The memory stores a computer program, and the processor executes the program stored in the memory to perform the progress information push method described in the above embodiments.

[0115] A readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the progress information push method.

[0116] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented in hardware or by using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computer device (such as a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0117] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application.

[0118] Those skilled in the art will understand that the modules in the apparatus of the implementation scenario can be distributed within the apparatus of the implementation scenario as described, or they can be located in one or more apparatuses different from this implementation scenario, with corresponding changes. The modules of the above-described implementation scenario can be combined into one module, or they can be further divided into multiple sub-modules.

[0119] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of the implementation scenario.

[0120] The above disclosures are only a few specific implementation scenarios of this application. However, this application is not limited to these. Any variations that can be conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A method for pushing progress information, characterized in that, include: In response to a service fulfillment commencement instruction, determine the service rights indicated by the service fulfillment commencement instruction, the service link for acquiring the service rights, and the multiple service nodes constituting the service link; According to the order of the multiple service nodes on the service link, service reminders are pushed to the service personnel corresponding to the multiple service nodes so that the service personnel can execute the service content indicated by the corresponding service node. This includes: if a service node is detected as an associated service node, then determining the previous service node of the associated service node on the service link, wherein the service content of the associated service node indicates that the service content of the associated service node is executed according to the service progress information of the previous service node; continuously detecting whether the uploaded service progress information is received based on the previous service node; when it is detected that the service progress information is received based on the previous service node, querying the service content indicated by the associated service node in the service rights, and generating a service reminder for the associated service node carrying the service content indicated by the associated service node and the service progress information received by the previous service node; obtaining multiple candidate service personnel with the ability to execute the service content indicated by the associated service node, and selecting one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the associated service node, wherein the selected candidate service personnel is a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed; and pushing the service reminder generated for the associated service node to the service personnel corresponding to the associated service node. When a service progress information uploaded by a service personnel is received by one of the multiple service nodes, the service progress information is marked with the node identifier of the service node, and the marked service progress information is pushed to the user who initiated the service fulfillment start command. Specifically, when a service node is detected to have not received uploaded service progress information within a preset service time range, the first node identifier and first service content of the service node are obtained; the service content is marked using the first node identifier, and a service timeout reminder carrying the marked first service content is generated; the service personnel corresponding to the service node are determined, and the service timeout reminder is pushed to the service personnel so that the service personnel's terminal displays the service timeout reminder according to a preset reminder method, wherein the preset reminder method includes a red highlight reminder and a flashing reminder.

2. The method according to claim 1, characterized in that, The step of pushing service reminders to the service personnel corresponding to the multiple service nodes in the order of the multiple service nodes on the service link includes: For each of the plurality of service nodes, query the service content indicated by the service node in the service rights; Obtain multiple candidate service personnel with the ability to execute the service content, and select one candidate service personnel from the multiple candidate service personnel as the service personnel corresponding to the service node, wherein the selected candidate service personnel is either a candidate service personnel currently in an idle state or a candidate service personnel with the fewest currently associated service contents to be executed. By utilizing the service content indicated by each service node, a service reminder carrying the service content is generated for each service node, resulting in multiple service reminders; According to the order of the multiple service nodes on the service link, the service reminders generated for the service nodes are pushed to the service personnel corresponding to each service node in sequence.

3. The method according to claim 1, characterized in that, The step of, when a service node receives service progress information uploaded by a service user based on one of the plurality of service nodes, marking the service progress information with the node identifier of the service node, and pushing the marked service progress information to the user who initiated the service fulfillment start command, includes: For each of the plurality of service nodes, continuously detect whether each service node has received the uploaded service progress information; When a service node is detected to have received uploaded service progress information, the node identifier of the service node is obtained, and the service progress information is marked using the node identifier. The system queries the user who initiated the service fulfillment start command, obtains the user's preset reminder recipient, and pushes the marked service progress information to the reminder recipient. The reminder recipient is one or more of the following: email address, in-application account, and personal terminal information.

4. The method according to claim 1, characterized in that, The method further includes: When a service failure feedback is received based on a service node, the second node identifier and the second service content of the service node are obtained; The second service content is labeled using the second node identifier, and a service failure notification carrying the labeled second service content is generated; Multiple candidate communicators are obtained, and one candidate communicator is selected from the multiple candidate communicators as the target communicator. The target communicator is either a candidate communicator that is currently idle or a candidate communicator with the fewest pending communication tasks currently associated with it. Query the user who initiated the service fulfillment start command and obtain the user's user identifier; The user identifier and the service failure notification are pushed to the target communication personnel so that the target communication personnel can identify the user indicated by the user identifier and display the service failure notification to the user according to a preset communication method, which is any one of telephone communication, online conversation communication, email communication, SMS communication, and robot communication.

5. The method according to claim 1, characterized in that, The method further includes: In response to a service cancellation instruction, the service rights indicated by the service cancellation instruction are determined, and the service node that received the service cancellation instruction is identified among a plurality of service nodes included in the service rights, and the service node is designated as a service node to be cancelled. Obtain the specified node identifier of the service node to be cancelled, and generate a service cancellation reminder carrying the specified node identifier; The system queries the historical service personnel who performed the service content of the service node to be cancelled, and sends the service cancellation reminder to the historical service personnel so that they can perform the service cancellation operation on the service node to be cancelled.

6. A progress information push device, characterized in that, include: The acquisition module is used to, in response to a service fulfillment start instruction, determine the service rights indicated by the service fulfillment start instruction, as well as the service link for acquiring the service rights and the multiple service nodes constituting the service link; The push module is used to push service reminders to service personnel corresponding to the multiple service nodes in the order of the service links, so that the service personnel can execute the service content indicated by the corresponding service node. This includes: if a service node is detected as an associated service node, determining the previous service node of the associated service node in the service links, wherein the service content instruction of the associated service node is executed according to the service progress information of the previous service node; continuously detecting whether uploaded service progress information has been received based on the previous service node; and when it is detected that service progress information has been received based on the previous service node, querying the associated service node... The system retrieves the service content indicated in the service rights, generates a service reminder for the associated service node carrying the service content indicated by the associated service node and the service progress information received by the previous service node; it acquires multiple candidate service personnel capable of executing the service content indicated by the associated service node, and selects one candidate service personnel from among the multiple candidate service personnel as the service personnel corresponding to the associated service node, wherein the selected candidate service personnel is either currently idle or has the fewest currently associated service contents to be executed; and pushes the service reminder generated for the associated service node to the service personnel corresponding to the associated service node. The annotation module is used to annotate the service progress information using the node identifier of the service node when the service progress information uploaded by the service personnel is received by one of the multiple service nodes, and to push the annotated service progress information to the user who initiated the service fulfillment start command. The service reminder module is used to, when a service node is detected to have not received uploaded service progress information within a preset service time range, obtain the first node identifier and first service content of the service node; mark the service content using the first node identifier to generate a service timeout reminder carrying the marked first service content; determine the service personnel corresponding to the service node, and push the service timeout reminder to the service personnel so that the service personnel's terminal displays the service timeout reminder according to a preset reminder method, wherein the preset reminder method includes a red highlight reminder and a flashing reminder.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images