Risk identification method and device for internet medical treatment platform and electronic equipment
By building a risk strategy database and identification model on the internet-based medical platform and monitoring medical information in real time, the problem of the inability of existing technologies to fully identify risks in internet-based medical services has been solved, thus improving the safety and reliability of medical services.
Patent Information
- Application Number
- CN202211096177.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-08
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-09-08
AI Technical Summary
Existing internet-based medical platforms lack effective risk identification capabilities and are unable to comprehensively monitor various risks during the medical process, particularly prescription risks, doctor qualifications, and potential problems during consultations.
By building a risk strategy library and risk identification model on the internet-based medical platform, the system can monitor medical information in real time using preset risk strategies and identification models, identify and output risk identification results, including risk type, classification, level and treatment recommendations.
It enables risk identification at each stage of the online medical consultation process, improves the safety and reliability of medical services, promptly identifies and addresses potential risks, and safeguards patients' lives.
Smart Images

Figure CN115689834B_ABST
Abstract
Description
Technical Field
[0001] The embodiments described in this specification relate to the field of internet-based medical diagnosis and treatment technology, specifically to a risk identification method, apparatus, and electronic device for internet-based medical diagnosis and treatment platforms. Background Technology
[0002] Internet-based medical services, utilizing the internet as a platform, can effectively integrate medical resources and improve patients' healthcare experience. Currently, internet-based medical services have played a positive role in meeting patients' medical needs, alleviating pressure on medical resources, and reducing gatherings of people, becoming an important component of the healthcare service system.
[0003] To ensure patient safety, strict regulation is needed to address the various risks that may arise during online medical consultations. However, current online medical services lack comprehensive risk identification capabilities and cannot effectively regulate most stages of the consultation process. Summary of the Invention
[0004] This specification provides a method, apparatus, electronic device, and computer-readable storage medium for risk identification in internet-based medical consultation platforms, aiming to solve the technical problem that current related technologies cannot effectively identify various risks in the process of internet-based medical consultation.
[0005] One embodiment of this specification provides a risk identification method for an internet-based medical platform, comprising: selecting at least one target risk strategy from a risk strategy library; determining a risk identification model corresponding to each target risk strategy among a plurality of preset risk identification models; inputting the acquired medical information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current medical service process, wherein the risk identification model is used to execute the corresponding target risk strategy to identify the medical information.
[0006] In one embodiment of this specification, at least one target risk strategy includes a basic risk strategy, and the current diagnosis and treatment service process includes at least one diagnosis and treatment stage. Selecting at least one target risk strategy from a risk strategy library includes: determining at least one risk strategy corresponding to the current diagnosis and treatment stage as a basic risk strategy in the risk strategy library.
[0007] In one embodiment of this specification, at least one target risk strategy further includes a supplementary risk strategy, wherein selecting at least one target risk strategy from a risk strategy library further includes: obtaining risk identification results from a prior diagnosis and treatment phase as reference risk information; and determining at least one risk strategy corresponding to the reference risk information as a supplementary risk strategy in the risk strategy library.
[0008] In one embodiment of this specification, at least one target risk strategy further includes a key risk strategy, wherein selecting at least one target risk strategy from the risk strategy library further includes: determining whether the diagnosis and treatment information includes preset key identification information; when the diagnosis and treatment information includes key identification information, determining at least one risk strategy corresponding to the key identification information in the risk strategy library as a key risk strategy.
[0009] In one embodiment of this specification, the preset key identification information includes specific disease information and / or specific drug information.
[0010] In one embodiment of this specification, determining the risk identification model corresponding to each target risk strategy from a set of preset risk identification models includes: determining the risk type of each target risk strategy, wherein the risk type includes one of medical qualification risk, consultation process risk, diagnosis result risk, and prescription risk; and determining the risk identification model corresponding to each target risk strategy from the set of preset risk identification models based on the risk type.
[0011] In one embodiment of this specification, the risk identification method further includes: determining whether there is any new medical information; if so, obtaining the new medical information; and inputting the new medical information into the risk identification model corresponding to each target risk strategy to obtain the updated risk identification result.
[0012] In one embodiment of this specification, each target risk strategy corresponds to a risk identification rule. Before inputting the acquired diagnosis and treatment information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current diagnosis and treatment service process, the above-mentioned risk identification method further includes: inputting the risk identification rule corresponding to each target risk strategy into the risk identification model corresponding to each target risk strategy.
[0013] One embodiment of this specification provides a risk identification device for an internet-based medical platform, comprising: a strategy selection module for selecting at least one target risk strategy from a risk strategy library; a model determination module for determining a risk identification model corresponding to each target risk strategy from a plurality of preset risk identification models; and an acquisition module for inputting acquired medical information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current medical service process, wherein the risk identification model is used to execute the corresponding target risk strategy to identify the medical information.
[0014] One embodiment of this specification provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the risk identification method provided in any embodiment of this specification.
[0015] One embodiment of this specification provides a computer-readable storage medium having computer instructions stored thereon, which, when executed on a computer, cause the computer to perform the risk identification method provided in any embodiment of this specification.
[0016] One embodiment of this specification provides a computer program product that, when run on a computer, causes the computer to perform the risk identification method provided in any embodiment of this specification.
[0017] The various implementation methods provided in this specification utilize risk strategies and risk identification models pre-designed to address various risks that may occur during the internet-based medical service process. During the actual execution of the medical service process, the required target risk strategies and corresponding risk identification models can be determined. In turn, the actual medical information generated can be identified through the risk identification model to obtain risk identification results that reflect the security of the current medical service process. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of this specification, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] Figure 1 This is a schematic diagram illustrating an exemplary medical service performed on an internet-based medical platform, as one embodiment of this specification.
[0020] Figure 2 This is a schematic diagram of an exemplary internet-based medical system provided for one embodiment of this specification.
[0021] Figure 3 This is a flowchart illustrating a risk identification method provided in one embodiment of this specification.
[0022] Figure 4 This is a flowchart illustrating a risk identification method provided in one embodiment of this specification.
[0023] Figure 5 This specification provides a risk identification device for an internet-based medical platform, as one embodiment of the invention.
[0024] Figure 6 This is a block diagram of an electronic device provided for one embodiment of this specification. Detailed Implementation
[0025] The technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.
[0026] Overview
[0027] While the technology behind internet-based medical services is developing rapidly, regulatory measures for various risks that may arise during the process are still inadequate.
[0028] Currently, among related technologies, regulatory measures with risk identification capabilities typically only include rational drug use systems. Rational drug use systems extend offline prescription review methods to online medical platforms, reviewing prescriptions issued online by medical personnel to determine if there are potential medication risks (e.g., incorrect dosage, negative interactions between multiple drugs, duplicate medication, etc.).
[0029] However, in actual online medical consultations, prescription issuance is only one stage, and even that stage only occurs in a small number of services. In other words, for most stages of the medical service, the rational drug use system is completely ineffective in risk identification.
[0030] Furthermore, the risks identified by the rational drug use system are limited to the prescription itself, failing to consider the impact of other stages on prescription risk. Specifically, the current rational drug use system typically cannot identify situations where doctors prescribe across departments (e.g., an internist prescribing a psychiatric prescription) or prescribe beyond their authority (e.g., a non-senior-level doctor prescribing antibiotics containing special-use drugs). Moreover, the current rational drug use system lacks rigor in follow-up assessments and cannot determine the preconditions for online follow-up prescriptions (e.g., the authenticity and validity of follow-up certificates, the patient's condition control, etc.). In addition, the current rational drug use system only reviews the prescription itself, not the diagnoses, meaning it assumes the doctor's diagnosis is correct and therefore cannot determine the appropriateness of the medications in the prescription, let alone identify any problems during the consultation process.
[0031] Therefore, it is necessary to provide a risk identification method for internet-based medical platforms. This method pre-sets risk strategies and risk identification models for the numerous potential risks present in the internet-based medical process, so that the risk identification results can be determined based on the medical information during the actual medical service process. This solves the technical problem that related technologies cannot effectively identify the various risks present in the internet-based medical process.
[0032] Scenario Example
[0033] This specification provides an example application scenario for a risk identification method used in internet-based medical platforms.
[0034] Figure 1 This is a schematic diagram illustrating an exemplary medical service process performed on an internet-based medical platform, as one embodiment of this specification. Figure 1 As shown, the medical service process can include at least the following stages: medical staff registration, patient appointment booking, online consultation, doctor's diagnosis, and doctor's prescription. It should be understood that these stages are optional, and in some cases, only some of them may actually occur. For example, if the doctor determines that the patient does not need medication, the prescription stage will not occur; or, for another example, if the patient cancels their appointment, the online consultation stage and all subsequent stages will not occur.
[0035] Various risks can occur at any stage of the medical service process. For example, during the registration stage for medical personnel, there is a risk that the registrant may use someone else's medical qualification certificate to register under a false name, or use a forged medical qualification certificate to register; another example is that during the stage when doctors issue diagnosis results, there is a risk that the wrong disease name may be written due to the doctor's judgment error or operational error.
[0036] In response to these potential risks in the diagnosis and treatment service process, the risk identification method provided in the embodiments of this specification can be used to monitor the diagnosis and treatment information generated at each stage of the process, comprehensively assess the authenticity, accuracy, and security of this information, and obtain risk identification results in a timely manner, thereby improving the ability of the internet diagnosis and treatment platform to protect the life safety of patients.
[0037] In this application scenario, the risk identification method provided in this specification can be continuously executed during the diagnosis and treatment service process, thereby enabling monitoring of any one or more stages of the currently ongoing diagnosis and treatment service process. By acquiring the diagnosis and treatment information generated in the diagnosis and treatment service process in real time and inputting the diagnosis and treatment information into a pre-built risk identification model, the risk identification result corresponding to the current diagnosis and treatment service process is obtained from the output of the risk identification model.
[0038] For example, medical information may include medical staff information (such as doctor's number), patient information (such as patient number, follow-up visit certificate, symptoms treated), consultation interaction data (such as text and image interaction messages, voice recordings, video recordings, etc.), diagnosis result data (such as disease name, severity of condition, and recommendations for offline consultation or online prescription), and prescription medication data (such as drug type, usage, dosage, etc.).
[0039] Here, multiple risk identification models, each corresponding to a different risk type, can be used for risk identification. These multiple risk identification models may include, for example, a medical qualification identification model, a consultation process identification model, a medical conclusion identification model, and a prescription identification model. Before risk identification, each risk identification model can retrieve at least one target risk strategy for verifying medical information from a pre-built database, along with the risk identification rules corresponding to each target risk strategy. During the risk identification process, the risk identification model verifies the objects contained in the medical information according to the risk identification rules corresponding to each target risk strategy, thereby determining whether the corresponding type of risk exists in the current medical service process.
[0040] The risk identification model invokes at least one target risk strategy, which is selected based on the fulfillment of various preconditions. This may include a basic risk strategy selected based on the current stage of diagnosis and treatment, a supplementary risk strategy selected based on risks identified in previous stages of diagnosis and treatment, and / or a key risk strategy selected based on key identification information appearing in the diagnosis and treatment information. These risk strategies can be pre-stored in a risk strategy library and selected during the execution of the risk identification method based on the fulfillment of the aforementioned preconditions, serving as the target risk strategy executed by the risk identification model.
[0041] Based on the risk identification rules corresponding to each target risk strategy, the risk identification model can output risk identification results. These results may include risk type (e.g., prescription risk) and / or risk classification (e.g., duplicate medication), as well as any one or more of the following risk-related information: corresponding risk level (e.g., level 3), risk description (expressing the specific circumstances of the risk), and treatment recommendations (expressing how to eliminate the corresponding risk).
[0042] Optionally, after obtaining the risk identification result, it can be confirmed again whether new medical information has been generated. Exemplarily, the risk identification method provided in the embodiments of this specification can be executed in real-time loops. For example, it can be started at the beginning of each new medical stage, or whenever new medical information is obtained. Through such execution logic, the currently occurring risks can be output in a timely manner, improving the real-time performance of risk identification and further enhancing the reliability of the internet-based medical platform.
[0043] Optionally, after each risk identification model outputs its risk identification results, these results can be aggregated and stored or displayed to each client. For example, based on the risk identification results, the internet-based medical platform can choose whether to perform further operations, such as sending risk warning information to the client.
[0044] It should be understood that the above content is only one possible application of the risk identification method provided in this specification. The descriptions of details such as the specific stages of the Internet medical platform, the classification of risk types, and the content of medical information are all exemplary. Those skilled in the art can make changes according to actual needs, and all such modified solutions should fall within the scope of protection of this specification.
[0045] System Architecture
[0046] Figure 2 This specification provides an exemplary internet-based medical consultation system as one embodiment of the invention. (For example...) Figure 2 As shown, the internet-based medical system may include a server 210, at least one client 220, and a database 230. The server 210 may be used to execute the risk identification method provided in the embodiments of this specification. The at least one client 220 may be used to participate in one or more stages of the internet-based medical service. The database 230 may be used to provide the server 210 with various data required to execute the risk identification method provided in the various embodiments of this specification.
[0047] Here, at least one client 220 may include multiple clients, which may be, for example, platform client 220a (e.g., a user terminal used by maintenance personnel of an internet medical platform), medical personnel client 220b (e.g., a user terminal used by a doctor or pharmacist), and patient client 220c (e.g., a user terminal used by a patient). Server 210 can obtain various medical information in the medical service process sent by each client 220, and can also send risk identification results to each client 220.
[0048] Specifically, server 210 can be an electronic device with certain computing capabilities, including a network communication module, processor, and memory. Of course, server 210 can also refer to software running on the aforementioned electronic device. Server 210 can also be a distributed server, a system with multiple processors, memory, network communication modules, etc., operating collaboratively. Alternatively, server 210 can be a server cluster formed by several servers. Furthermore, with the development of science and technology, server 210 can also be a new technical means capable of realizing the corresponding functions provided in the embodiments of the specification. For example, it could be a new form of "server" based on quantum computing.
[0049] Client 220 can be an electronic device with network access capabilities. For example, client 220 can be a desktop computer, tablet, laptop, smartphone, digital assistant, smart wearable device, shopping guide terminal, television, smart speaker, microphone, etc. Smart wearable devices include, but are not limited to, smart bracelets, smartwatches, smart glasses, smart helmets, smart necklaces, etc. Alternatively, client 220 can also be software capable of running on the aforementioned electronic devices. It should be understood that platform client 220a, medical staff client 220b, and patient client 220c can be different types of electronic devices or the same type of electronic devices; no limitation is made here.
[0050] Example method
[0051] Figure 3 This is a flowchart illustrating a risk identification method for an internet-based medical platform, provided as one embodiment of this specification. This risk identification method can be executed by a server, for example, by... Figure 2 The risk identification method is executed by server 210 in the system shown. The risk identification method may include the following steps:
[0052] Step S301: Select at least one target risk strategy from the risk strategy library.
[0053] To address various risks that may arise during the medical service process conducted on internet-based medical platforms, multiple risk strategies can be pre-designed and stored in a risk strategy library. For example, risk strategies can be designed based on relevant medical service policies and regulations, basic rules of medical safety, fundamental knowledge of diagnosis and medication, and various national and local policies and regulations specifying internet-based medical services. In some implementations, risk strategies can also be designed according to other specific needs; this specification does not limit this approach.
[0054] Specifically, each risk strategy may include a verification subject, a verification object, and verification elements. The verification subject specifies the subject (e.g., a doctor) corresponding to the current risk strategy; the verification object specifies the object corresponding to the verification subject of the current risk strategy (e.g., a doctor's professional qualification certificate); and the verification elements specify the specific elements of the verification object of the current risk strategy (e.g., the authenticity of the professional qualification certificate).
[0055] In some optional implementations, each risk strategy may further include a strategy number to uniquely identify the current risk strategy, and a strategy title to describe the current risk strategy.
[0056] In some optional implementations, each risk strategy may further include an effective region. The effective region is used to specify in which regions the current risk identification rules are in effect, thereby enabling the risk identification methods provided in this specification to be applied to different regions and flexibly address risks that may arise in the medical service process under various special circumstances.
[0057] In some alternative implementations, each risk strategy may further include a validation frequency, which specifies how often the current risk strategy can be executed during the entire medical service process, for example, it may be divided into single or repeated executions.
[0058] In some implementations, at least one target risk strategy includes a basic risk strategy, and the current medical service process includes at least one medical stage. Step S301 includes: determining, from a risk strategy library, at least one risk strategy corresponding to the current medical stage as the basic risk strategy.
[0059] The medical service process occurring on an internet-based medical platform may include at least one stage, some of which may have fixed execution items, thus generating fixed types of medical information and risks. For example, during the medical personnel registration stage, medical information related to the doctor's qualifications and identity is generated, potentially leading to risks related to medical qualifications. Similarly, during the doctor's prescription stage, medical information related to medications is generated, potentially leading to risks related to prescriptions.
[0060] Based on these inherent characteristics, corresponding risk strategies can be designed for each stage of diagnosis and treatment. These risk strategies can then be selected as the basic risk strategies for each stage during the risk identification process. This improves the efficiency and accuracy of risk strategy selection, enabling timely identification of high-probability risks at each stage of diagnosis and treatment.
[0061] In some implementations, at least one target risk strategy further includes a supplementary risk strategy, wherein at least one target risk strategy is selected from a risk strategy library. Step S301 further includes: obtaining risk identification results from previous treatment phases as reference risk information; and determining at least one risk strategy corresponding to the reference risk information as a supplementary risk strategy in the risk strategy library.
[0062] For example, if the risk of a doctor misusing another person's qualification certificate is identified during the medical personnel registration stage, this risk can be used as reference risk information. In subsequent treatment stages, a risk strategy related to this reference risk information can be selected as a supplementary risk strategy to identify other risks that this risk may cause. In this way, setting the selection logic of risk strategies based on the implicit correlation between multiple risks can effectively improve the accuracy of risk identification at each stage of treatment and effectively improve the risk identification efficiency of the overall medical service process.
[0063] In some implementations, at least one target risk strategy further includes a key risk strategy, wherein at least one target risk strategy is selected from a risk strategy library. Step S301 further includes: determining whether the medical information includes preset key identification information; when the medical information includes key identification information, determining at least one risk strategy corresponding to the key identification information in the risk strategy library as a key risk strategy.
[0064] Specifically, the preset key identification information may include specific disease information and / or specific drug information. It is understood that, according to relevant regulations, some diseases can only be diagnosed by doctors with relevant qualifications, such as mental illnesses. To monitor the risk of doctors diagnosing beyond their authority, these diseases can be pre-defined as specific diseases, and information related to these specific diseases (such as disease names, symptom descriptions, etc.) can be set as key identification information, with corresponding risk strategies implemented. For example, at the stage where doctors issue diagnostic results, if specific disease information is found in the medical records, the risk strategy corresponding to the risk of medical qualification risk can be selected as the key risk strategy to identify the risk of doctors diagnosing beyond their authority in subsequent steps.
[0065] Similarly, some medications can only be prescribed by qualified physicians, such as those requiring further observation of their activity or side effects; medications that can cause dependence; and medications with high toxicity. To monitor the risk of physicians prescribing medications without authorization, these medications can be pre-identified as specific drugs, and information related to these specific drugs (such as drug name, ingredient names, etc.) can be set as key identification information, with corresponding risk strategies implemented. For example, if specific drug information is found in the medical records during the prescription stage, the risk strategy corresponding to the risk of physician qualification can be selected as the key risk strategy to identify the risk of physicians making unauthorized diagnoses in subsequent steps.
[0066] In some specific implementations, a target risk strategy can be selected by determining whether the preconditions for each risk strategy are met. Here, each risk strategy in the risk strategy library can further include preconditions and a strategy status. Preconditions are used to determine whether the current risk strategy should be selected. Preconditions can include at least one condition; when all conditions are met or a preset number of conditions are met, the current risk strategy will be selected as the target risk strategy. Each condition can consist of two parts: first, the strategy number specifying the risk strategy; and second, the execution status of the risk strategy (e.g., executed, or the execution result being a hit or miss). The strategy status is used to indicate whether the current risk strategy has been selected as the target risk strategy. In this way, the logical relationships between various risk strategies can be pre-defined, and other target risk strategies can be selected based on the execution results of the already executed target risk strategies, thereby improving the efficiency and accuracy of risk identification based on the implicit correlations between various risks.
[0067] Step S302: Among the preset multiple risk identification models, determine the risk identification model corresponding to each target risk strategy.
[0068] Specifically, based on the characteristics of the diagnostic and treatment information involved in each risk, multiple risk identification models can be pre-constructed to identify different risk types, diagnostic and treatment information at different stages of treatment, or diagnostic and treatment information with different structures. Of course, in some implementations, risk identification models can also be designed according to other classification methods or usage requirements. These risk identification models can be decision tree models, neural network models, etc., and this specification does not specifically limit them.
[0069] In some optional implementations, each risk strategy may further include a risk type. The risk type specifies the type of risk corresponding to the current risk strategy. For example, the risk type may include one of the following: medical qualification risk, consultation process risk, diagnostic outcome risk, and prescription risk. Accordingly, the multiple risk identification models may include a medical qualification identification model, a consultation process identification model, a diagnostic structure identification model, and a prescription identification model. Here, step S302 may include: determining the risk type of each target risk strategy; and, based on the risk type, determining the risk identification model corresponding to each target risk strategy from a set of preset risk identification models.
[0070] In some optional implementations, each risk strategy may further include a correspondence with a risk identification model. This correspondence directly determines which risk identification model can execute each risk strategy. In other words, in these implementations, the risk identification model corresponding to each target risk strategy can be directly determined.
[0071] Step S303: Input the acquired diagnosis and treatment information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current diagnosis and treatment service process.
[0072] The risk identification model is used to execute corresponding target risk strategies to identify medical information. During the current medical service process, relevant medical information can be obtained, which may contain potential risks. Based on this information, by executing pre-set risk strategies targeting these risks, the actual risks can be effectively identified.
[0073] Different stages of diagnosis and treatment may generate various types of information. For example, during the registration stage for medical personnel, doctors can submit information such as their medical qualification certificate, affiliated hospital and department, professional level and authority, and personal identification information; during the patient appointment registration stage, patients can submit information such as their medical record number, follow-up visit certificate, symptoms, and personal identification information; during the online consultation stage, the communication between doctors and patients may generate information such as text and image interaction messages, voice recordings, and video recordings; during the stage when doctors issue diagnostic results, the diagnostic results may include the confirmed disease and treatment suggestions; and during the stage when doctors prescribe medications, the prescription may include information such as the type of medication, usage, and dosage.
[0074] It is understandable that the aforementioned medical information may be subject to risks in terms of authenticity, accuracy, and security, which may affect the overall medical service process.
[0075] For example, during the registration phase for medical personnel, the risks involved may include those related to the qualifications of online hospitals, doctors, pharmacists, prescription authority, and the real-name authentication of medical personnel. Examples include internists prescribing psychiatric prescriptions outside their department, or non-senior-level doctors prescribing prescriptions containing special-use antibiotics beyond their authorized level. During the patient appointment registration phase, the risks may include those related to follow-up visit vouchers, the patient's symptoms, and the patient's real-name authentication. For example, follow-up evaluations involve verifying the authenticity and validity of follow-up visit vouchers. During the online consultation phase, the risks may include whether the consultation actually took place, whether the language used during the consultation was illegal or irregular, and whether the consultation process was rigorous and effective. For example, whether the doctor inquired about the patient's condition. During the doctor's diagnosis phase, the risks may include whether the doctor's proposed treatment (e.g., recommending in-person consultation or online prescription) complies with laws and regulations, and whether the diagnosis is rigorous and reasonable. During the doctor's prescription phase, the risks may include whether the drug selection, usage, and dosage in the prescription are reasonable.
[0076] It is understandable that risks arising in the medical service process are often reflected in the medical information. Therefore, by inputting the medical information into a risk identification model, which then executes pre-designed risk strategies targeting potential risks, risks present in the medical information can be effectively identified.
[0077] For example, after obtaining the risk identification model corresponding to each target risk strategy, the diagnosis and treatment information can be input into each risk identification model, so that each risk identification model can execute its corresponding target risk strategy for the complete diagnosis and treatment information, and obtain the risk identification result corresponding to each target risk strategy, thereby improving the accuracy of the risk identification result.
[0078] For example, assuming three target risk strategies are selected in S301, where two of the target risk strategies have a risk type of medical qualification risk and one target risk strategy has a risk type of prescription risk, then the risk identification model corresponding to each target risk strategy obtained in S302 can include a medical qualification identification model and a prescription identification model. Furthermore, in S303, medical information can be input into the medical qualification identification model and the prescription identification model respectively. Based on this, the medical qualification identification model can execute the two target risk strategies with a risk type of medical qualification risk according to the medical information, thereby obtaining the execution results of each of the two target risk strategies; similarly, the prescription identification model can execute the one target risk strategy with a risk type of prescription risk according to the same medical information, thereby obtaining the execution result of that target risk strategy.
[0079] After confirming that all target risk strategies have been executed, the risk identification model can summarize the execution results of each target risk strategy to form a risk identification result and output it. Alternatively, the risk identification model can output the execution result of a target risk strategy as a risk identification result immediately after execution, and update the previous risk identification result based on the new execution result after executing the next target risk strategy, until all target risk strategies have been executed.
[0080] When multiple risk identification models are run separately, each risk identification model can output its own risk identification result. Alternatively, the risk identification method can further include summarizing, weighting, or averaging the risk identification results of multiple risk identification models to obtain the final risk identification result.
[0081] In some implementations, the risk identification result can include risk type; that is, the risk identification model can output what type of risk exists in the current medical service process. For example, if the risk type includes medical qualification risk, consultation process risk, diagnosis result risk, and prescription risk, then when a risk is identified in the diagnosis result, the risk identification model can output "there is a risk in the diagnosis result".
[0082] In some implementations, risk identification results may include risk classification. Specifically, each risk type can be further subdivided into multiple risk classifications based on the specific circumstances of the risk. For example, when it is determined that some medications in a doctor's prescription involve duplicate medication, it can be identified that there is a prescription risk in the current medical service process, and the specific risk classification is "duplicate medication." In this case, the risk identification result output by the risk identification model can be "duplicate medication risk exists."
[0083] It should be understood that the risk identification result may include only the risk type or risk classification, or it may include both risk type and risk classification. For example, when "duplicate medication risk" occurs, the risk identification result output by the risk identification model may include "prescription risk exists" and "prescription risk includes duplicate medication risk".
[0084] Optionally, the risk identification results may further include risk levels. For example, risk levels can represent the actual probability of occurrence or severity of each risk, and can be set according to needs or the characteristics of each risk. For instance, for prescription risks, they can be divided into levels 1, 2, and 3 based on the severity of the side effects of various medications, with level 1 or 3 designated as the highest level. By setting risk levels, the risk identification results can be more flexibly applied to subsequent processing.
[0085] Optionally, the risk identification results may further include risk details. Risk details can be used to describe the detailed information about the risk. When the risk identification results are subsequently displayed to the client, medical staff, patients, maintenance personnel of the internet diagnostic platform, or other regulatory personnel can quickly grasp the detailed risk situation that occurred in the diagnosis and treatment service process through the risk details, thereby enabling them to consider appropriate countermeasures in a timely manner.
[0086] Optionally, to enable relevant personnel to respond to risks as quickly as possible, the risk identification results can also include management suggestions. While alerting to the risk, guidance information can be directly displayed or played through the user terminal, informing relevant personnel of the appropriate response measures to take when encountering the corresponding risk. This further contributes to subsequent risk mitigation efforts and enhances the ability to protect patient safety.
[0087] It should be understood that, depending on the actual needs, the risk identification results may include other information, or may not include one or more of the above information, and this specification does not limit this.
[0088] The various implementation methods provided in this specification utilize risk strategies and risk identification models pre-designed to address various risks that may occur during the internet-based medical service process. During the execution of the medical service process, the required target risk strategies and corresponding risk identification models can be determined. In turn, the actual medical information generated can be identified through the risk identification model to obtain risk identification results that reflect the security of the current medical service process.
[0089] In some preferred embodiments, each target risk strategy corresponds to a risk identification rule. Prior to step S303, the risk identification method may further include: inputting the risk identification rule corresponding to each target risk strategy into the risk identification model corresponding to each target risk strategy.
[0090] Specifically, a risk identification rule base can be pre-set, including multiple risk identification rules. Each risk identification rule can correspond to a risk strategy in the risk strategy base, indicating the specific verification content and method of that risk strategy. After determining the risk identification model, the risk identification rule corresponding to the target risk strategy can be input into the risk identification model corresponding to that target risk strategy, so that the risk identification model can verify the diagnosis and treatment information according to the risk identification rule, thereby obtaining the risk identification result.
[0091] For example, risk identification rules can be formulated based on national policies and regulations related to internet-based medical services and healthcare services, local regulatory requirements for internet-based medical services in various regions, drug instructions, clinical drug use guidelines, etc.
[0092] In some specific implementations, each risk identification rule may include the following parts: Rule Number: used to uniquely identify the current risk identification rule; Rule Title: used to describe the current risk identification rule; Attribution Strategy: used to indicate the correspondence between the current risk identification rule and the risk strategy; Rule Details: including the conditions for its validity and the rule logic.
[0093] For example, rule details can include multiple conditions, each consisting of a condition number, a left variable, an operator, and a right variable, such as "1. Patient gender = male". Rule logic can be represented by the condition numbers in the rule details connected by AND, OR, parentheses, etc., indicating the execution logic of the current risk identification rule to determine whether the current risk identification rule is met. For example, "1&2&(3|4)" can mean: the current risk identification rule is met when conditions 1 and 2 are both true and either condition 3 or condition 4 is true.
[0094] Optionally, each risk identification rule may also include the following parts: Risk Classification: Used to specify the risk corresponding to the current risk identification rule, such as the risk classification "duplicate medication" in the risk type "prescription medication"; Risk Level: Used to specify the corresponding risk level, such as level 1 or level 3; Risk Description: Used to describe the specific circumstances of the risk; Handling Recommendations: Used to provide risk response recommendations to relevant personnel.
[0095] Optionally, each risk identification rule may also include an effective region. The effective region is used to specify in which regions the current risk identification rule is effective, thereby enabling the risk identification method provided in this specification to be applied to different regions and flexibly address the risks that may arise in the medical service process under various special circumstances.
[0096] Figure 4 This is a flowchart illustrating a risk identification method for an internet-based medical platform, provided as one embodiment of this specification. This risk identification method can be executed by a server, for example, by... Figure 2 Server 210 in the system shown is executing. Figure 3 Based on the risk identification method shown, Figure 4 The risk identification method shown may further include the following steps:
[0097] Step S404: Determine if there is any new medical information. If so, obtain the new medical information.
[0098] Step S405: Input the newly added diagnosis and treatment information into the risk identification model corresponding to each target risk strategy to obtain the updated risk identification results.
[0099] It should be understood that the process of determining risk identification results based on newly added medical information is similar to... Figure 3 The process for determining risk identification results based on medical information provided in the illustrated embodiment is similar, and can be referred to in detail. Figure 3 The specific details of the embodiments shown will not be repeated here.
[0100] Optionally, in step S404, if it is determined that there is no new diagnosis and treatment information, the current risk identification result can be output, and step S405 is no longer executed.
[0101] Optionally, in some implementations, the risk identification method may further include the following steps:
[0102] Step S406: Determine whether the current medical service has ended. If not, repeat step S404; if yes, output the current risk identification result.
[0103] By assessing the progress of medical services, risk identification results can be output in a timely manner, saving computing resources.
[0104] In some alternative implementations, Figure 3 or Figure 4 The risk identification method shown may also include: inputting risk identification labels into the risk identification model corresponding to each target risk strategy.
[0105] Specifically, a risk identification label library can be pre-built, which may include multiple risk identification labels. For example, risk identification labels may include drug labels and disease labels, corresponding to specific drugs and specific diseases as preset. When determining risk strategies and corresponding risk identification rules based on medical information, the risk identification labels can be input into the risk identification model, enabling the model to more accurately identify key identification information from the medical information, thereby identifying the relevant risks of specific drugs and / or specific diseases.
[0106] In some alternative implementations, Figure 3 or Figure 4 The risk identification method shown may also include: inputting the medical qualification database into the risk identification model corresponding to each target risk strategy.
[0107] Here, the medical qualification database can consist of hospital qualification data, doctor qualification data, pharmacist qualification data, and real-person authentication data. For example, hospital qualification data can refer to relevant practice information for internet hospitals, such as a "Medical Institution Practice License"; doctor qualification data can refer to the identity information that doctors must provide to provide medical services online, such as physician qualification certificates; pharmacist qualification data can refer to the identity information that pharmacists must provide to provide prescription review services online, such as pharmacist qualification certificates; and real-person authentication data can refer to all relevant information that can be used to prove the identity and real name of natural persons, including doctors, pharmacists, and patients, including but not limited to ID documents, photos, videos, hardware terminal information, and historical authentication results.
[0108] By utilizing a pre-set database of medical qualifications, the relevant risks to medical staff and patients can be identified more accurately and efficiently, thereby improving the reliability of the overall medical service process.
[0109] The risk identification method provided in this specification, through a combination of risk strategies and risk identification models, achieves comprehensive risk identification coverage of the entire process of internet-based medical services. It allows for rapid configuration of risks with different characteristics via risk strategies and risk identification rules, supports flexible expansion of the risk identification model, and meets the differentiated regulatory requirements of internet-based medical services in various regions through the localized configuration of risk strategies and risk identification rules. It eliminates the shortcomings of related technologies that cannot identify most risks in internet-based medical services, and can cover potential risks in multiple stages of the overall medical service process, achieving comprehensive identification and effectively avoiding omissions.
[0110] Example devices, electronic devices, storage media, and software
[0111] Figure 5 This specification provides one embodiment of a risk identification device 500 for an internet-based medical platform. For example... Figure 5 As shown, the risk identification device 500 may include:
[0112] The strategy selection module 501 is used to select at least one target risk strategy from the risk strategy library;
[0113] The model determination module 502 is used to determine the risk identification model corresponding to each target risk strategy from a set of multiple preset risk identification models.
[0114] The acquisition module 503 is used to input the acquired diagnosis and treatment information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current diagnosis and treatment service process. The risk identification model is used to execute the corresponding target risk strategy to identify the diagnosis and treatment information.
[0115] The various implementation methods provided in this specification utilize risk strategies and risk identification models pre-designed to address various risks that may occur during the internet-based medical service process. During the actual execution of the medical service process, the required target risk strategies and corresponding risk identification models can be determined. In turn, the actual medical information generated can be identified through the risk identification model to obtain risk identification results that reflect the safety of the current medical service process.
[0116] In some implementations, at least one target risk strategy includes a basic risk strategy, and the current medical service process includes at least one medical stage. The strategy selection module 501 may include a first strategy selection unit, used to determine, from a risk strategy library, at least one risk strategy corresponding to the current medical stage as the basic risk strategy.
[0117] In some implementations, at least one target risk strategy further includes a supplementary risk strategy, wherein the strategy selection module 501 may further include a history acquisition unit and a second strategy selection unit. The history acquisition unit may be used to acquire the risk identification results of previous diagnosis and treatment stages as reference risk information; the second strategy selection unit may be used to determine at least one risk strategy corresponding to the reference risk information as a supplementary risk strategy from the risk strategy library.
[0118] In some implementations, at least one target risk strategy further includes a key risk strategy. The strategy selection module 501 may further include a key judgment unit and a third strategy selection unit. The key judgment unit can be used to determine whether the diagnostic information includes preset key identification information; the third strategy selection unit can be used to determine at least one risk strategy corresponding to the key identification information in the risk strategy library as a key risk strategy when the diagnostic information includes key identification information.
[0119] In some implementations, the preset key identification information may include specific disease information and / or specific drug information.
[0120] In some implementations, the model determination module 502 may be specifically used to: determine the risk type of each target risk strategy, wherein the risk type includes one of medical qualification risk, consultation process risk, diagnosis result risk, and prescription risk; and determine the risk identification model corresponding to each target risk strategy from a plurality of preset risk identification models based on the risk type.
[0121] In some embodiments, the risk identification device may further include a judgment module and an update module. The judgment module may be used to determine whether there is any new medical information, and if so, to obtain the new medical information. The update module may be used to input the new medical information into the risk identification model corresponding to each target risk strategy to obtain the updated risk identification result.
[0122] In one embodiment of this specification, each target risk strategy corresponds to a risk identification rule. The acquisition module 503 can also be used to input the risk identification rule corresponding to each target risk strategy into the risk identification model corresponding to each target risk strategy.
[0123] The specific implementation process of the functions and roles of each module and unit in the above-mentioned risk identification device can be found in the implementation process of the corresponding steps in the above-mentioned risk identification method, and will not be repeated here.
[0124] Figure 6 The diagram shown is a block diagram of an electronic device 600 provided in one embodiment of this specification. Figure 6 As shown, the electronic device 600 includes: a memory for storing a computer program; and a processor for executing the computer program to implement the risk identification method provided in any embodiment of this specification.
[0125] For example, electronic device 600 may include processing component 610, which further includes one or more processors, and memory resources represented by memory 620 for storing instructions, such as applications, that can be executed by processing component 610. The applications stored in memory 620 may include one or more modules, each corresponding to a set of instructions. Furthermore, processing component 610 is configured to execute instructions to perform the risk identification method described above.
[0126] Electronic device 600 may also include a power supply component configured to perform power management of electronic device 600, a wired or wireless network interface configured to connect electronic device 600 to a network, and an input / output (I / O) interface. Electronic device 600 may operate on an operating system stored in memory 620, such as Windows Server™, Mac OSX™, Unix™, Linux™, FreeBSD™, or similar.
[0127] One embodiment of this specification provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, causes the computer to perform the risk identification method provided in any embodiment of this specification.
[0128] One embodiment of this specification provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the risk identification method provided in any embodiment of this specification.
[0129] It is understood that the specific examples in this document are only intended to help those skilled in the art better understand the embodiments described herein, and are not intended to limit the scope of the invention.
[0130] It is understood that in the various embodiments described in this specification, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments described in this specification.
[0131] It is understood that the various implementation methods described in this specification can be implemented individually or in combination, and the implementation methods in this specification are not limited in this respect.
[0132] Unless otherwise stated, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of this specification. The term "and / or" as used in this specification includes any and all combinations of one or more of the associated listed items. The singular forms "a," "the," and "the" as used in the embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.
[0133] It is understood that the processor in the embodiments of this specification can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-described method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this specification can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.
[0134] It is understood that the memory in the embodiments of this specification may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0135] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this specification.
[0136] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the aforementioned method implementations, and will not be repeated here.
[0137] In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0138] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.
[0139] In addition, the functional units in the various embodiments of this specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0140] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this specification, in essence, or the parts that contribute to the prior art, or parts of the technical solutions, can be embodied in the form of software products. These computer software products are stored in a storage medium and include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this specification. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0141] The above description is merely a specific embodiment of this specification, but the scope of protection of this invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this specification should be included within the scope of protection of this specification. Therefore, the scope of protection of this invention should be determined by the scope of the claims.
Claims
1. A risk identification method for internet-based medical service platforms, characterized in that, include: Select at least one target risk strategy from the risk strategy library, wherein the at least one target risk strategy includes a basic risk strategy and a key risk strategy; Among the multiple preset risk identification models, determine the risk identification model corresponding to each target risk strategy; The acquired medical information is input into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current medical service process. The risk identification model is used to execute the corresponding target risk strategy to identify the medical information. The current diagnosis and treatment service process includes at least one diagnosis and treatment stage, and the selection of at least one target risk strategy from the risk strategy library includes: In the risk strategy library, at least one risk strategy corresponding to the current treatment stage is determined as the basic risk strategy. The basic risk strategy is used to identify risks in fixed-type treatment information in the treatment information, where the fixed-type treatment information is generated by fixed execution items present in the current treatment stage; and; Determine whether the diagnostic information includes preset key identification information. If the diagnostic information includes the key identification information, determine at least one risk strategy corresponding to the key identification information from the risk strategy library as the key risk strategy. The preset key identification information includes specific disease information that restricts the relevant qualifications of the doctor issuing the diagnosis and / or specific drug information that restricts the relevant qualifications of the doctor prescribing the prescription. The key risk strategy is used to identify the risk of doctors making unauthorized diagnoses.
2. The risk identification method according to claim 1, characterized in that, The at least one target risk strategy also includes supplementary risk strategies. The step of selecting at least one target risk strategy from the risk strategy library further includes: Obtain the risk identification results from the earlier diagnosis and treatment phases as reference risk information; In the risk strategy library, at least one risk strategy corresponding to the reference risk information is determined as the supplementary risk strategy.
3. The risk identification method according to claim 1, characterized in that, The step of determining the risk identification model corresponding to each target risk strategy from a set of preset risk identification models includes: Determine the risk type for each target risk strategy, wherein the risk type includes one of medical qualification risk, consultation process risk, diagnosis result risk, and prescription risk; Based on the risk type, a risk identification model corresponding to each target risk strategy is determined from among the preset multiple risk identification models.
4. The risk identification method according to claim 1, characterized in that, Also includes: Determine whether there is any new medical information; if so, obtain the new medical information. The newly added diagnosis and treatment information is input into the risk identification model corresponding to each target risk strategy to obtain the updated risk identification results.
5. The risk identification method according to claim 1, characterized in that, Each of the aforementioned target risk strategies corresponds to a risk identification rule. Specifically, before inputting the acquired medical information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current medical service process, the risk identification method further includes: The risk identification rules corresponding to each target risk strategy are input into the risk identification model corresponding to each target risk strategy.
6. A risk identification device for an internet-based medical platform, characterized in that, include: The strategy selection module is used to select at least one target risk strategy from the risk strategy library, wherein the at least one target risk strategy includes a basic risk strategy and a key risk strategy; The model determination module is used to determine the risk identification model corresponding to each target risk strategy from a set of preset risk identification models. The acquisition module is used to input the acquired diagnosis and treatment information into the risk identification model corresponding to each target risk strategy to obtain the risk identification result of the current diagnosis and treatment service process. The risk identification model is used to execute the corresponding target risk strategy to identify the diagnosis and treatment information. The strategy selection module includes a first strategy selection unit, a key judgment unit, and a third strategy selection unit. The current diagnosis and treatment service process includes at least one diagnosis and treatment stage. The first strategy selection unit is used to determine at least one risk strategy corresponding to the current diagnosis and treatment stage as the basic risk strategy. The basic risk strategy is used to identify risks in fixed-type diagnosis and treatment information in the diagnosis and treatment information. The fixed-type diagnosis and treatment information is generated by fixed execution items in the current diagnosis and treatment stage. The key point judgment unit is used to determine whether the diagnostic information includes preset key point identification information; and The third strategy selection unit is used to determine at least one risk strategy corresponding to the key identification information in the risk strategy library as the key risk strategy when the diagnosis and treatment information includes the key identification information. The preset key identification information includes specific disease information that restricts the relevant qualifications of the doctor who makes the diagnosis and / or specific drug information that restricts the relevant qualifications of the doctor who prescribes the prescription. The key risk strategy is used to identify the risk of whether the doctor makes an unauthorized diagnosis.
7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the risk identification method according to any one of claims 1-5.
Citation Information
Patent Citations
Risk prevention and control method and device
CN110147967A
Risk decision-making method and system
CN112862339A
Risk early warning method and device and electronic equipment
CN114694843A
