Triage methods, devices, equipment, and storage media for online consultation pre-diagnosis rooms

Abstract

This application relates to the fields of computer and smart healthcare technology, specifically disclosing a triage method, device, equipment, and storage medium for an online pre-consultation room. The method includes: receiving a patient's consultation request; determining whether a target doctor is specified in the consultation request; if no target doctor is specified, determining whether a corresponding channel doctor exists based on the channel through which the consultation request was received; if no corresponding channel doctor exists, establishing a correspondence between the backup doctor and the patient by using a fallback doctor; configuring message scripts according to a first scenario rule; and pushing the message scripts to the patient. The triage method for the online pre-consultation room provided by this application offers patients a preliminary pre-consultation, significantly improving the efficiency of subsequent communication between patients and renowned doctors, reducing business processing pressure, and facilitating business iteration and error troubleshooting.

Description

Technical Field

[0001] This application relates to the fields of computer and smart healthcare technology, specifically to a triage method, device, equipment, and storage medium for an online consultation and pre-diagnosis room. Background Technology

[0002] With the development of internet-based healthcare, patients are gradually accepting online consultations. Online consultation programs can provide patients with a large number of doctors, including renowned specialists from various regions and hospitals.

[0003] The availability of renowned doctors has increased the pool of physicians. However, due to a lack of direct knowledge about these doctors, patients often don't know which one to consult online. Even if patients can accurately identify the doctor they want to consult, after contacting the doctor, they still need to start communicating from the most basic descriptions of their symptoms and needs, making online communication between patients and doctors time-consuming and inefficient.

[0004] Therefore, existing technologies lack a preliminary diagnosis procedure and a method that can automatically triage patients to precise specialist clinics. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a triage method, apparatus, equipment, and storage medium for an online consultation pre-diagnosis room. This provides a pre-processing procedure for online consultations, enabling automatic triage of patients to precise specialist clinics for pre-diagnosis consultations, thereby improving the accuracy and efficiency of online consultations.

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

[0007] Firstly, a triage method for an online pre-diagnosis consultation room is provided, the method comprising:

[0008] Receive patient consultation requests and determine whether a target doctor is specified in the consultation request;

[0009] If no target doctor is specified, the existence of a corresponding doctor will be determined based on the channel through which the consultation request was received.

[0010] If there is no corresponding channel doctor, then the backup doctor will be used as the receiving doctor, and a correspondence between the backup doctor and the patient will be established.

[0011] Configure the message script according to the first scenario rules, and push the message script to the patient.

[0012] Secondly, a triage device for an online pre-diagnosis consultation room is provided, the device comprising:

[0013] The target doctor determination unit is used to receive the patient's consultation request and determine whether the consultation request specifies a target doctor.

[0014] The channel doctor judgment unit is used to determine whether a corresponding channel doctor exists based on the incoming channel of the consultation request when no target doctor is specified.

[0015] The "backup doctor" unit is used to establish a correspondence between the backup doctor and the patient when there is no corresponding channel doctor.

[0016] The first triage unit is used to configure message scripts according to the first scenario rules and push the message scripts to patients.

[0017] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described online consultation pre-diagnosis room triage method.

[0018] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when instructed by a processor, implements the steps of the above-described online consultation and triage method.

[0019] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0020] The online consultation pre-consultation room triage method provided in this application first determines whether the patient has specified a target doctor. If the patient has not specified a target doctor, it determines whether the patient entered the consultation through a specific channel. If the patient did not enter the consultation through a specific channel, a backup doctor is used as the receiving doctor, and a pre-consultation room is assigned to the patient for triage using configured message scripts. This online consultation pre-consultation room triage method directly triages patients to the virtual pre-consultation room of the corresponding virtual target doctor when the patient clearly indicates that they need to consult a renowned doctor, providing pre-consultation and significantly improving the efficiency of subsequent communication between the patient and the renowned doctor. When the patient initiates a consultation through a specific channel, a virtual channel doctor is used to select the most suitable doctor from a small pool of virtual target doctors, reducing the workload of business processing. When the patient is unsure how to select a renowned doctor or a specific channel, the backup doctor uniformly redirects the patient to a pre-consultation room, greatly improving the efficiency and accuracy of pre-consultation triage and facilitating business iteration and error detection. Attached Figure Description

[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0022] Figure 1A schematic diagram illustrating the application environment of a triage method in an online consultation pre-diagnosis room according to an embodiment of this application is shown.

[0023] Figure 2 A flowchart illustrating a triage method in an online consultation pre-diagnosis room according to an embodiment of this application is shown.

[0024] Figure 3 A flowchart illustrating a triage method in an online consultation pre-diagnosis room according to another embodiment of this application is shown;

[0025] Figure 4 A schematic diagram of the structure of a triage device in an online consultation pre-diagnosis room according to an embodiment of this application is shown;

[0026] Figure 5 This illustration shows a schematic diagram of the structure of a computer device according to an embodiment of the present application;

[0027] Figure 6 A schematic diagram of the structure of a computer device according to another embodiment of this application is shown. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] To enable those skilled in the art to more clearly understand the technical solutions provided in the various embodiments of this application, the scenarios involved in the technical solutions of this application will be introduced first.

[0030] The triage method for online consultation pre-diagnosis rooms proposed in this application is a preliminary procedure before patients directly contact a physical doctor during online consultations. This preliminary procedure aims to automatically triage patients to precise pre-diagnosis rooms based on their consultation requests. The pre-diagnosis room in this application is a virtual pre-diagnosis room, with one virtual pre-diagnosis room corresponding to one virtual target doctor, and one virtual target doctor corresponding to one physical doctor. In other words, the virtual target doctor is equivalent to a "virtual clone" of the physical doctor in the virtual pre-diagnosis room. This virtual target doctor cannot provide actual, specific consultation services; its role is merely to pre-analyze the patient's consultation needs through pre-defined messaging to achieve a pre-diagnosis.

[0031] This application also provides virtual channel doctors and virtual backup doctors. One virtual channel doctor corresponds to multiple virtual target doctors, and multiple virtual target doctors correspond to virtual pre-diagnosis rooms. The channel doctor is essentially a pre-positioned virtual doctor configured for multiple virtual target doctors. This channel doctor uses messaging scripts to determine a suitable virtual target doctor for the patient, and then the target doctor takes over from the channel doctor to conduct a pre-diagnosis. One virtual backup doctor corresponds to all virtual target doctors, and all virtual target doctors correspond to virtual pre-diagnosis rooms. This backup doctor is essentially a general virtual doctor configured for all virtual target doctors. This backup doctor uses general messaging scripts to determine a suitable virtual target doctor for the patient, and then the target doctor takes over from the backup doctor to conduct a pre-diagnosis.

[0032] After a patient has a preliminary diagnosis through a virtual target doctor, they can then connect to the corresponding physical doctor for a direct online consultation.

[0033] The triage method for online consultation and pre-diagnosis rooms provided in this application embodiment can be applied to, for example... Figure 1 In this environment, the client communicates with the server via a network.

[0034] The client is used to instruct the patient who needs to conduct a consultation. The client can be, but is not limited to, devices with a display screen and input device such as personal computers, laptops, smartphones, tablets, and portable wearable devices. An online consultation application can be installed on the client, or an online consultation window can be embedded in the client through other applications. Patients can register by logging into the application or entering the online consultation window. In specific implementations, the server can provide a registration interface to the application or the online consultation window embedded in other applications, allowing patients to register by filling in registration information. After the registration information filled in by the patient is transmitted to the server, the server generates a corresponding user identifier for the patient, thus forming an account for that patient.

[0035] A single client can register multiple patients. The server generates a user identifier for each patient, thus establishing an account for each patient. Different patients can switch between online consultation windows embedded in the application or other applications, thereby enabling them to conduct online consultations under their respective user identifiers. One of the multiple patients registered on the client can also be designated as the master user, who has the authority to configure the registration information of other patients. That is, in addition to configuring their own registration information like other patient accounts, the master user can also add, delete, and edit the registration information of other patients.

[0036] The patient on the client side initiates a consultation request to the server, which then determines a virtual target doctor based on the consultation request, thereby conducting a preliminary consultation in the virtual pre-consultation room.

[0037] The server can be implemented using a standalone server or a service platform composed of multiple servers. The server stores a database, which may, but is not limited to, pre-store the mapping relationship between target doctors and actual doctors, the mapping relationship between channel doctors and target doctors, the mapping relationship between input ports and channel doctors, and the binding relationship between patient user identifiers and target doctors, channel doctors, or backup doctors. The database also pre-stores the script sets of target doctors, channel doctors, and backup doctors.

[0038] After receiving a patient's consultation request, the server determines whether a target doctor is specified in the consultation request. If no target doctor is specified, it determines whether a corresponding channel doctor exists based on the channel through which the consultation request was sent. If no corresponding channel doctor exists, a fallback doctor is used as the receiving doctor, and a correspondence is established between the fallback doctor and the patient. The message script is configured according to the first scenario rule and pushed to the patient.

[0039] The online consultation pre-consultation room triage method of this application first determines whether the patient has specified a target doctor. If the patient has not specified a target doctor, it determines whether the patient entered the consultation through a specific channel. If the patient has not entered the consultation through a specific channel, a backup doctor is used as the receiving doctor, and a pre-consultation room is assigned to the patient for triage using configured message scripts. This online consultation pre-consultation room triage method directly triages patients to the virtual pre-consultation room of the corresponding virtual target doctor when the patient clearly indicates that they need to consult a renowned doctor, providing pre-consultation and greatly improving the efficiency of subsequent communication between patients and renowned doctors. When patients initiate consultations through specific channels, a virtual channel doctor is used to select the most suitable doctor from a small range of virtual target doctors, reducing the workload of business processing. When patients are unsure how to select a renowned doctor or a specific channel, the backup doctor uniformly redirects them to a pre-consultation room, greatly improving the efficiency and accuracy of pre-consultation triage, facilitating business iteration and error detection.

[0040] Figure 2 This illustration shows a flowchart of a triage method for an online pre-diagnosis room according to an embodiment of this application. Figure 2 As shown, the method includes steps S210 to S240:

[0041] Step S210: Receive the patient's consultation request and determine whether the consultation request specifies a target doctor.

[0042] The server provides consultation services through online consultation windows embedded in applications or other applications. The consultation service can be provided in various forms, including a "Famous Doctors' Hall," scenario-based channels, and general consultations. The "Famous Doctors' Hall" includes multiple renowned doctors, each with a corresponding virtual target doctor. Scenario-based channels include multiple specific channels and multiple general channels; for example, specific channels include drug purchase channels and departmental channels, while general channels include physical examination channels. Each specific channel has its corresponding virtual channel doctor, while each general channel does not have its own virtual channel doctor; each general channel has a corresponding virtual backup doctor. General consultations correspond to a virtual backup doctor. Patients send consultation requests to the server on their client devices based on the consultation service.

[0043] The server determines whether a target doctor is specified in the received consultation request. For example, if the patient sends a consultation request through a "Famous Doctors' Hall" provided by an online consultation window embedded in the application or other applications, the server determines that a target doctor is specified in the request. If the patient sends a consultation request through a scenario-based classification channel or a general consultation format provided by an online consultation window embedded in the application or other applications, the server determines that a target doctor is not specified in the request. This determination is used to indicate whether to directly triage the patient to the virtual pre-consultation room of the virtual target doctor corresponding to the actual famous doctor for pre-consultation.

[0044] Step S220: If no target doctor is specified, determine whether there is a corresponding channel doctor based on the incoming channel of the consultation request.

[0045] If the server determines that the consultation request does not specify a target doctor, it further determines whether the patient accessed the consultation through a specific channel. One specific channel corresponds to one virtual channel doctor, and one virtual channel doctor corresponds to multiple virtual target doctors.

[0046] For example, if the server determines that the patient sent a consultation request through a specific channel within the scenario-based online consultation window embedded in the application or other applications, then a corresponding channel doctor exists. If the server determines that the patient sent a consultation request through a general or common consultation method within the scenario-based online consultation window embedded in the application or other applications, then no corresponding channel doctor exists. This determination is used to indicate whether to triage the patient to a virtual channel doctor. If triaged to a virtual channel doctor, the patient can be further triaged to the virtual pre-consultation room of the corresponding virtual target doctor for pre-consultation based on the question and answer, and by establishing a correspondence between the virtual channel doctor and multiple virtual target doctors.

[0047] In step S230, if there is no corresponding channel doctor, the backup doctor will be used as the receiving doctor to establish a correspondence between the backup doctor and the patient.

[0048] If the server determines that the patient did not access the consultation through a specific channel, meaning there is no corresponding doctor for that channel, then the server will assign a virtual fallback doctor as the receiving doctor, establishing a correspondence between the fallback doctor and the patient. This virtual fallback doctor is essentially a virtual all-purpose doctor; when the patient neither specifies a renowned doctor nor initiates a consultation through a specific channel, the virtual fallback doctor assigned by the server can provide the patient with general triage services.

[0049] The server establishes a mapping between the virtual backup doctor and the patient. In one possible scenario, if the patient is not consulting through regular channels or standard consultation methods for the first time, the server has already bound the virtual backup doctor and patient during previous consultations. Therefore, the server can directly retrieve the mapping between the virtual backup doctor and patient based on this binding relationship. In this case, the mapping retrieved by the server may also include the patient's previous consultation history through regular channels or standard consultation methods. In another possible scenario, if the patient is consulting through regular channels or standard consultation methods for the first time, the server performs an initial binding between the virtual backup doctor and patient. In this case, after establishing the mapping between the virtual backup doctor and patient, the server can record the patient's consultation with the virtual backup doctor in the mapping relationship.

[0050] Step S240: Configure the message script according to the first scenario rules and push the message script to the patient.

[0051] After the server establishes the correspondence between the virtual backup doctor and the patient, it can configure message scripts to be pushed to the patient. These message scripts are configured through a first-scenario rule. The first-scenario rule is used to determine the most suitable message arrangement rule for the patient from all virtual target doctors corresponding to the virtual backup doctor through question-and-answer dialogue. For example, message scripts configured based on the first-scenario rule may include scripts that ask for preliminary information such as the patient's description of their condition, the patient's location, and the purpose of the consultation, and these scripts will be pushed to the patient.

[0052] from Figure 2As shown in the method, the online consultation pre-diagnosis room triage method provided in this application receives the patient's consultation request and determines whether a target doctor is specified in the consultation request. If no target doctor is specified, it determines whether a corresponding channel doctor exists based on the incoming channel of the consultation request. If no corresponding channel doctor exists, a backup doctor is used as the receiving doctor, establishing a correspondence between the backup doctor and the patient. The message script is configured according to the first scenario rule and pushed to the patient. The online consultation pre-diagnosis room triage method of this application, when the patient clearly states that they need to consult a renowned doctor, directly triages the patient to the virtual pre-diagnosis room of the virtual target doctor corresponding to the renowned doctor, providing the patient with a preliminary pre-diagnosis, which greatly improves the efficiency of subsequent communication between the patient and the renowned doctor. When the patient initiates a consultation through a specific channel, the virtual channel doctor is used to select the most suitable doctor for the patient from a small range of virtual target doctors, reducing the business processing pressure. When the patient is unclear about how to select a renowned doctor and a specific channel, the backup doctor uniformly jumps to the pre-diagnosis room, which greatly improves the efficiency and accuracy of pre-diagnosis triage, and facilitates business iteration and error investigation.

[0053] In some optional implementations, in the above method, step S210 of receiving a patient's consultation request and determining whether a target doctor is specified in the consultation request includes: receiving the patient's consultation request; splitting the consultation request into statements according to parsing rules to obtain a user identifier character field, a doctor identifier character field, and an input channel character field; determining the patient's user identifier based on the user identifier character field; and determining whether the doctor identifier character field includes a doctor identifier.

[0054] The server receives patients' consultation requests through online consultation windows embedded in applications or other applications provided to the client.

[0055] Consultation requests can be transmitted to the server in formats such as URLs (Uniform Resource Locators). The server can parse the consultation request based on the parsing rules corresponding to the format of the transmitted consultation request. Taking the URL format as an example, the server splits the URL string into segments according to the parsing rules corresponding to the syntax rules of the URL format, obtaining character segments representing different meanings. These character segments include at least a user identifier character segment, a doctor identifier character segment, and an input channel character segment.

[0056] Since the consultation request is sent through a client logged in with a patient account, the user identifier field must contain a specific user identifier. Therefore, the server determines the patient's user identifier based on the specific content recorded in the user identifier field.

[0057] Patients may send consultation requests via the "Famous Doctors' Hall" feature in the client application or an online consultation window embedded in other applications, or they may not send consultation requests via the "Famous Doctors' Hall" feature. If a patient sends a consultation request via the "Famous Doctors' Hall" feature, the doctor identifier field in the consultation request will include a clear doctor identifier; if a patient does not send a consultation request via the "Famous Doctors' Hall" feature, the doctor identifier field in the consultation request will be empty. The server determines whether the consultation request specifies a target doctor by checking whether the doctor identifier field includes a doctor identifier.

[0058] In some optional implementations, in the above method, if no target doctor is specified in step S220, the existence of a corresponding channel doctor is determined based on the incoming channel of the consultation request, including: if the doctor identifier character field is empty, the patient's incoming port is determined based on the incoming channel character field; based on the incoming port, the corresponding channel doctor is matched from the channel doctor database, wherein the channel doctor database includes the correspondence between the incoming port and the channel doctor.

[0059] When the server determines that the doctor identifier field is empty, it indicates that the consultation request did not specify a target doctor. At this point, the server determines the patient's input port based on the input channel field.

[0060] Patients may send consultation requests to the server through specific channels within the online consultation window embedded in the client application or other applications. For example, a patient might send a consultation request through a medication purchase channel. Alternatively, patients may send consultation requests to the server through general channels or universal consultations within the online consultation window embedded in the client application or other applications. For example, a patient might send a consultation request through a physical examination channel. The incoming channel character field in the consultation request records the patient's incoming port, so the server determines the patient's incoming port based on the specific content recorded in the incoming channel character field.

[0061] The server pre-stores a channel doctor database, which indicates the mapping between incoming ports and channel doctors. Specific channels have their corresponding channel doctors, therefore the mapping between incoming ports and channel doctors for a specific channel is stored in this database. Ordinary channels or general consultations do not have corresponding channel doctors, so this data is not stored in the channel doctor database. The server matches the incoming port against the channel doctor database; if a match is found, the match is successful; otherwise, the match fails.

[0062] In some optional implementations, in the above method, if there is no corresponding channel doctor in step S230, the backup doctor is used as the receiving doctor to establish a correspondence between the backup doctor and the patient. This includes: if matching fails, the backup doctor is used as the receiving doctor; determining whether the user identifier and the backup doctor already have a binding relationship based on the patient's user identifier; if a binding relationship already exists, retrieving the binding relationship to establish a correspondence between the backup doctor and the patient; if no binding relationship exists, binding the backup doctor and the patient and recording it, thereby establishing a correspondence between the backup doctor and the patient.

[0063] If the server fails to match the incoming port in the channel doctor database, it means the patient did not send the consultation request from a specific channel. In this case, a virtual backup doctor will be used as the receiving doctor. The server determines whether a user ID and a backup doctor are already bound together based on the patient's user ID. The server can also assign a unique backup doctor ID to this virtual backup doctor and determine whether a binding relationship already exists between them by comparing the patient's user ID and the backup doctor ID.

[0064] If this is not the patient's first consultation through regular channels or general consultation methods, the server has already bound the patient's user ID to a virtual backup doctor and stored this binding relationship in the database. Therefore, the server can retrieve this binding relationship to establish the correspondence between the virtual backup doctor and the patient. At this point, the server can also retrieve the patient's previous consultation history through regular channels or general consultation methods, i.e., the patient's conversation records with the virtual backup doctor.

[0065] If a patient consults through regular channels or a standard consultation method for the first time, the server will initially link a virtual backup doctor to the patient. After establishing the correspondence between the virtual backup doctor and the patient, the server can record the conversations between the patient and the virtual backup doctor in the corresponding database.

[0066] After the server establishes the virtual doctor-patient relationship, it can configure message scripts according to the first scenario rules. In practice, if the patient and the virtual doctor are being bound for the first time, the message scripts configured according to the first scenario rules can include inquiries about the patient's basic information, a description of the patient's condition, and the purpose of the consultation. If the patient and the virtual doctor are not being bound for the first time, based on the server's retrieved history and the message scripts configured according to the first scenario rules, the message scripts can simply include inquiries about the patient's condition and the purpose of the consultation, without repeating inquiries about the patient's basic information.

[0067] In some optional implementations, after step S240 of configuring the message script according to the first scenario rule and pushing the message script to the patient, the method further includes: in response to the patient's reply based on the message script, determining the target doctor that best matches the reply; replacing the backup doctor with the target doctor as the attending physician, establishing a correspondence between the target doctor and the patient; configuring the message script according to the second scenario rule based on the target doctor, and pushing the message script to the patient.

[0068] After the server sends the message script configured according to the first scenario rules to the client, the patient responds to the message script on the client and sends the response back to the server. Based on the patient's response, the server determines the most suitable virtual target doctor from all virtual target doctors corresponding to the virtual backup doctor. In practice, the server may not be able to accurately determine the most suitable virtual target doctor through a single question-and-answer session. In such cases, the server can further refine the message script based on the patient's response and the first scenario rules to obtain more information from the patient's responses, thereby determining the most suitable target doctor.

[0069] The server replaces the virtual backup doctor with the matched virtual target doctor as the attending physician, establishing a correspondence between the virtual target doctor and the patient. The patient may not be consulting with this virtual target doctor for the first time; for example, the patient may have previously specified this virtual target doctor through the online consultation platform. Therefore, the server has already bound the patient's user identifier to the virtual target doctor and stored this binding relationship in the database. At this point, the server can retrieve the binding relationship to establish the correspondence between the virtual target doctor and the patient, and it can also retrieve the patient's previous conversation history with the virtual target doctor. If the patient is consulting with this virtual target doctor for the first time, the server performs an initial binding between the virtual target doctor and the patient. After establishing the correspondence between the virtual target doctor and the patient, the server can record the patient's conversation with the virtual target doctor in the correspondence database.

[0070] After the server establishes a virtual correspondence between a target doctor and a patient, it can configure message scripts to be pushed to the patient. These message scripts are configured through a second scenario rule. The second scenario rule is used to indicate the message orchestration rules that can perform pre-diagnosis for patient consultation requests through question-and-answer scripts. In specific implementation, if the patient and the virtual target doctor are being bound for the first time, the message scripts configured according to the second scenario rule can include inquiries about the patient's chief complaint and past medical history. If the patient and the virtual target doctor are not being bound for the first time, the message scripts based on the historical records retrieved by the server and the second scenario rule can include inquiries about the patient's chief complaint and expected outcome, without repeatedly inquiring about the patient's past medical history.

[0071] After the server sends the message script configured according to the second scenario rules to the client, the patient responds to the message script on the client and sends the response back to the server. Based on the patient's response, the server can conduct a pre-diagnosis for the patient before the patient directly contacts the corresponding physician. The server can simultaneously transmit the pre-diagnosis result to both the client and the physician. The patient can choose whether to continue direct contact with the physician based on the pre-diagnosis result, and the physician can obtain a brief understanding of the patient's condition based on the pre-diagnosis result.

[0072] In some optional implementations, after step S210 of determining whether a target doctor is specified in the consultation request, the method further includes: if a target doctor is specified, then the target doctor is designated as the attending physician, and a correspondence between the target doctor and the patient is established; the message script is configured according to the second scenario rule based on the target doctor, and the message script is pushed to the patient.

[0073] Based on the received consultation request, the server determines if a target doctor is specified in the request and then directly triages the patient to the virtual pre-consultation room of the target doctor for pre-consultation. In practice, the server can use parsing rules to split the URL format string transmitted by the client into statements, obtain the doctor identifier string, and determine the virtual target doctor based on the specific content recorded in the doctor identifier string.

[0074] The server establishes a virtual mapping between target doctors and patients. It determines whether a binding relationship already exists between the patient's user ID and the target doctor. The server can also assign a unique target doctor ID to the virtual target doctor and use this mapping to determine if a binding relationship already exists.

[0075] The patient may not be consulting with the virtual doctor for the first time. The server has already bound the patient's user ID to the virtual doctor and stored the binding relationship in the database. At this point, the server can retrieve the binding relationship to establish the correspondence between the virtual doctor and the patient, and can also retrieve the patient's previous conversation history with the virtual doctor. If the patient is consulting with the virtual doctor for the first time, the server will perform an initial binding between the virtual doctor and the patient. After establishing the correspondence between the virtual doctor and the patient, the server can record the patient's conversation with the virtual doctor in the corresponding relationship database.

[0076] After the server establishes a virtual correspondence between the target doctor and the patient, it can configure message scripts through the second scenario rules and push them to the patient. Since the patient specifies the target doctor and is directly triaged by the server to the virtual pre-diagnosis room of the virtual target doctor, the server directly arranges message scripts based on the second scenario rules to pre-diagnose the patient's consultation request.

[0077] In some optional implementations, after step S220, which determines whether a corresponding channel doctor exists based on the incoming channel of the consultation request, the method further includes: if a corresponding channel doctor exists, then the channel doctor is designated as the receiving doctor, establishing a correspondence between the channel doctor and the patient; configuring message scripts according to the incoming channel using third scenario rules, and pushing the message scripts to the patient; in response to the patient's reply based on the message scripts, determining the target doctor that best matches the reply; replacing the channel doctor with the target doctor as the receiving doctor, establishing a correspondence between the target doctor and the patient; configuring message scripts according to the target doctor using second scenario rules, and pushing the message scripts to the patient.

[0078] If the server determines that a patient sent a consultation request through a specific channel within the scenario-based online consultation window embedded in the application or other applications, then a corresponding channel doctor exists. In practice, the server uses parsing rules to split the URL format string transmitted by the client, obtaining the incoming port character segment. The server then matches the corresponding channel doctor as the attending physician based on the pre-stored channel doctor database and the specific content recorded in the incoming port character segment.

[0079] The server establishes a virtual correspondence between channel doctors and patients. The server determines whether a binding relationship already exists between a patient's user ID and a channel doctor. The server can also assign a unique channel doctor ID to the virtual channel doctor, and use this identifier to determine if a binding relationship already exists between the patient's user ID and the channel doctor ID.

[0080] The patient may not be sending a consultation request through this specific channel for the first time. The server has already bound the patient's user identifier to a virtual channel doctor and stored this binding relationship in the database. At this point, the server can retrieve the binding relationship to establish the correspondence between the virtual channel doctor and the patient, and can also retrieve previous conversation records between the patient and the virtual channel doctor. If the patient is consulting with this virtual channel doctor for the first time, the server will perform an initial binding between the virtual channel doctor and the patient. After establishing the correspondence between the virtual channel doctor and the patient, the server can record the patient's conversations with the virtual channel doctor in the corresponding relationship database.

[0081] After the server establishes the virtual correspondence between channel doctors and patients, it can configure message scripts to be pushed to patients. These message scripts are configured through third-scenario rules. Third-scenario rules are used to determine the most suitable message arrangement rules for the patient from among multiple virtual target doctors corresponding to the virtual channel doctor, based on question-and-answer scripts. In practical implementation, for example, if a patient sends a consultation request through a medication purchase channel, the server can configure message scripts that include inquiries about the patient's medication's indications and whether it is a prescription drug, based on the medication purchase channel and the third-scenario rules.

[0082] After the server sends the message script configured according to the third-scenario rules to the client, the patient responds to the message script on the client and sends the response back to the server. Based on the patient's response, the server determines the most suitable virtual target doctor from among multiple virtual target doctors corresponding to the virtual channel doctor. In practice, the server may not be able to accurately determine the most suitable virtual target doctor through a single question-and-answer session. In such cases, the server can further refine the message script based on the patient's response and the third-scenario rules to obtain more information from the patient's responses, thereby determining the most suitable target doctor.

[0083] The server replaces the virtual channel doctor with the matched virtual target doctor as the attending physician, establishing a correspondence between the virtual target doctor and the patient. The patient may not be consulting with this virtual target doctor for the first time. The server has already bound the patient's user identifier to the virtual target doctor and stored this binding relationship in the database. At this point, the server can retrieve the binding relationship to establish the correspondence between the virtual target doctor and the patient, and can also retrieve previous conversation records between the patient and the virtual target doctor. If the patient is consulting with this virtual target doctor for the first time, the server performs an initial binding between the virtual target doctor and the patient. After establishing the correspondence between the virtual target doctor and the patient, the server can record the conversations between the patient and the virtual target doctor in the correspondence database.

[0084] After the server establishes a virtual correspondence between the target doctor and the patient, it can configure the message script through the second scenario rules and push it to the patient to conduct a pre-diagnosis of the patient's consultation request.

[0085] Figure 3 This application illustrates a triage method for an online pre-diagnosis room according to another embodiment of the present application. According to... Figure 3 As shown, the method may include the following steps:

[0086] Step S301: Receive the patient's consultation request, split the consultation request into sentences according to the parsing rules to obtain the user identifier character field, doctor identifier character field, and input channel character field, determine the patient's user identifier based on the user identifier character field, and proceed to step S302.

[0087] Step S302: Determine whether the doctor identifier character field includes a doctor identifier. If it does not include a doctor identifier, proceed to step S303. If it does include a doctor identifier, proceed to step S309.

[0088] Step S303: Determine the patient's input port based on the input channel character field, then proceed to step S304.

[0089] Step S304: Match the corresponding channel doctor from the channel doctor database according to the incoming port. If the match is unsuccessful, proceed to step S305. If the match is successful, proceed to step S310.

[0090] Step S305: Using the backup doctor as the receiving doctor, determine whether there is already a binding relationship between the user ID and the backup doctor based on the patient's user ID. If there is already a binding relationship, retrieve the binding relationship to establish the correspondence between the backup doctor and the patient. If there is no binding relationship, bind the backup doctor and the patient and record it, thereby establishing the correspondence between the backup doctor and the patient, and proceed to step S306.

[0091] Step S306: Configure the message script according to the first scenario rule and push the message script to the patient. In response to the patient's reply based on the message script, determine the target doctor that best matches the reply and replace the fallback doctor as the attending physician. Proceed to step S307.

[0092] Step S307: Determine whether a binding relationship already exists between the user identifier and the target doctor based on the patient's user identifier. If a binding relationship already exists, retrieve the binding relationship to establish the correspondence between the target doctor and the patient. If no binding relationship exists, bind the target doctor and the patient and record it, thereby establishing the correspondence between the target doctor and the patient, and proceed to step S308.

[0093] Step S308: Configure the message script according to the second scenario rules based on the target doctor, and push the message script to the patient.

[0094] Step S309: Select the target doctor as the attending physician and proceed to step S307.

[0095] Step S310: Using the channel doctor as the receiving doctor, determine whether the user identifier and the channel doctor have a binding relationship based on the patient's user identifier. If a binding relationship already exists, retrieve the binding relationship to establish the correspondence between the channel doctor and the patient. If no binding relationship exists, bind the channel doctor and the patient and record it, thereby establishing the correspondence between the channel doctor and the patient, and proceed to step S311.

[0096] Step S311: Configure the message script according to the third scenario rules and push the message script to the patient. In response to the patient's reply based on the message script, determine the target doctor that best matches the reply and replace the channel doctor as the attending physician. Step S307.

[0097] Figure 4 A schematic diagram of the triage device in an online consultation pre-diagnosis room according to an embodiment of this application is shown. Figure 4 As shown, the device 400 includes:

[0098] The target doctor determination unit 401 is used to receive the patient's consultation request and determine whether the consultation request specifies a target doctor.

[0099] The channel doctor judgment unit 402 is used to determine whether there is a corresponding channel doctor based on the incoming channel of the consultation request when no target doctor is specified.

[0100] Unit 403, which identifies the backup doctor, is used to establish a correspondence between the backup doctor and the patient when there is no corresponding channel doctor.

[0101] The first triage unit 404 is used to configure message scripts according to the first scenario rules and push the message scripts to the patient.

[0102] In some optional embodiments, in the above-described device 400, the target doctor determination unit 401 is specifically used to: receive a patient's consultation request; split the consultation request into sentences according to the parsing rules to obtain a user identifier character segment, a doctor identifier character segment, and an input channel character segment; determine the patient's user identifier based on the user identifier character segment; and determine whether the doctor identifier character segment includes a doctor identifier.

[0103] In some optional embodiments, in the above-described device 400, the channel doctor determination unit 402 is specifically used to: determine the patient's input port based on the input channel character field when the doctor identifier character field is empty; and match the corresponding channel doctor from the channel doctor database based on the input port, wherein the channel doctor database includes the correspondence between input ports and channel doctors.

[0104] In some optional embodiments, in the above-described device 400, the backup doctor determination unit 403 is specifically used to: when matching fails, use the backup doctor as the attending physician; determine whether the user identifier and the backup doctor already have a binding relationship based on the patient's user identifier; if a binding relationship already exists, retrieve the binding relationship to establish the correspondence between the backup doctor and the patient; if no binding relationship exists, bind the backup doctor and the patient and record it, thereby establishing the correspondence between the backup doctor and the patient.

[0105] In some optional embodiments, the device 400 further includes: a backup doctor switching unit, used to determine the target doctor that best matches the patient's response based on the message script; to replace the backup doctor with the target doctor as the attending physician, and to establish a correspondence between the target doctor and the patient; to configure the message script according to the second scenario rules based on the target doctor, and to push the message script to the patient.

[0106] In some optional embodiments, the above-mentioned device 400 further includes: a target doctor determination unit, used to designate the target doctor as the attending physician when a target doctor is specified, establish a correspondence between the target doctor and the patient; configure message scripts according to the target doctor using the second scenario rules, and push the message scripts to the patient.

[0107] In some optional embodiments, the device 400 further includes: a channel doctor switching unit, used to, when a corresponding channel doctor exists, use the channel doctor as the attending physician and establish a correspondence between the channel doctor and the patient; configure message scripts according to the incoming channel using third scenario rules and push the message scripts to the patient; in response to the patient's reply based on the message scripts, determine the target doctor that best matches the reply; replace the channel doctor with the target doctor as the attending physician and establish a correspondence between the target doctor and the patient; configure message scripts according to the target doctor using second scenario rules and push the message scripts to the patient.

[0108] It should be noted that the triage device 400 in the online consultation pre-diagnosis room can implement the aforementioned triage method in the online consultation pre-diagnosis room, which will not be elaborated further.

[0109] Figure 5 This application shows a schematic diagram of the structure of a computer device according to one embodiment of the present application. Figure 5 As shown, the internal structure of this computer device may include a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it implements the functions or steps of the online consultation pre-diagnosis room triage method server-side.

[0110] In one embodiment, the computer device provided in this application includes a memory and a processor. The memory stores a database and a computer program that can run on the processor. When the processor executes the computer program, it performs the following steps:

[0111] Receive patient consultation requests and determine whether a target doctor is specified in the consultation request;

[0112] If no target doctor is specified, the existence of a corresponding doctor will be determined based on the channel through which the consultation request was received.

[0113] If there is no corresponding channel doctor, then the backup doctor will be used as the receiving doctor, and a correspondence between the backup doctor and the patient will be established.

[0114] Configure the message script according to the first scenario rules, and push the message script to the patient.

[0115] In one embodiment, a computer device is also provided, which may be a client, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps of the online consultation pre-diagnosis room triage method on the client side.

[0116] In one embodiment, a computer-readable storage medium is also provided, on which a computer program is stored, the computer program performing the following steps when executed by a processor:

[0117] Receive patient consultation requests and determine whether a target doctor is specified in the consultation request;

[0118] If no target doctor is specified, the existence of a corresponding doctor will be determined based on the channel through which the consultation request was received.

[0119] If there is no corresponding channel doctor, then the backup doctor will be used as the receiving doctor, and a correspondence between the backup doctor and the patient will be established.

[0120] Configure the message script according to the first scenario rules, and push the message script to the patient.

[0121] It should be noted that the functions or steps that can be implemented by the computer device or computer-readable storage medium described above can be referred to the relevant descriptions on the server side and client side in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0122] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0123] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0124] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A triage method for an online pre-diagnosis consultation room, characterized in that, The method includes: Receive a patient's consultation request and determine whether the consultation request specifies a target doctor; If no target doctor is specified, the existence of a corresponding channel doctor will be determined based on the channel through which the consultation request was received. If there is no corresponding channel doctor, then the backup doctor will be used as the receiving doctor, and a correspondence between the backup doctor and the patient will be established. Configure the message script according to the first scenario rules, and push the message script to the patient; Among them, one virtual channel doctor corresponds to multiple virtual target doctors, and multiple virtual target doctors correspond to virtual pre-diagnosis rooms; the channel doctor is equivalent to a front-end virtual doctor configured for multiple virtual target doctors. The channel doctor is used to determine the virtual target doctor suitable for the patient through message scripts, and then the target doctor takes over from the channel doctor to conduct a pre-diagnosis for the patient; one virtual backup doctor corresponds to all virtual target doctors, and all virtual target doctors correspond to virtual pre-diagnosis rooms; the backup doctor is equivalent to a general virtual doctor configured for all virtual target doctors. The backup doctor is used to determine the virtual target doctor suitable for the patient through general message scripts, and then the target doctor takes over from the backup doctor to conduct a pre-diagnosis for the patient.

2. The triage method for the online consultation and pre-diagnosis room according to claim 1, characterized in that, The process of receiving a patient's consultation request and determining whether the consultation request specifies a target doctor includes: Receive patient consultation requests; The consultation request is split into three segments according to the parsing rules: user identifier segment, doctor identifier segment, and input channel segment. The patient's user identifier is determined based on the user identifier character field; Determine whether the doctor identifier character field includes a doctor identifier.

3. The triage method for the online consultation and pre-diagnosis room according to claim 2, characterized in that, If no target doctor is specified, the method of determining whether a corresponding doctor exists based on the channel through which the consultation request was received includes: If the doctor identifier field is empty, the patient's input port is determined based on the input channel field. Based on the input port, a corresponding channel doctor is matched from the channel doctor database, wherein the channel doctor database includes the correspondence between the input port and the channel doctor.

4. The triage method for the online consultation and pre-diagnosis room according to claim 3, characterized in that, If no corresponding channel doctor exists, then a backup doctor will be used as the receiving doctor, and a correspondence between the backup doctor and the patient will be established, including: If a match fails, the backup doctor will be used as the attending physician. Determine whether a binding relationship already exists between the user identifier and the designated doctor based on the patient's user identifier; If a binding relationship already exists, the binding relationship is retrieved to establish the correspondence between the backup doctor and the patient; If no binding relationship exists, the backup doctor and the patient are bound together and recorded, thereby establishing the correspondence between the backup doctor and the patient.

5. The triage method for the online consultation and pre-diagnosis room according to claim 1, characterized in that, After the step of configuring the message script according to the first scenario rule and pushing the message script to the patient, the method further includes: In response to the patient's reply based on the message script, identify the target doctor that best matches the reply; Replace the fallback doctor with the target doctor as the attending physician, and establish a correspondence between the target doctor and the patient; The target doctor configures the message script according to the second scenario rules and pushes the message script to the patient.

6. The triage method for the online consultation and pre-diagnosis room according to claim 1, characterized in that, After the step of determining whether a target doctor is specified in the consultation request, the method further includes: If a target doctor is specified, then the target doctor will be designated as the attending physician, and a correspondence between the target doctor and the patient will be established. The target doctor configures the message script according to the second scenario rules and pushes the message script to the patient.

7. The triage method for the online consultation and pre-diagnosis room according to claim 1, characterized in that, After the step of determining whether a corresponding doctor exists based on the input channel of the consultation request, the method further includes: If a corresponding channel doctor exists, then the channel doctor will be used as the receiving doctor, and a correspondence between the channel doctor and the patient will be established. Configure the message script according to the third scenario rules based on the input channel, and push the message script to the patient; In response to the patient's reply based on the message script, identify the target doctor that best matches the reply; Replace the channel doctor with the target doctor as the receiving doctor, and establish a correspondence between the target doctor and the patient; The target doctor configures the message script according to the second scenario rules and pushes the message script to the patient.

8. A triage device for an online consultation and pre-diagnosis room, characterized in that, The device includes: The target doctor determination unit is used to receive a patient's consultation request and determine whether a target doctor is specified in the consultation request. The channel doctor determination unit is used to determine whether a corresponding channel doctor exists based on the incoming channel of the consultation request when no target doctor is specified. The backup doctor identification unit is used to establish a correspondence between the backup doctor and the patient when there is no corresponding channel doctor. The first triage unit is used to configure message scripts according to the first scenario rules and push the message scripts to the patient; Among them, one virtual channel doctor corresponds to multiple virtual target doctors, and multiple virtual target doctors correspond to virtual pre-diagnosis rooms; the channel doctor is equivalent to a front-end virtual doctor configured for multiple virtual target doctors. The channel doctor is used to determine the virtual target doctor suitable for the patient through message scripts, and then the target doctor takes over from the channel doctor to conduct a pre-diagnosis for the patient; one virtual backup doctor corresponds to all virtual target doctors, and all virtual target doctors correspond to virtual pre-diagnosis rooms; the backup doctor is equivalent to a general virtual doctor configured for all virtual target doctors. The backup doctor is used to determine the virtual target doctor suitable for the patient through general message scripts, and then the target doctor takes over from the backup doctor to conduct a pre-diagnosis for the patient.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the triage method for the online consultation and pre-diagnosis room as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is instructed by the processor, it implements the steps of the triage method for the online consultation and pre-diagnosis room as described in any one of claims 1 to 7.

Images