Emr system linked to chatbot performing consultation and reservation

Abstract

Disclosed is an operating method of an electronic device including a chatbot that performs a consultation for a hospital reservation. The present operating method comprises the steps of: providing, to a user terminal, a conversation user interface (UI) for performing a conversation with the chatbot; updating schedule information of a hospital by adding a procedure schedule on the basis of content of the conversation performed between a user and the chatbot through the conversation UI; when a request for medical record information of the user is received from a hospital terminal of the hospital, providing, to the hospital terminal, the procedure schedule together with the medical record information of the user; and providing, to the hospital terminal, conversation content between the chatbot and the user related to the procedure schedule.

Description

EMR system linked to a chatbot that performs consultations and reservations

[0001] The present disclosure relates to an operating method of an electronic device or system that operates an EMR system, and more specifically, to an EMR system that is linked to a chatbot's consultation or reservation.

[0002] The EMR (Electronic Medical Record) system is a system for recording and preserving all medical records of individual customers / patients as electronic documents.

[0003] The EMR system has advantages in minimizing manual work in medical institutions, reducing document management costs, providing convenience in information storage, facilitating medical professionals' access to patient records, and enabling diverse use of information.

[0004] EMR is mainly managed based on medical records directly entered by doctors or nurses, so it is highly useful in terms of accuracy, but has limitations in the information it provides.

[0005] For example, a typical EMR typically does not include detailed consultations between patients and doctors, nor does it typically include consultations between professional counselors and patients / customers.

[0006] However, detailed communication history with patients / customers is a very important factor in terms of not only hospital treatment but also sales and management strategies, so it is necessary to manage these factors in conjunction.

[0007] Typically, consultants not only perform the role of salespeople, but also provide information about procedures and manage reservations and schedules.

[0008] However, if this counseling structure is maintained, as the size of the hospital grows, the number of counselors also increases, making it difficult to manage human resources and the quality of counseling, and the cost of hiring counselors also continues to increase.

[0009] The present disclosure not only utilizes a chatbot to conduct consultations for making reservations for procedures, etc., but also provides an operating method of an electronic device based on EMR that manages conversations obtained through the chatbot by linking them with medical records.

[0010] According to one embodiment of the present disclosure, a method for operating an electronic device including a chatbot for performing consultation for making a reservation at a hospital may include the steps of providing a conversational UI (User Interface) for performing a conversation with the chatbot through a user terminal, updating schedule information of the hospital by adding a treatment schedule based on a conversation performed between a user and the chatbot through the conversational UI, providing the treatment schedule together with the user's medical record information to the hospital terminal when a request for the user's medical record information is received from a hospital terminal of the hospital, and providing the conversation content between the user and the chatbot related to the treatment schedule to the hospital terminal.

[0011] The method of operating the electronic device may include providing the conversation UI to each of a plurality of user terminals, adding a treatment schedule for each of the plurality of users through the chatbot, providing information on a plurality of treatment schedules reserved for each of the plurality of users to the hospital terminal, and providing, when at least one treatment schedule among the plurality of treatment schedules is selected by the hospital terminal, a conversation content between the user and the chatbot related to the selected treatment schedule to the hospital terminal.

[0012] In this case, the step of adding a treatment schedule for each of the plurality of users may include, when a reservation for a first treatment schedule is requested based on the conversation between the first user and the chatbot, updating the schedule information of the hospital by adding the first treatment schedule, and, when a reservation for a second treatment schedule that overlaps with the first treatment schedule is requested based on the conversation between the second user and the chatbot while the first treatment schedule is added, updating the schedule information of the hospital by adding a third treatment schedule in which the second treatment schedule is changed.

[0013] Meanwhile, the electronic device may include a basic chatbot for registering a treatment schedule. In this case, the operating method of the electronic device may include: acquiring, through the hospital terminal, treatment menu information including the types of treatments available for reservation, work information on available personnel for each type of treatment, and the time required for each type of treatment; and tuning the basic chatbot to register at least one treatment schedule based on the treatment menu information, thereby creating a dedicated chatbot matching the hospital.

[0014] The method of operating the electronic device may include a step of obtaining information on the user's medical records and the progress of the procedure through the hospital terminal when the procedure schedule ends, and a step of updating the user's medical record information based on the medical records and the progress of the procedure.

[0015] In addition, if the medical record information of the user is not pre-registered at the time the procedure schedule is added, the method may include a step of extracting at least one medical keyword from the conversation between the user and the chatbot, and a step of generating the medical record information of the user based on a sentence including the at least one medical keyword extracted from the conversation.

[0016] Here, the step of generating the user's medical record information may include analyzing a plurality of sentences including at least one medical keyword in the conversation content to select a main sentence indicating at least one of the user's diseases, procedures, and symptoms, and generating and storing medical record information including the selected main sentence.

[0017] The method of operating an electronic device according to the present disclosure not only provides consultations on procedures, etc. to multiple users without time constraints through a chatbot, but also manages the acquired conversation content and procedure schedule in conjunction with medical records to provide an EMR service that includes more detailed and useful information.

[0018] FIG. 1 is a drawing for explaining an operation in which an electronic device according to an embodiment of the present disclosure provides treatment consultation through a user terminal and provides a treatment schedule reserved according to the consultation along with medical record information to a hospital terminal.

[0019] FIG. 2 is a flowchart illustrating an operation of an electronic device according to an embodiment of the present disclosure to provide consultation through a chatbot and add a treatment schedule;

[0020] FIG. 3 is a sequence diagram for explaining an operation of an electronic device according to an embodiment of the present disclosure adding a treatment schedule through a chatbot and providing medical record information at the request of a hospital terminal while providing the treatment schedule together.

[0021] FIG. 4 is a sequence diagram for explaining a process in which an electronic device according to an embodiment of the present disclosure simultaneously provides chatbot-based consultations to multiple users while preventing overlapping reservations for treatment schedules.

[0022] FIG. 5A is a drawing for explaining an operation of providing reservation information and consultation contents of a treatment schedule in a process of providing EMR to a hospital terminal by an electronic device according to an embodiment of the present disclosure;

[0023] FIG. 5b is a drawing for explaining an operation of an electronic device according to an embodiment of the present disclosure to provide a UI including information on reservation, reception, storage, etc. in real time.

[0024] FIG. 6 is a block diagram illustrating the configuration of an electronic device according to an embodiment of the present disclosure;

[0025] FIG. 7 is a diagram for explaining an operation of an electronic device according to an embodiment of the present disclosure utilizing multiple chatbots matched to each hospital;

[0026] FIG. 8 is a flowchart illustrating an operation of an electronic device according to an embodiment of the present disclosure to obtain a dedicated chatbot suitable for an individual hospital based on treatment menu information obtained through a hospital terminal; and

[0027] FIG. 9 is a block diagram illustrating a configuration of an electronic device according to various embodiments of the present disclosure.

[0028] Before describing the present disclosure in detail, the description method of the specification and drawings will be described.

[0029] First, the terms used in this specification and claims are general terms selected based on their functions in the various embodiments of the present disclosure. However, these terms may vary depending on the intentions of those skilled in the art, legal or technical interpretations, and the emergence of new technologies. Furthermore, some terms may have been arbitrarily selected by the applicant. These terms may be interpreted according to the meanings defined in this specification. In the absence of a specific definition, they may be interpreted based on the overall content of this specification and common technical knowledge in the relevant field.

[0030] Additionally, the same reference numbers or symbols in each drawing attached to this specification represent parts or components that perform substantially the same functions. For convenience of explanation and understanding, the same reference numbers or symbols are used in different embodiments. In other words, even if components with the same reference numbers are all depicted in multiple drawings, the multiple drawings do not necessarily represent a single embodiment.

[0031] Additionally, terms including ordinal numbers, such as "first," "second," etc., may be used in this specification and claims to distinguish between components. These ordinal numbers are used to distinguish identical or similar components from each other, and the use of these ordinal numbers should not be interpreted in a limited manner. For example, components associated with these ordinals should not be restricted in their order of use or arrangement by their numbers. If necessary, each ordinal number may be used interchangeably.

[0032] In this specification, singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "comprise" or "consist of" are intended to indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but should be understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0033] In the embodiments of the present disclosure, terms such as "module," "unit," "part," etc. are terms used to refer to components that perform at least one function or operation, and such components may be implemented as hardware or software, or a combination of hardware and software. In addition, a plurality of "modules," "units," "parts," etc. may be integrated into at least one module or chip and implemented as at least one processor, except in cases where each needs to be implemented as a separate, specific hardware.

[0034] Additionally, in the embodiments of the present disclosure, when a part is said to be connected to another part, this includes not only a direct connection but also an indirect connection through another medium. Furthermore, unless specifically stated otherwise, the statement that a part includes a certain component does not exclude other components, but rather implies that other components may be included.

[0035] FIG. 1 is a drawing for explaining an operation of an electronic device according to an embodiment of the present disclosure providing treatment consultation through a user terminal and providing a treatment schedule reserved according to the consultation along with medical record information to a hospital terminal.

[0036] Referring to FIG. 1, the electronic device (100) may include at least one chatbot (10) for providing consultation on a procedure provided by at least one hospital.

[0037] An electronic device (100) can communicate with a user terminal (200) to provide treatment consultation through a chatbot (10). The chatbot (10) may include, but is not limited to, a Large Language Model (LLM) trained to provide responses to inquiries based on knowledge data related to treatments provided by a hospital.

[0038] Additionally, the electronic device (100) can register the user's treatment schedule based on the conversation between the chatbot (10) and the user. Specifically, the electronic device (100) can add a treatment schedule based on command information from the chatbot (10) requesting additional registration of a treatment schedule. As a result, the treatment schedule can be added, updating the hospital's schedule information.

[0039] Additionally, the electronic device (100) can manage medical record information including information on the personal information, treatment history, diagnosis history, etc. of a patient / customer that matches the user terminal (200).

[0040] The electronic device (100) can provide medical record information of a patient / customer to at least one hospital terminal (300), and at this time, the electronic device (100) can also provide schedule information including the patient / customer's scheduled treatment schedule. In addition, the electronic device (100) can store the contents of consultations conducted between the chatbot (10) and the customer / patient and provide them to the hospital terminal (300).

[0041] In this way, the electronic device (100) according to the present disclosure not only reduces the need for consultation personnel by utilizing a chatbot (10) to automatically perform consultations and reservations, but also provides the consultation content and treatment schedule of the chatbot (10) together with medical record information, thereby constructing a system environment that is more efficient and contains a lot of diversified information than the existing EMR. In particular, since consultations via the user terminal (200) are performed by the chatbot (10), there is an advantage in that conversation content and treatment schedules can be managed together with the EMR without much difficulty.

[0042] The electronic device (100) may be implemented as a server that provides at least one web page or application. Alternatively, the electronic device (100) may be implemented as a user terminal, such as a smartphone, tablet PC, desktop PC, notebook PC, or PDA. Alternatively, the electronic device (100) may correspond to a terminal device installed in a specific area (e.g., a hospital reception desk, a consultation room, etc.), such as a kiosk. The following drawings will describe the electronic device (100) as a server.

[0043] FIG. 2 is a flowchart illustrating an operation of an electronic device according to an embodiment of the present disclosure to provide consultation through a chatbot and add a treatment schedule.

[0044] The electronic device (100) can provide a UI (User Interface) for conversation with a chatbot (10) by accessing a hospital's webpage link or application for consultation through a user terminal (200) (S210).

[0045] Specifically, the electronic device (100) can support a conversation between a chatbot (10) and a user (customer / patient) by providing at least one conversation UI for visually providing conversation content corresponding to the input and output of the chatbot through a user terminal (200).

[0046] For example, the electronic device (100) may input a first message of a user related to at least one procedure received through a conversational UI into a chatbot, and provide a second message of the chatbot in response to the first message through the conversational UI.

[0047] If each hospital has a separate chatbot, the electronic device (100) can provide consultation to customers requesting consultation at each hospital via a chatbot matching the hospital. For example, the electronic device (100) can support consultation via chatbot a for users who access the consultation link for hospital A, and support consultation via chatbot b for users who access the consultation link for hospital B.

[0048] In addition, the electronic device (100) can update the hospital's schedule information by adding a treatment schedule based on the conversation between the chatbot (10) and the user (S220).

[0049] The chatbot (10) may be trained to generate a command to register a schedule matching the requested treatment when a treatment is requested from a user through a conversation.

[0050] For example, if a user input requesting a treatment appointment according to at least one treatment schedule is received from a user terminal (200), the chatbot (10) may generate command information for registering the treatment schedule. In this case, the electronic device (100) may update the hospital's schedule information by adding a treatment schedule for the user. At this time, the electronic device (100) may also transmit information regarding the added treatment schedule to the user terminal (200).

[0051] When at least one treatment schedule is added to the schedule information, a user terminal (200) of a user who is a party to the treatment schedule may conduct a conversation with the chatbot (10), and a query from the user requesting a change or cancellation of the treatment schedule may be received. In this case, the chatbot (10) may generate command information for changing or canceling the treatment schedule, and the schedule management module (132) of the electronic device (100) may update the schedule information by changing or canceling the treatment schedule. At this time, the electronic device (100) may transmit information regarding the changed treatment schedule to the user terminal (200).

[0052] FIG. 3 is a sequence diagram illustrating an operation of an electronic device according to an embodiment of the present disclosure adding a treatment schedule through a chatbot and providing medical record information at the request of a hospital terminal while providing the treatment schedule together.

[0053] Referring to FIG. 3, the electronic device (100) can provide a conversational UI to the user terminal (200) to provide consultation with the chatbot (10). At this time, if the user requests a treatment reservation during the conversation (S320), the electronic device (100) can update schedule information in real time to prevent overlapping treatment schedule reservations.

[0054] Specifically, the electronic device (100) can compare the schedule information and the treatment schedule to determine whether another treatment schedule that overlaps already exists (S330).

[0055] If the requested treatment schedule does not overlap with existing schedule information as a result of determining whether there is a duplicate according to at least one of the above-described embodiments, the electronic device (100) can register the user's treatment reservation by adding the treatment schedule (S340).

[0056] The above-described process of registering a treatment reservation by determining whether there is any duplication in schedule information may be performed directly by the chatbot (10) (first mode) or may be performed by the schedule management module of the electronic device (100) (second mode).

[0057] First, we explain the first mode, in which the chatbot automatically checks for overlapping treatment schedules and requests additional schedules.

[0058] When the first mode is activated, if a request is made to schedule a specific procedure for a specific date and time during a conversation between the chatbot (10) and a user, the chatbot (10) can determine whether the requested procedure schedule can be added. Specifically, the chatbot (10) can compare the procedure schedule matching the requested procedure schedule with current real-time schedule information to determine whether there is a duplication. To this end, the electronic device (100) can input the current schedule information into the chatbot (10) in real time while the conversation is in progress. For example, when an event occurs where the procedure schedule of at least one user is added / changed / cancelled and the hospital's schedule information is updated, the electronic device (100) can input the updated schedule information into the chatbot (10). As a result, the chatbot (10) can check schedule information in real time during a conversation with multiple users, thereby avoiding duplication of procedure reservations while enabling the quick addition of procedure schedules for each of multiple users. If the requested treatment schedule can be registered, the chatbot (10) can generate command information for registering the requested treatment schedule. As a result, the schedule management module (132) can update the schedule information by adding the treatment schedule. Conversely, if the requested treatment schedule cannot be registered, the chatbot (10) can provide the user with a message indicating that the treatment schedule needs to be changed. At this time, the message can be provided via the conversation UI. Thereafter, a changed treatment schedule can be requested based on the conversation, and a non-overlapping treatment schedule can be added.

[0059] When the second mode is activated, the electronic device (100) can provide the chatbot (10) with schedule information at that time only when a conversation between the chatbot (10) and a user begins. Here, when a command for adding a treatment schedule is generated by the chatbot (10) based on the conversation with the user, the schedule management module of the electronic device (100) can determine whether the requested treatment schedule can be added. Specifically, the schedule management module can compare the treatment schedule matching the requested treatment reservation with the current real-time schedule information to determine whether there is an overlap. Even if the chatbot (10) requests the addition of a treatment schedule that does not overlap based on the schedule information at the start of the conversation, this is to take into account the possibility that another treatment schedule may occur at the same time as the conversation progresses, as conversations with other users are conducted simultaneously. If the addition of a treatment schedule is possible, the schedule management module can update the schedule information by adding the treatment schedule. On the other hand, if adding a treatment schedule is not possible due to overlapping, the electronic device (100) may request a change in the treatment schedule from the chatbot (10). In this case, the schedule management module may input real-time schedule information at the time of requesting the change into the chatbot (10), thereby allowing the chatbot (10) to avoid the corresponding date and time while considering the treatment schedules of other users and making reservations. As a result, the chatbot (10) may generate a message notifying the user that a change is necessary due to overlapping treatment schedules, and may provide this message to the user via the conversational UI.

[0060] Based on the same number of users, the first mode has a greater load than the second mode, considering the complexity of the operation of the artificial intelligence model within the chatbot (10), as schedule information is input to the chatbot (10) in conversation every time the schedule information is updated.

[0061] The electronic device (100) can activate either the first mode or the second mode. For example, based on a chatbot for consultations regarding procedures at a specific hospital, the electronic device (100) can activate the first mode when the chatbot simultaneously converses with fewer than a threshold number of users, and activate the second mode when the chatbot simultaneously converses with more than a threshold number of users. In this way, when the number of users simultaneously converses is large, the second mode, which has a relatively low load, is selected, thereby ensuring system stability.

[0062] For example, the electronic device (100) can identify the number of users having a conversation with the chatbot every certain time unit (e.g., 10 minutes, 20 minutes, 30 minutes, etc.) and activate the first mode or the second mode (for each certain time unit) by comparing the number of identified users with the threshold number described above.

[0063] Here, the threshold number can be set differently for each time zone. For example, the electronic device (100) can monitor the number of users who engage in consultations with the chatbot at each time zone according to a certain period (e.g., weekly, monthly). The time zones can correspond to multiple time intervals divided by a certain time unit (e.g., 1 hour, 2 hours, 4 hours, etc.). For example, time zones such as Monday 9:00 AM to 10:00 AM and Monday 10:00 AM to 11:00 AM can be defined separately.

[0064] In this case, the electronic device (100) can identify the number of users conducting consultations with the chatbot for each time zone of each cycle. In addition, the electronic device (100) can set the aforementioned threshold number for each time zone of the next cycle based on the average value of the number of users identified for each time zone for a recent period (e.g., N cycles). Specifically, the larger the average value, the smaller the threshold number, and the smaller the average value, the larger the threshold number. As a result, the overall load of the electronic device (100) or the system required for each time zone can be generally evenly distributed. That is, for time zones with many users, the second mode with a small load is more likely to be maintained despite changes in the number of real-time users, and for time zones with few users, the first mode with a large load is more likely to be activated despite changes in the number of real-time users, and as a result, a situation in which the load difference between time zones becomes severe can be prevented.

[0065] Meanwhile, the hospital terminal (300) can request the user's medical record information via the electronic device (100) (S350). That is, hospital staff can access the EMR system provided by the electronic device (100) via the hospital terminal (300) and view the medical records of each user (customer / patient).

[0066] At this time, the electronic device (100) may not only provide the requested user's medical record information, but also provide information regarding the user's scheduled treatment (type of treatment, date, etc.) (S360). Furthermore, the electronic device (100) may provide the hospital terminal (300) with the conversation between the user and the chatbot (10) related to the treatment schedule.

[0067] Meanwhile, the electronic device (100) can identify whether the user's medical record information is already registered on the electronic device (100) at the time the procedure schedule is added. In other words, it can be determined whether the user who has a procedure scheduled is a first-time customer at the hospital.

[0068] If the user's medical record information is not already registered at the time the procedure schedule is added, the electronic device (100) can automatically create the user's medical record information.

[0069] Specifically, the electronic device (100) can extract at least one medical keyword from the conversation between the user and the chatbot (100). The medical keyword corresponds to words related to medical information such as disease, medical treatment, procedure, and symptom, and the electronic device (100) can extract the medical keyword from the conversation by comparing it with a plurality of pre-stored medical keywords.

[0070] In addition, the electronic device (100) can generate the user's medical record information based on a sentence containing at least one medical keyword extracted from the conversation content.

[0071] Specifically, the electronic device (100) can extract only sentences containing medical keywords from the conversation content, and perform natural language understanding only on the extracted sentences to select key sentences indicating the user's disease status / history, treatment history, desired treatment, and symptom status / history. To this end, at least one natural language understanding module for natural language understanding can be utilized, and the natural language understanding module can perform mechanical understanding by converting text into a vector, including at least one transformer, encoder, etc.

[0072] In addition, the electronic device (100) can generate and register the user's medical record information to include the selected key sentences. Thereafter, the electronic device (100) can provide the user's (customer / patient's) treatment schedule to the hospital terminal (300) as well as medical record information. In this way, the electronic device (100) according to the present disclosure has the advantage of constructing or adding medical record information and treatment schedules based on the consultation with the chatbot (10), and managing the quality of the information confirmed by the hospital terminal (300).

[0073] Meanwhile, the electronic device (100) can simultaneously provide consultations of a chatbot (10) related to a hospital to multiple user terminals through a conversational UI.

[0074] FIG. 4 is a sequence diagram illustrating a process in which an electronic device according to an embodiment of the present disclosure simultaneously provides chatbot-based consultations to multiple users while preventing overlapping reservations for treatment schedules.

[0075] Referring to FIG. 4, the electronic device (100) can conduct conversations with two users based on a single chatbot matched to a hospital. Specifically, the electronic device (100) can support conversations with the chatbot by providing a conversation UI to each of the first user terminal (200-1) and the second user terminal (200-2) (S410, S420).

[0076] Here, when a request is made for a specific treatment reservation for a specific date and time (addition of treatment schedule) from the first user terminal (200-1) (S430), the electronic device (100) compares the schedule information with the (requested) treatment schedule (S440), and, assuming that there is no duplication, can add the treatment schedule and update the schedule information (S450).

[0077] At this time, if a treatment reservation is requested from a second user terminal (200-2) that was also conducting a conversation with a chatbot (S460), the electronic device (100) can compare the schedule information with the treatment schedule (requested by the second user terminal (200-2)) (S470).

[0078] If the treatment schedule requested by the second user terminal (200-2) overlaps with the treatment schedule previously added by the first user terminal (200-1), the electronic device (100) can generate a message through the chatbot informing that a change in the treatment schedule is necessary and provide the message to the second user terminal (200-2) through the conversation UI.

[0079] As a result, additional consultations may be conducted, and the hospital's schedule information may be updated by adding a new procedure schedule with a change in the procedure schedule requested by the second user terminal (200-2).

[0080] Meanwhile, the electronic device (100) can provide information on multiple treatment schedules reserved for each of multiple users to the hospital terminal.

[0081] Here, when at least one treatment schedule among multiple treatment schedules is selected by the hospital terminal (300), the electronic device (100) can provide a conversation between the user and the chatbot (10) related to the treatment schedule selected by the hospital terminal (300).

[0082] Meanwhile, FIG. 5a is a drawing for explaining an operation of providing reservation information and consultation content for a treatment schedule in a process of providing EMR to a hospital terminal by an electronic device according to an embodiment of the present disclosure.

[0083] Referring to FIG. 5a, the electronic device (100) can provide reservation status (510) for each customer / patient via the hospital terminal (300). At this time, the reservation status (510) corresponds to schedule information with one or more treatment schedules added based on the current time.

[0084] The reservation status (510) may include multiple treatment schedules (511, 512, 513) reserved for one customer (e.g., Hong Gil-dong), and may also include treatment schedules reserved for multiple customers / patients.

[0085] Here, when a user input of a hospital terminal (300) selecting a treatment schedule (ex. 511) is obtained, the electronic device (100) can provide the contents of a consultation (520) between the chatbot (10) and the user that occurred during the process of adding the treatment schedule (ex. 511).

[0086] In this way, the electronic device (100) according to the present disclosure not only provides information on the treatment schedule of an individual customer / patient in conjunction with EMR, but also provides specific consultation content of a chatbot (10) that matches the treatment schedule, which is very useful information for patient / customer management and service.

[0087] FIG. 5b is a diagram for explaining an operation of an electronic device according to an embodiment of the present disclosure providing a UI including information on reservation, reception, storage, etc. in real time.

[0088] Referring to FIG. 5b, the electronic device (100) can provide information on reservation status for treatment schedules of various users (customers / patients), as well as reception status, waiting for payment, etc., through the hospital terminal (300).

[0089] Meanwhile, FIG. 6 is a block diagram for explaining the configuration of an electronic device according to an embodiment of the present disclosure.

[0090] FIG. 6 is a block diagram illustrating the configuration of an electronic device according to an embodiment of the present disclosure.

[0091] Referring to FIG. 6, the electronic device (100) may include a memory (110), a communication unit (120), and a processor (130).

[0092] The memory (110) is a configuration for storing an operating system (OS) for controlling the overall operation of components of the electronic device (100) and at least one instruction or data related to the components of the electronic device (100).

[0093] The memory (110) may include non-volatile memory such as ROM, flash memory, etc., and may include volatile memory composed of DRAM, etc. In addition, the memory (120) may include a hard disk, SSD (Solid state drive), etc.

[0094] Referring to FIG. 6, the memory (110) may include a chatbot. The chatbot, configured to perform treatment consultations, may include at least one artificial intelligence model for understanding text corresponding to a user's inquiry and providing a response. Specifically, the chatbot may be implemented as a Large Language Model (LLM) including at least one Transformer, but is not limited thereto.

[0095] The memory (110) may include schedule information for at least one hospital. The schedule information may include at least one treatment schedule for various customers / patients (users) and may be updated in real time.

[0096] The memory (110) may contain medical record information for various customers / patients. The medical record information may include personal information, physical information, medical history, family history, and other various biometric information of the customer / patient. The electronic device (100) may manage medical record information for each customer / patient and provide it to at least one hospital terminal (200), thereby operating as an EMR (Electronic Medical Record) system.

[0097] The communication unit (120) can be connected to an external server and / or terminal device through one or more networks, and at this time, data can be exchanged through various wired and wireless communication methods.

[0098] Depending on the area or scale, a network may be a personal area network (PAN), a local area network (LAN), or a wide area network (WAN), and depending on the openness of the network, it may be an intranet, an extranet, or the Internet.

[0099] Wireless communication may include at least one of communication methods such as LTE (long-term evolution), LTE-A (LTE Advance), 5G (5th Generation) mobile communication, CDMA (code division multiple access), WCDMA (wideband CDMA), UMTS (universal mobile telecommunications system), WiBro (Wireless Broadband), GSM (Global System for Mobile Communications), DMA (Time Division Multiple Access), WiFi (Wi-Fi), WiFi Direct, Bluetooth, NFC (near field communication), and Zigbee.

[0100] Wired communication may include at least one of the following communication methods: Ethernet, optical network, Universal Serial Bus (USB), ThunderBolt, etc.

[0101] Meanwhile, the communication method is not limited to the examples described above, and may include new communication methods that emerge as technology advances.

[0102] The processor (130) is a configuration for controlling the overall configuration and operation of the electronic device (100).

[0103] The processor (130) is connected to the memory (110) and can control the electronic device (100) by executing at least one instruction stored in the memory (110).

[0104] To this end, the processor (130) may be implemented as a general-purpose processor such as a CPU (Central Processing Unit), an AP (Application Processor), a graphics-only processor such as a GPU (Graphics Processing Unit), a VPU (Vision Processing Unit), or an artificial intelligence-only processor such as an NPU (Neural Processing Unit). The processor (130) may include a volatile memory such as an SRAM.

[0105] Referring to FIG. 6, the processor (130) can control various modules, such as a chatbot management module (131), a schedule management module (132), and an EMR module (133). Each of these modules corresponds to a functional unit module implemented in software and / or hardware.

[0106] The chatbot management module (131) is a module for managing chatbots. Specifically, the chatbot management module (131) can provide chatbot learning, user consultations via chatbots, and more.

[0107] In this process, the chatbot management module (131) can support a conversation between the chatbot and the user by providing at least one conversation UI (User Interface) to visually provide conversation content corresponding to the input and output of the chatbot through the user terminal (200).

[0108] The schedule management module (132) manages schedule information for at least one hospital. The schedule management module (132) can update schedule information by adding treatment schedules generated based on chatbot consultations, and can also cancel or change at least one treatment schedule based on user input received from the user terminal (200).

[0109] The EMR module (133) is a module for establishing and managing an EMR system for each hospital. Specifically, the EMR module (133) can manage medical record information for each user corresponding to a patient / customer and provide it to the hospital terminal (200). At this time, the EMR module (133) can also support personnel using the hospital terminal (200) to collectively check the medical record information and treatment schedule of each user (customer / patient) by managing the scheduled treatment schedule for each user in conjunction with the medical record information.

[0110] As an example, when a scheduled treatment schedule is completed according to the schedule information, the EMR module (133) can obtain information on the user's medical records and treatment progress through the hospital terminal (300). In this case, the EMR module (133) can also update the user's medical record information based on the medical records and treatment progress.

[0111] Meanwhile, FIG. 7 is a drawing for explaining an operation of an electronic device according to an embodiment of the present disclosure utilizing multiple chatbots matched to each hospital.

[0112] Referring to FIG. 7, the electronic device (100) may include separate chatbots (10-1, 2, 3, …) for providing consultation on treatment schedules for each hospital. For example, a chatbot (10-1) may provide consultation to a user terminal that has accessed a consultation link for Hospital A, a chatbot (10-2) may provide consultation to a user terminal that has accessed a consultation link for Hospital B, and a chatbot (10-3) may provide consultation to a user terminal that has accessed a consultation link for Hospital C.

[0113] At this time, each chatbot may be trained based on the types of procedures available for reservation at each hospital, the work information of the personnel available for each type of procedure (e.g., individual personnel work schedules), and the time required for each type of procedure.

[0114] As an example, the electronic device (100) includes a basic chatbot (e.g., LLM) to support consultation on treatment schedules and addition / registration of treatment schedules, but can also create a dedicated chatbot that matches each hospital according to the treatment menu information of each hospital.

[0115] In relation to this, FIG. 8 is a flowchart illustrating an operation of an electronic device according to an embodiment of the present disclosure to obtain a dedicated chatbot suitable for an individual hospital based on treatment menu information obtained through a hospital terminal.

[0116] Referring to FIG. 8, the electronic device (100) can obtain treatment menu information via the hospital terminal (S610). The treatment menu information may include, but is not limited to, the types of treatments available for reservation, information on the number of personnel available for each type of treatment, and the time required for each type of treatment.

[0117] Furthermore, the electronic device (100) can create a dedicated chatbot matching the hospital by tuning the aforementioned basic chatbot to register at least one treatment schedule based on the treatment menu information (S620). At this time, the electronic device (100) can also train the dedicated chatbot based on knowledge data related to at least one treatment included in the treatment menu information, thereby improving the quality of the dedicated chatbot's consultation regarding knowledge information for each treatment.

[0118] With the dedicated chatbot thus created, the electronic device (100) can provide a conversational UI for conducting a conversation with the dedicated chatbot to a user terminal accessing a consultation webpage matching the hospital. The electronic device (100) can input the user's message received through the conversational UI for conducting a conversation with the dedicated chatbot into the dedicated chatbot, and can update the hospital's schedule information by adding a treatment schedule for the user based on the command information generated by the dedicated chatbot. In addition, the electronic device (100) can transmit the updated hospital schedule information to the hospital terminal.

[0119] FIG. 9 is a block diagram illustrating a configuration of an electronic device according to various embodiments of the present disclosure.

[0120] If the electronic device (100) is implemented as a smartphone, tablet PC, notebook PC, kiosk, etc. rather than a server, as shown in FIG. 7, the electronic device (100) may further include a user input unit (140), an output unit (150), etc. in addition to a memory (110), a communication unit (120), and a processor (130).

[0121] The user input unit (140) is configured to receive user inquiries, commands, etc., and may include at least one button, keypad, touchpad, touchscreen, microphone, camera, etc., but is not limited thereto.

[0122] The output unit (150) may include a display, a speaker, etc. as a configuration for outputting various information. Specifically, the electronic device (100) may provide visual UI items constituting a conversational UI (e.g., a profile image of a conversationalist (user, chatbot, etc.), a conversation input window, a conversation message, etc.) through the display of the output unit (150). In addition, the electronic device (100) may provide information on the user's (reserved) treatment schedule through the display of the output unit (150).

[0123] Meanwhile, the various embodiments described above may be implemented by combining two or more embodiments as long as they do not conflict or contradict each other.

[0124] Meanwhile, the various embodiments described above may be implemented in a recording medium readable by a computer or similar device using software, hardware, or a combination thereof.

[0125] In terms of hardware implementation, the embodiments described in the present disclosure may be implemented using at least one of Application Specific Integrated Circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and other electrical units for performing functions.

[0126] In some cases, the embodiments described herein may be implemented within the processor itself. In a software implementation, the embodiments described herein, such as the procedures and functions described herein, may be implemented as separate software modules. Each of the software modules described above may perform one or more of the functions and operations described herein.

[0127] Meanwhile, computer instructions or computer programs for performing processing operations in electronic devices (100), user terminals (200), hospital terminals (300), etc. according to various embodiments of the present disclosure described above may be stored in a non-transitory computer-readable medium. When the computer instructions or computer programs stored in the non-transitory computer-readable medium are executed by a processor of a specific device, they cause the specific device to perform processing operations in electronic devices (100), user terminals (200), hospital terminals (300), etc. according to various embodiments described above.

[0128] A non-transitory computer-readable medium refers to a medium that permanently stores data and can be read by a device, rather than a medium that stores data for a short period of time, such as a register, cache, or memory. Specific examples of non-transitory computer-readable media include CDs, DVDs, hard disks, Blu-ray discs, USBs, memory cards, and ROMs.

[0129] Although the preferred embodiments of the present disclosure have been illustrated and described above, the present disclosure is not limited to the specific embodiments described above, and various modifications may be made by a person having ordinary skill in the art to which the present disclosure pertains without departing from the gist of the present disclosure as claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the present disclosure.

Claims

1. A method of operating an electronic device including a chatbot that performs consultation for making a hospital reservation, A step of providing a conversational UI (User Interface) for conducting a conversation with the chatbot through a user terminal; A step of updating the schedule information of the hospital by adding a treatment schedule based on the conversation between the user and the chatbot through the conversation UI; When a request for the user's medical record information is received from the hospital terminal of the hospital, a step of providing the treatment schedule together with the user's medical record information to the hospital terminal; and An operating method of an electronic device, comprising: providing a conversation between a user and the chatbot related to the procedure schedule to the hospital terminal; 2. In paragraph 1, The method of operating the above electronic device is as follows: A step of providing the conversation UI to each of a plurality of user terminals and adding a treatment schedule for each of the plurality of users through the chatbot; A step of providing information on a plurality of treatment schedules reserved for each of the plurality of users to the hospital terminal; and An operating method of an electronic device, comprising: a step of providing a conversation between a user and the chatbot related to the selected treatment schedule to the hospital terminal when at least one treatment schedule among the plurality of treatment schedules is selected by the hospital terminal; 3. In paragraph 2, The step of adding a treatment schedule for each of the above multiple users is: When a reservation for the first treatment schedule is requested based on the conversation between the first user and the chatbot, the hospital's schedule information is updated by adding the first treatment schedule. An operating method of an electronic device, wherein when a reservation for a second treatment schedule that overlaps with the first treatment schedule is requested based on a conversation between a second user and the chatbot while the first treatment schedule is added, the schedule information of the hospital is updated by adding a third treatment schedule in which the second treatment schedule is changed.

4. In paragraph 1, The above electronic device, Includes a basic chatbot for registering treatment schedules, The method of operating the above electronic device is as follows: A step of obtaining treatment menu information including types of treatments that can be reserved, work information on personnel available for each type of treatment, and time required for each type of treatment through the above hospital terminal; and An operating method of an electronic device, comprising: a step of creating a dedicated chatbot matching the hospital by tuning the basic chatbot to register at least one treatment schedule according to the treatment menu information; 5. In paragraph 1, The method of operating the above electronic device is as follows: When the above treatment schedule is completed, a step of obtaining information on the user's medical records and treatment progress through the hospital terminal; and An operating method of an electronic device, comprising: a step of updating the user's medical record information based on the medical record and the procedure progress; 6. In paragraph 1, The method of operating the above electronic device is as follows: If the user's medical record information is not already registered at the time the above-mentioned treatment schedule is added, a step of extracting at least one medical keyword from the conversation between the user and the chatbot; and An operating method of an electronic device, comprising: a step of generating medical record information of the user based on a sentence containing at least one medical keyword extracted from the conversation content.

7. In paragraph 6, The step of creating the above user's medical record information is: In the above conversation, a plurality of sentences containing at least one medical keyword are analyzed to select a main sentence representing at least one of the user's diseases, procedures, and symptoms, A method of operating an electronic device, wherein medical record information including the selected key sentences is generated and stored.

Images