Browsing support system, browsing support method, and program

Abstract

To provide a browsing support system for supporting creation of an electronic medical chart.SOLUTION: An information processor 10 provided in a browsing support system 1 includes a display part 11 for displaying an electronic medical chart creation display screen W1, and an inputting part 12 for inputting a question related to medical chart information. A medical chart management system 3 has a medical chart management part 31 for outputting creation information for creating an electronic medical chart input by an information processing terminal 10 to a RAG system 4, receiving an answer from the RAG system 4, and supporting the creation of the electronic medical chart. The RAG system 4 has a vector DB52 for storing knowledges vectorized and embedded in a vector space, and a knowledge-retrieving part 44 for retrieving the knowledges from the vector DB52 on the basis of the vectorized creation information, and outputting an answer obtained by forming the retrieved knowledges to the medical chart management part 31.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a browsing support system, a browsing support method, and a program. [Background technology]

[0002] In health insurance treatment, the calculation rules for dental diagnosis procedures and insurance points are defined by the Ministry of Health, Labor and Welfare and are revised regularly. In particular, insurance points must reflect fluctuations in the price of gold, which is used in dental fillings, etc. For this reason, they are now revised every three months (four times a year) instead of twice a year.

[0003] Doctors and medical institutions that provide medical treatment covered by insurance must provide treatment in accordance with the rules of medical treatment covered by insurance, which are published in the Official Gazette issued by the Ministry of Health, Labor and Welfare, for example.

[0004] Patent document 1 discloses a technology for improving the quality of medical data as a whole (for example, all medical data related to a certain patient) by evaluating the consistency between reference data (reference data, first medical data) and other data (target data, second medical data). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Special Publication No. 2023-504193 Summary of the Invention [Problem to be solved by the invention]

[0006] Traditionally, the writing of medical records was left to the ability of each individual. As a result, dentists who frequently had incomplete medical records experienced a lot of stress due to the constant return of records. As mentioned above, the rules for insured medical treatment are frequently revised, so not only medical records but also prescriptions must be written in accordance with the rules. Insured physicians are not only required to acquire knowledge and skills related to treatment, but also to be thoroughly familiar with the rules of insured medical treatment and to constantly update their knowledge.

[0007] However, the rules for insured medical treatment are vast and the information written is often difficult to understand. This makes it extremely difficult for insured physicians to keep up with the frequent cycle of updating their knowledge. If an insured physician makes an incorrect prescription, the prescription will be returned, and medical institutions with too many returns will be audited in the form of individual guidance. Dentists with little experience in insured medical treatment must continue practicing without being able to grasp such situations. Generally, the content taught to students at educational institutions such as dental schools mainly focuses on diagnostic and treatment methods. For this reason, dentists rarely receive sufficient training in how to write medical records and claim prescriptions at their educational institutions, and in most cases they only encounter these issues once they start working in the clinical field after graduation.

[0008] The above-mentioned Patent Document 1 describes, for example, support technology for detecting omissions in electronic medical records, but does not describe support technology for filling out electronic medical records in accordance with the rules of insurance-covered medical treatment.

[0009] The present invention has been made in view of the above circumstances, and aims to support the creation of electronic medical records. [Means for solving the problem]

[0010] The browsing support system according to the present invention comprises an information processing terminal, a medical record management system for managing electronic medical records, and an input support system connected via a network. The information processing terminal comprises a display unit for displaying an electronic medical record creation display screen having an information display area and an answer display area for displaying answers related to the content displayed in the information display area, and an input unit for inputting questions. The medical record management system comprises a creation support unit that outputs creation information for creating an electronic medical record input by the information processing terminal to the input support system, receives answers from the input support system, and supports the creation of the electronic medical record. The input support system comprises a vector database that stores knowledge that has been vectorized and embedded in a vector space, and a knowledge search unit that searches the vector database for knowledge based on the vectorized creation information and outputs answers formed from the searched knowledge to the creation support unit. [Effects of the Invention]

[0011] According to the present invention, it is possible to support the creation of electronic medical records. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a functional block diagram showing an example of the overall configuration of a browsing assistance system according to a first embodiment of the present invention. [Figure 2] 1 is a diagram showing an example of the data structure of data and information used in a medical record management system according to a first embodiment of the present invention. FIG. [Figure 3] 2 is a diagram showing an example of the data structure of a medical record DB according to the first embodiment of the present invention. FIG. [Figure 4] 1 is a block diagram showing an example of the internal configuration of a RAG system according to a first embodiment of the present invention. [Figure 5] FIG. 2 is a diagram illustrating an example of the configuration of a knowledge DB according to the first embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a vector DB according to the first embodiment of the present invention. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of a prompt DB according to the first embodiment of the present invention. [Figure 8] 1 is a block diagram showing an example of the hardware configuration of a computer according to a first embodiment of the present invention. [Figure 9] FIG. 2 is a diagram showing a first display example of an electronic medical record creation display screen according to the first embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing a second display example of the electronic medical record creation display screen according to the first embodiment of the present invention. [Figure 11] 10 is a flowchart showing an example of a knowledge addition process in the RAG system according to the first embodiment of the present invention. [Figure 12] 10 is a flowchart showing an example of a knowledge update process in the RAG system according to the first embodiment of the present invention. [Figure 13] 4 is a flowchart showing an example of a process for creating an electronic medical record according to the first embodiment of the present invention. [Figure 14] 4 is a flowchart showing an example of knowledge search processing by the RAG system according to the first embodiment of the present invention. [Figure 15] FIG. 10 is a functional configuration diagram showing an example of the overall configuration of a browsing support system according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functions or configurations are designated by the same reference numerals, and redundant description will be omitted.

[0014] [First embodiment] <Example of overall configuration of browsing support system> First, a configuration example and a processing example of a browsing support system according to the first embodiment will be described with reference to FIGS.

[0015] 1 is a functional block diagram showing an example of the overall configuration of a browsing support system 1 according to the first embodiment. Dental clinic staff who use the browsing support system 1 are assumed to be, for example, dentists, dental hygienists, reception staff, etc.

[0016] 2 is a diagram showing an example of the data structure of the data and information used in the medical record management system 3. Below, in addition to the explanation of the viewing support system 1, the data and information used in the medical record management system 3 will also be explained with reference to FIG.

[0017] The browsing support system 1 mainly comprises an information processing terminal 10 used in medical institutions such as dental clinics and medical universities, a medical receipt management system 2 operated by a service company, a medical record management system 3, and a Retrieval-Augmented Generation (RAG) system 4. The information processing terminal 10, medical receipt management system 2, and medical record management system 3 are connected via a network, and data can be sent and received safely using secure communication methods such as encryption and a VPN (Virtual Private Network). The medical receipt management system 2, medical record management system 3, and RAG system 4 are connected via the service company's internal LAN or the like.

[0018] The browsing support system 1 according to the first embodiment implements a medical record management function and an input support function using RAG in a cloud-based medical record management system 3 provided to dental clinics by a service company. Therefore, the medical records described below are "electronic medical records" that have been digitized using the medical record management function of the medical record management system 3, and these electronic medical records are insurance medical records that record the treatments given to patients and their insurance points.

[0019] The dental clinic staff accesses the medical record management system 3 by using their own information processing terminal 10 to input a user ID, password, etc. into the authentication screen of the medical record management system 3. The staff then browses the medical record DB 33 and creates an electronic medical record.

[0020] The RAG system 4 is an example of an input support system that presents answers to staff and supports their input. For example, when staff create electronic medical records, the RAG system 4 can provide input support. With the viewing support system 1 shown in Figure 1, dental clinics do not need to prepare individual servers, etc., which significantly reduces initial costs.

[0021] (Dental clinic staff) The information processing terminal 10 is an example of an information processing terminal such as a desktop PC (Personal Computer), a notebook PC, a smartphone, a tablet, etc. The information processing terminal 10 is connected to a medical receipt management system 2 and a medical record management system 3 via the Internet, and displays medical-related information including medical receipts and medical records (electronic medical records). The medical receipt management system 2 and the medical record management system 3 are examples of medical-related information management systems that manage medical-related information. The information processing terminal 10, when operated by a staff member, displays various screens provided by the medical receipt management system 2, the medical record management system 3, and the RAG system 4, and accepts various information inputs by the staff member. To this end, the information processing terminal 10 includes a display unit 11 that displays medical-related information, and an input unit 12 that creates questions to be registered in the medical-related information displayed on the display unit 11.

[0022] For example, at a dental clinic, a dentist provides dental care to a patient and inputs the details of the treatment and medical fees into the information processing terminal 10. Also, at a dental clinic, a dental hygienist may operate the information processing terminal 10 to refer to the medical records and receipts displayed on the screen. At a medical university, a professor or a medical student may operate the information processing terminal 10 to obtain necessary information.

[0023] When a staff member operates the information processing terminal 10 to access the medical receipt management system 2, a medical receipt input screen (not shown) is displayed on the web browser of the display unit 11 based on the functions provided by the medical receipt management system 2. The information processing terminal 10 can also access the medical record management system 3 and display an electronic medical record creation display screen W1 shown in Figures 9 and 10 (described later) on the web browser of the display unit 11.

[0024] In addition, the dental clinic staff operates the input unit 12 to input words and phrases into various screens displayed on the display unit 11, and create medical records and medical receipts. The insurance medical records created by the medical record creation process are electronic, so they are called "electronic medical records." The words and phrases input from the input unit 12 are sent to the medical receipt management system 2 together with information in the word and phrase input fields.

[0025] Furthermore, when the information processing terminal 10 accesses the medical record management system 3, it displays the display screen of the electronic medical record on the web browser of the display unit 11 based on the functions provided by the medical record management system 3. The electronic medical record is displayed in a fixed format that matches the layout of an actual book, allowing words on the page to be copied and pasted using the web browser or a dedicated application. In addition, dental clinic staff can switch to a reflowable display, which allows the font size to be changed to any size, or a horizontal or vertical display.

[0026] In addition, the dental clinic staff can highlight important points in the displayed electronic medical record, create indexes for pages, and convert the electronic medical record into a portable document format (PDF).The electronic medical record can be displayed on the information processing terminal 10 by turning one page at a time, or by turning multiple pages consecutively.

[0027] In addition to the "disease name" and "procedure name (or treatment name)," electronic medical records also record, for example, the patient's chief complaint (e.g., a throbbing pain in the area) and the dentist or other staff member's findings (e.g., bleeding when pressing the affected area with a finger). For example, keywords such as the patient's chief complaint and the staff member's findings are recorded as trends in the disease name in the electronic medical record.

[0028] (Receipt management system) The information entered by the dental clinic staff into the receipt input field via the information processing terminal 10 is transmitted to the receipt management system 2 as medical treatment data d1 shown in Figure 2. The receipt management system 2 includes a receipt management unit 21 and a receipt DB (Data Base) 22.

[0029] The medical receipt management unit 21 manages data related to medical treatment and data related to the issuance of medical receipts, which are input from the information processing terminal 10. The medical receipt management unit 21 outputs an input screen for data related to medical treatment to the information processing terminal 10. The medical receipt management unit 21 also outputs information to be displayed on the information processing terminal 10 (such as html (Hyper Text Markup Language) files, xml (Extensible Markup Language) files, image files, etc.). The web browser of the information processing terminal 10 displays a medical receipt entry screen. The medical receipt management unit 21 also displays a screen for entering medical treatment-related data, in addition to the electronic medical record entry screen, on the display unit 11 of the information processing terminal 10 using a program that manages the issuance of medical receipts.

[0030] Medical data d1 is input to the medical receipt management unit 21 from the information processing terminal 10. The medical data d1 is data entered in the electronic medical record and data for creating medical receipts. The medical receipt management unit 21 imports the medical data d1 from the information processing terminal 10 and stores it in the medical receipt DB 22.

[0031] The medical receipt DB 22 stores medical treatment log data and basic medical institution information shown in FIG. 2, which will be described later. The medical receipt management unit 21 creates medical receipts based on data acquired from the medical receipt DB 22. For example, the medical receipt DB 22 stores medical treatment log data and medical receipt data created for each patient and each medical procedure. Staff at the dental clinic periodically operate the information processing terminal 10 to print medical receipts. For example, while the medical receipt data read from the medical receipt management system 2 is displayed, the staff presses a print button displayed on the screen of the information processing terminal 10, thereby outputting a printed receipt. This printed receipt is submitted to an examination and processing agency (not shown).

[0032] 2, the medical data d1 stores the date and time, the user ID, and the user name. The date and time item stores the date and time when the dental clinic staff entered the receipt using the information processing terminal 10. In the item of user ID, a user ID that uniquely identifies a staff member as a user of the information processing terminal 10 is stored. The user name field stores the name of the user associated with the user ID, i.e., the name of the dental clinic staff member. The medical receipt information item stores medical receipt information entered by the user.

[0033] (Medical log data configuration) As described above, the medical receipt DB 22 of the medical receipt management system 2 stores the medical care log data shown in Fig. 2. Each item of the medical care log data includes a date and time, a medical staff ID, a patient name, and an event recorded in the medical record. The date and time item stores the date and time when the dental clinic staff filled out the electronic medical record. The medical staff ID field stores a medical staff ID assigned to identify a staff member.

[0034] The patient name field stores the patient's name. The event entry item in the medical record stores information about events entered in the electronic medical record by dental clinic staff. Events entered in the electronic medical record include the quoted content (disease name, procedure name, summary, etc.), the date and time of citation, the citation by (healthcare professional ID), and the number of citations when the staff cites information on the page or phrase that they referred to in the electronic medical record.

[0035] (Basic information on medical institutions) The medical institution basic information shown in Figure 2 is also registered in the receipt DB 22. The medical institution basic information is information that is also known by the service company. Each item of the medical institution basic information stores the name of the clinic, address, telephone number, home page URL (Uniform Resource Locator), and medical staff information.

[0036] The clinic name field stores the name of the dental clinic (or hospital). The address item stores the address of the dental clinic (or hospital). The telephone number field stores the telephone number of the dental clinic (or hospital). The item "Website URL" stores the URL of the website managed by the dental clinic (or hospital). The medical staff information item stores information about medical staff working at the dental clinic (or hospital). The medical staff information includes, for example, information about the university from which the medical staff graduated.

[0037] (service company) The service company not only manages the entire viewing support system 1, but also provides dental clinic staff with a service that supports the input of information to be recorded in the electronic medical record using the medical record management system 3. Typically, staff who can view the electronic medical record include, for example, other staff at the dental clinic where the staff member who created the electronic medical record works.

[0038] The medical record management system 3 displays the electronic medical record read from the medical record DB 33 on the display unit 11 of the information processing terminal 10 when the dental clinic staff operates the information processing terminal 10. The dental clinic staff operates the information processing terminal 10 connected to the medical record management system 3 to open the electronic medical record at any page, refer to the page corresponding to the treatment content, and create the patient's electronic medical record or medical receipt. The dental clinic staff can also copy and paste selected words from the electronic medical record into the receipt input field, or enter comments in the input field.

[0039] The medical record management system 3 includes a medical record management unit 31, a reference management unit 32, a medical record DB 33, and a reference log DB . The medical record management unit 31 manages electronic medical record information. The medical record management unit 31 also outputs creation information for creating medical-related information, which is input by the information processing terminal 10, to the RAG system 4. The medical record management unit 31 then receives a response from the RAG system 4 and supports the creation of medical-related information. In other words, the medical record management unit 31 can be said to be an example of a creation support unit that supports staff in creating medical-related information.

[0040] The creation information for creating medical-related information includes questions to be entered in the display area of ​​the medical-related information creation display screen (see Figures 9 and 10 described below) used for creation of the medical-related information. This creation information also includes information about the items selected by the dental clinic staff on the medical-related information creation display screen. For example, questions asked by staff when creating electronic medical records or medical receipts, instructions for creating summary documents, etc., are examples of created information. This created information includes at least one of text, audio, and images. Responses also include summary documents and information on the source of the reference information summarized by LLM45 (e.g., page numbers, chapter titles, etc.).

[0041] The medical record management unit 31 accepts input to the electronic medical record by dental clinic staff and outputs a screen displaying the electronic medical record to the display unit 11 of the information processing terminal 10. The medical record management unit 31 manages the electronic medical records whose creation is supported by the RAG system 4. The electronic medical record is generated based on information obtained from the RAG system 4 when the knowledge search unit 44 inputs creation information (prompts, described later) into the LLM 45.

[0042] The RAG system 4 reads past electronic medical records, official gazettes, etc., and performs embedding processing to map vectorized text and images into a vector space. The RAG system 4 also uses large language models (LLMs) to output information appropriate for the input content. A detailed configuration example of the RAG system 4 is shown in Figure 4, which will be described later, so only a brief explanation will be given here.

[0043] The RAG system 4 includes an LLM 45 (an example of a large-scale language model) shown in Figure 4 (described later). The LLM 45 may be provided by a service other than the service provider. The LLM 45 is a type of text generation AI (artificial intelligence) and is a language model trained on a vast amount of text data. The LLM 45 is capable of performing advanced natural language processing tasks (text generation, translation, summarization, question answering, etc.). Furthermore, the LLM 45 utilizes the Transformer mechanism to output appropriate answers based on information (e.g., questions) entered by dental clinic staff. The information may be text explicitly entered by staff, or text or images automatically extracted from information displayed on the screen.

[0044] The reference management unit 32 collects data such as reference log data d2 (see FIG. 2) from the reference log DB 34 in accordance with commands received from the information processing terminal 10, and passes it to the receipt DB 22 of the receipt management system 2. The receipt management unit 21 manages receipt data stored in the receipt DB 22 for each dental clinic or each dental clinic staff member.

[0045] 2 includes information on the reference history of electronic medical records that dental clinic staff referred to when creating electronic medical records or inputting medical receipts by operating the information processing terminal 10. The reference log data d2 is stored in the reference log DB 34 of the medical record management system 3.

[0046] The reference log data d2 is data that stores the type of electronic medical record that the staff member referenced, the version of the electronic medical record (such as the creation date), the time the electronic medical record was left, etc. The reference management unit 32 reads out the version of the electronic medical record specified by the input unit 12 from the medical record DB 33 and displays it on the display unit 11 of the information processing terminal 10. In addition, the operations that the dental clinic staff performed while referring to the electronic medical record when entering the prescription (for example, copying and pasting specific items) are also stored in the reference log DB 34 as reference log data d2.

[0047] (Reference log data configuration) The reference log DB 34 stores the reference log data d2 shown in FIG. The reference log data d2 stores the medical record ID, book title, version, index, page information, and reference page. In the item of medical record ID, a medical record ID that uniquely identifies the electronic medical record being viewed on the information processing terminal 10 is stored. The book name field stores the name of the electronic medical record linked to the medical record ID as the book name. The version item stores the version of the electronic medical record (date of creation, etc.). The page information item stores page information such as the page number of the electronic medical record.

[0048] The reference log DB 34 may also store the receipt ID and return information indicated by the dashed dotted line as reference log data d2. The Receipt ID field stores the receipt ID used to identify the receipt submitted to the review and processing organization. The receipt ID is a unique identification assigned to each receipt when it is created by staff. In the items of the return information, a return flag indicating whether the receipt submitted to the examination processing institution has been returned, and return information including the phrases and locations where corrections were pointed out by the examination processing institution at the time of return are stored.

[0049] Figure 3 is a diagram showing an example of the data structure of the medical record DB 33. The medical record DB 33 has items for patient ID, book ID, date, body part, disease name, and treatment. In the patient ID item, a patient ID that uniquely identifies the patient is stored. In the book ID item, a book ID that uniquely identifies the bookified electronic medical record is stored. In the date item, the creation date or update date of the electronic medical record is stored.

[0050] In the body part item, information on the treated body part is stored. In the disease name item, information on the patient's disease name is stored. In the treatment item, information on the treatment performed on the patient is stored.

[0051] For a first-time visit patient, since a new electronic medical record is created, the creation date of the electronic medical record is stored in the date item. For a follow-up visit patient, since it is added to the existing patient ID's electronic medical record, a new record is added to the medical record DB 33, and the follow-up treatment details are stored in that record.

[0052] <Example of the internal configuration of the RAG system> Figure 4 is a block diagram showing an example of the internal configuration of the RAG system 4. Here, the cooperation between the medical record management system 3 and the RAG system 4 will be described.

[0053] First, let us explain RAG. RAG is a technology that combines information retrieval capabilities with a generative model (usually a text generation model), and is primarily composed of a search engine (Retriever) and a generative model (Generator). A search engine has the function of searching for relevant documents and information from a database based on a user's input (query). To do this, the search engine uses an embedding model that embeds the user's query and documents in the database into a vector space to calculate similarity and search for documents related to the query. On the other hand, a generative model generates responses and text for the user based on the information retrieved by the search engine. To do this, the generative model generates responses by converting the contents of documents retrieved by the search engine into language expressions that are easy for humans to understand.

[0054] The RAG system 4 includes a knowledge upload unit 41, a knowledge update unit 42, an embedding unit 43, a knowledge search unit 44, an LLM 45, a knowledge database (knowledge DB 51), a vector database (vector DB 52), and a prompt database (prompt DB 53).

[0055] A knowledge upload unit 41, a knowledge update unit 42, and a knowledge search unit 44 are connected to the medical record management system 3. The knowledge upload unit 41 is connected to the knowledge DB 51 and uploads knowledge acquired from the medical record management system 3 to the knowledge DB 51. The knowledge includes, for example, official gazettes published by the Ministry of Health, Labor and Welfare, guidelines for filling out medical insurance claims, past electronic medical records, etc. The knowledge uploaded by the knowledge upload unit 41 is stored in the knowledge DB 51.

[0056] The knowledge update unit 42 is connected to the embedding unit 43 and the knowledge DB 51. The knowledge update unit 42 updates the knowledge stored in the knowledge DB 51. The knowledge update unit 42 then acquires, from the knowledge DB 51, knowledge that has been instructed to be updated by the medical record management system 3, and outputs the acquired knowledge to the embedding unit 43.

[0057] The embedding unit 43 uses the embedding model to vectorize the knowledge input from the knowledge update unit 42 and embed it in a high-dimensional vector space. The knowledge embedding process uses a technique for mapping data such as text and images into a vector space. The embedding unit 43 performs tokenization to divide the knowledge into tokens, then vectorizes the tokens and generates a vector representation of the entire query.

[0058] A vector representation of the entire query is obtained by integrating token vectors in the query using an appropriate method (e.g., average pooling, max pooling, etc.). Through the embedding process in the embedding unit 43, words, sentences, and entire documents of the text are converted into numerical vectors, and semantically similar words and documents are placed close to each other in the vector space. Using these numerical vectors makes it easier to perform machine learning tasks such as calculating the similarity between different texts and clustering. The embedding unit 43 then stores the vectorized knowledge in the vector DB 52.

[0059] The vector DB 52 stores knowledge that has been vectorized and embedded in a vector space. For this reason, the vector DB 52 is constructed as a database specialized for vector search. The vector DB 52 stores chunks (e.g., text) that are obtained by dividing a file stored in the knowledge DB 51 into multiple chunks, as well as information about the chunks expressed as vectors.

[0060] The text embedded in the vector space is stored in the vector DB 52, for example, in matrix format. Each row of the matrix represents an individual text vector, and the columns represent the dimension of the vector. The vector may also be stored as a numerical array of floating-point numbers or in binary format. Searchability is improved by storing the vector in the vector DB 52 together with the text corresponding to the vector itself, the document ID of the document from which the text was written, the publication date and time, etc.

[0061] The knowledge search unit 44 is connected to the medical record management system 3, the embedding unit 43, the LLM 45, the vector DB 52, and the prompt DB 53. The knowledge search unit 44 searches the vector DB 52 for knowledge based on the vectorized creation information, and outputs a response formed from the searched knowledge to the medical record management unit 31.

[0062] When the knowledge search unit 44 receives a question (query) input from the medical record management system 3, it tokenizes the question by dividing it into tokens, and then vectorizes the tokens to vectorize the question.The knowledge search unit 44 then extracts vectorized knowledge based on the similarity between the vectorized knowledge stored in the vector DB 52 and the vectorized creation information (query vector).At this time, the knowledge search unit 44 extracts one record stored in the vector DB 52.

[0063] In a knowledge search, the knowledge search unit 44 calculates the similarity between a query vector and each vector in the database. Vector similarity can be calculated using, for example, cosine similarity or Euclidean distance. Cosine similarity is a method of calculating the cosine of the angle between two vectors, and its value ranges from -1 to 1. The closer the value is to 1, the more similar the vectors are determined to be. Euclidean distance is a method of calculating the linear distance between two vectors, and the smaller the value, the more similar the vectors are determined to be.

[0064] The embedding unit 43 embeds the question text into a vector space and searches the vector DB 52 for a vector that answers the question. The embedding unit 43 then determines the vector with the highest similarity as the answer with the highest confidence. The embedding unit 43 returns the text corresponding to the vector searched for in the vector DB 52 to the knowledge search unit 44 as the search result.

[0065] The knowledge search unit 44 also outputs the text of the knowledge found by the vector search to the LLM 45. The LLM 45 receives the text of the knowledge input from the knowledge search unit 44 and a question (prompt) composed of normal characters. The LLM 45 then generates natural sentences based on the prompt and can generate an answer based on the prompt. The LLM 45 also reads reference information in advance and summarizes the reference information based on prompts consisting of text or images. For example, the LLM 45 can summarize long texts contained in previously read reference information such as official gazettes and information on the Ministry of Health, Labor and Welfare website, and extract important information.

[0066] The LLM 45 can also translate text from one language into another and categorize text. By using the LLM 45, the RAG system 4 can utilize the text generation capabilities of the LLM 45 to return context-appropriate responses to staff based on the retrieved information. This allows the RAG system 4 to provide interactive functionality to the medical record management system 3. The knowledge search unit 44 can also output summary documents summarized by the LLM 45 to the medical record management system 3.

[0067] The entity that selects a prompt from the prompt DB 53 can be one of the first to third forms described below. In the first mode, the knowledge search unit 44 specifies a fixed prompt ID, and a prompt corresponding to the specified prompt ID is obtained from the prompt DB 53 and executed.

[0068] The second form is a derivative of the first form, in which, for example, the knowledge search unit 44 displays a list of prompts acquired from the prompt DB 53 on the screen, allowing the dental clinic staff to select any prompt.

[0069] In the third configuration, the LLM 45 and the prompt DB 53 are connected as shown by the dashed line in the figure. In other words, in this third configuration, the LLM 45 directly references the prompt DB 53. In this third configuration, dental clinic staff search for the most appropriate prompt to process the input question. The LLM 45 then uses the searched prompt to perform processing such as creating a summary.

[0070] Next, examples of the configurations of the knowledge DB 51, the vector DB 52, and the prompt DB 53 will be described with reference to FIGS. 5 is a diagram showing an example of the configuration (data structure) of the knowledge DB 51. The knowledge DB 51 has the following items: document ID, file name, file type, and BLOB (Binary Large Object). The document ID field stores a document ID that identifies the knowledge as a document. The document ID includes various printed information that can be referenced when creating an electronic medical record.

[0071] The file name item includes the file names of the various printed materials mentioned above. For example, PDF format medical record case collections, insurance revision collections, memos, etc. It also includes file names of files saved in text format, document file format, and presentation file format. The file type item includes the file type (for example, extension) of the file of each type of print material. The BLOB item stores data that has been compiled from a file, i.e., BLOB data, which includes text data or binary data such as image data.

[0072] 6 is a diagram showing an example of the configuration (data structure) of the vector DB 52. The vector DB 52 has the following items: document ID, chunk ID, text, vector, file name, character position, and page. The document ID field stores a document ID, which is the same as the document ID stored in the knowledge DB 51. The chunk ID item stores chunk IDs that identify chunks obtained by dividing a document into a specified number of characters. Multiple chunk IDs may be included for the same document ID. For example, a document with document ID "1" may contain chunk IDs "1" to "4."

[0073] Text items store text that has been split into chunks from a document. A chunk is, for example, a group of 500 characters, and is automatically split from the original document. However, chunks identified by consecutive chunk IDs are likely to lose context. For this reason, consecutive chunks are split from the original document so that some characters overlap each other.

[0074] For example, the chunk with chunk ID "1" is the text from characters 0 to 499 of "Medical Record Case Collection," and the chunk with chunk ID "2" is the text from characters 449 to 948, where splitting begins 50 characters back from the end character position of the chunk with chunk ID "1." To clarify the context, the segmentation start character position for the next chunk may be, for example, the character string from the segmentation end character position of the previous chunk segmentation up to the first period, or the heading and main text may be segmented into a single chunk.

[0075] The vector field stores the vector calculated for each chunk. Based on the characters contained in the chunk, it is tokenized into the smallest unit of meaning, and the tokens are embedded in a vector space to calculate a numeric vector for the token. The chunk vector calculated by combining the numeric vectors of each token is stored in the vector field. This process results in a vector that retains the meaning of each chunk in a high-dimensional vector space.

[0076] The file name item stores the file name of the file that stores the text. The character position field stores the start and end character positions of the chunks split from the original document. For example, the character positions of a chunk with a chunk ID of "1" are "0" as the start character position and "499" as the end character position. The page item stores the number of pages in the file that contained the chunk.

[0077] 7 is a diagram showing an example of the configuration (data structure) of the prompt DB 53. The prompt DB 53 has items such as ID and prompt.

[0078] The ID item stores a prompt ID that identifies the prompt. The prompt item stores the prompt to be entered into LLM45. A prompt is a command that dental clinic staff enters into the RAG system 4 through the medical record management system 3. For example, the prompt for ID1 is as follows. "You" in the prompt refers to LLM45. "You are a Japanese AI assistant for RAG, and will converse in a friendly tone. The following knowledge has been found in response to the user's question. {"Text": (0 to 499th characters of "Case Study")} Please explain to the user that you have found the above knowledge and provide a summary of it."

[0079] <Example of hardware configuration of information processing terminal 10 and each server> Next, the hardware configuration of the computer 100 that constitutes the information processing terminal 10 of the browsing support system 1, the medical receipt management system 2, the medical record management system 3, and the RAG system 4 will be described. FIG. 8 is a block diagram showing an example of the hardware configuration of the computer 100. As shown in FIG.

[0080] The computer 100 is an example of hardware used as a computer that can operate as the information processing terminal 10, the medical receipt management system 2, the medical record management system 3, and the RAG system 4 according to this embodiment. The computer 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103, each connected to a bus 104. The computer 100 further includes a display device 105, an input device 106, a non-volatile storage 107, and a network interface 108.

[0081] The CPU 101 reads out the program code of the software that realizes each function according to this embodiment from the ROM 102, loads it into the RAM 103, and executes it. Variables, parameters, etc. that arise during the calculation processing of the CPU 101 are temporarily written to the RAM 103, and these variables, parameters, etc. are read out by the CPU 101 as appropriate. However, an MPU (Micro Processing Unit) may be used instead of the CPU 101. Each function of the receipt management system 2, the medical record management system 3, and the RAG system 4 is realized by the operation of the CPU 101.

[0082] The display device 105 is, for example, a liquid crystal display monitor, and displays the results of processing performed by the computer 100 to the staff. The input device 106 is, for example, a keyboard, a mouse, etc., and allows the staff to input predetermined operations and give instructions. The functions of the display unit 11 and input unit 12 of the information processing terminal 10 are realized by the display device 105 and the input device 106. In addition, the functions of the display unit and input unit of a PC (not shown) connected to the medical record management system 3 are also realized by the display device 105 and the input device 106. The RAG system 4 does not need to be equipped with the display device 105 and the input device 106.

[0083] The nonvolatile storage 107 may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, or a nonvolatile memory. In addition to an operating system (OS) and various parameters, the nonvolatile storage 107 also stores programs for operating the computer 100.

[0084] The ROM 102 and the non-volatile storage 107 store programs, data, etc. necessary for the CPU 101 to operate, and are used as an example of a computer-readable non-transitory storage medium that stores programs executed by the calculator 100. Data of the receipt management system 2, the medical record management system 3, and the RAG system 4 is stored in the non-volatile storage 107.

[0085] The network interface 108 may be, for example, a network interface card (NIC), and various data can be transmitted and received between devices via a LAN, dedicated line, or the like connected to a terminal of the NIC.

[0086] [Screen display example] Next, examples of screens displayed on the information processing terminal 10 will be described with reference to Fig. 9 and Fig. 10. The following screens are all displayed on a general-purpose web browser installed on the information processing terminal 10.

[0087] <First display example of the electronic medical record creation display screen> 9 is a diagram showing a first display example of the electronic medical record creation display screen W1. The display function of the electronic medical record creation display screen W1 is realized by the medical record management unit 31. The electronic medical record creation display screen W1 is used in a medical record management system 3 equipped with a chat-type RAG. This electronic medical record creation display screen W1 has an oral cavity information display area W1a, a medical record information display area W1b, and a chatbot display area W1d.

[0088] The oral cavity information display area W1a displays a schematic diagram of the patient's oral cavity, which shows the arrangement and condition of the patient's teeth. The medical record information display area W1b displays the contents of the electronic medical record as medical record information. The medical record information includes the consultation date and the details of the treatment given to the patient. The medical record information display area W1b also displays a PDF button W1c.

[0089] The dental clinic staff inputs an instruction to convert the medical record information into a PDF by pressing the PDF button W1c. The PDF medical record information is uploaded to the knowledge DB 51 by the knowledge upload unit 41 and vectorized by the embedding unit 43. The vectorized medical record information is then stored in the vector DB 52. This makes it possible to perform knowledge searches based on past medical record information.

[0090] The chatbot display area W1d displays an answer chat represented by an image of a robot, and a question chat where staff members input questions. Initially, the answer chat displays "Is there something I can help you with?" When a staff member inputs "What dental prostheses are covered by the crown and bridge maintenance fee?" into the question chat, the answer chat displays "We will search for a relevant item in our knowledge."

[0091] Furthermore, when a staff member clicks on the "Crown and Bridge Maintenance Fee (Br5 teeth or less)" item displayed in the medical record information display area W1b, the question chat may automatically be configured to input "What crown prostheses are subject to the crown and bridge maintenance fee?". The answer chat then displays a summary categorized as follows: "Prostheses subject to crown and bridge maintenance include the following: 1. ..., 2. ..." This answer is an explanation summarized by the LLM 45 from the results of a search in the vector DB 52 based on the question vectorized by the embedding unit 43.

[0092] In addition, the reply chat will display the file name that is the basis for the reply and the relevant section within the file. For example, the reply chat will display both the content and the page number, such as "The CAD / CAM crowns listed in Fiscal Year 2024 Insurance Revision.pdf M015-2 are... Page 25." The basis for the answer may be a file name or a link including a URL that allows access to the file. In addition, multiple answers may be displayed in the answer chat in order of the degree of certainty of the answer, and staff members may select any answer.

[0093] As shown at the bottom of the chatbot display area W1d, information entered by the staff via keyboard or voice, such as "What crown prostheses are covered by the crown and bridge maintenance fee?" may be displayed. Alternatively, only "Cluburi," the abbreviation for "crown and bridge maintenance fee," may be entered and displayed in the question chat. Even with such a question, when the staff member presses the send button, the knowledge search process shown in Figures 13 and 14, which will be described later, is executed. The question text is then sent to the RAG system 4 via the medical record management system 3, and an answer can be obtained.

[0094] <Second display example of the electronic medical record creation display screen> 10 is a diagram showing a first display example of the electronic medical record creation display screen W2. The display function of the electronic medical record creation display screen W2 is realized by the medical record management unit 31. The electronic medical record creation display screen W2 is used in a medical record management system 3 equipped with a RAG that automatically detects input. This electronic medical record creation display screen W2 has an input information display area W2a and a knowledge display area W2b.

[0095] The input information display area W2a displays the items to be input into the electronic medical record. For example, if a staff member selects the item "Crown and bridge maintenance fee (Br5 teeth or less)," this item is highlighted.

[0096] The knowledge display area W2b displays the results of an automatic search for knowledge related to the item selected in the input information display area W2a. For example, the procedure name, disease name, or comment selected by the staff member is automatically adopted as a search word by the medical record management system 3. Knowledge related to this search word is always displayed in the knowledge display area W2b. This reduces the time and effort required for staff to conduct their own research, while still allowing them to focus on providing medical care and communicating with patients.

[0097] Note that the search target of the RAG system 4 is not limited to text. For example, the medical record management system 3 periodically takes screenshots of the input information display area W2a. By inputting the captured image into the multimodal RAG system 4, the medical record management system 3 can search for information corresponding to the captured image and display it in the knowledge display area W2b. In this case, information related to the knowledge displayed in the input information display area W2a is always displayed in the knowledge display area W2b.

[0098] [Example of operation of the medical record management system and RAG system] Next, an overview of an example of the operation of the medical record management system 3 and RAG system 4 according to this embodiment will be described with reference to Figures 11 to 14. In the following description, reference will be made as appropriate to the medical record management system 3 and RAG system 4 shown in Figure 1 and the internal configuration example of the RAG system 4 shown in Figure 4.

[0099] First, an example of the process of adding and updating knowledge in the RAG system 4 will be described with reference to Figures 11 and 12. These processes are performed before the service company provides the service to the dental clinic, but can also be performed at any time after the service is provided. Furthermore, these processes can be performed not only by the service company staff but also by staff at the dental clinic using the medical record management system 3.

[0100] FIG. 11 is a flowchart showing an example of a knowledge addition process in the RAG system 4. First, the knowledge upload unit 41 selects (S1) a file to be uploaded to the knowledge DB 51. Next, the knowledge upload unit 41 checks whether a file with the same file name as the selected file is stored in the knowledge DB 51 (S2).

[0101] If a file with the same file name is not stored in the knowledge DB 51 (NO in S2), the knowledge upload unit 41 uploads the selected file to the knowledge DB 51 (S3), and ends this process.

[0102] On the other hand, if a file with the same file name is stored in the knowledge DB 51 (YES in S2), the knowledge upload unit 41 ends this process without adding the knowledge. However, if the file has the same file name but a different version, the knowledge upload unit 41 may upload the different version of the file to the knowledge DB 51 and then end this process.

[0103] FIG. 12 is a flowchart showing an example of a knowledge update process in the RAG system 4. First, the knowledge update unit 42 acquires data including the knowledge to be updated from the knowledge DB 51 (S11). Next, the embedding unit 43 vectorizes the data using the embedding model (S12). This vectorization process includes, for example, dividing the document into chunks, tokenizing the words and phrases in the chunks, and vectorizing the tokens.

[0104] Next, the embedding unit 43 stores the vectorized data in the vector DB 52 (S13). Then, the knowledge update unit 42 determines whether or not the vectorized knowledge stored in the vector DB 52 has been updated with all the data acquired from the knowledge DB 51 (S14).

[0105] If the vectorized knowledge has not been updated using all the data (NO in S14), the process returns to step S11 and repeats. On the other hand, if the vectorized knowledge has been updated using all the data (YES in S14), the process ends.

[0106] Next, an example of the processing of the viewing support system 1 when a staff member creates an electronic medical record will be described with reference to FIGS. 13 is a flowchart showing an example of the process of creating an electronic medical record. Operations on the information processing terminal 10 are performed via a web screen displayed when a staff member accesses the medical record management system 3. Therefore, each operation on the information processing terminal 10 is executed by each functional unit of the medical record management system 3.

[0107] When a dental clinic staff member starts creating an electronic medical record by operating the input unit 12 of the information processing terminal 10, the medical record management unit 31 determines whether the created electronic medical record is stored in the medical record DB 33 (S21). This determination is made based on whether the patient is visiting for the first time or a repeat visit. The dental clinic staff member inputs the patient number written on the patient's patient card into the information processing terminal 10 to check whether the patient number is registered in the medical record DB 33.

[0108] If the created electronic medical record is stored in the medical record DB 33 (YES in S21), the medical record management unit 31 acquires the created electronic medical record from the medical record DB 33 (S22) and displays it on the display unit 11. This electronic medical record is displayed on the electronic medical record creation display screen W1 (see FIG. 9) or W2 (see FIG. 10).

[0109] On the other hand, if the created electronic medical record is not stored in the medical record DB 33 in step S21 (NO in S21), a new electronic medical record is created (S23).

[0110] The dental clinic staff inputs the necessary information while checking the electronic medical record. If there is an item that the staff is unsure about, they select that item and input a question into the question chat. This selected item is input as a prompt (text or image) into the medical record management system 3 (S24). The medical record management unit 31 outputs the input prompt to the RAG system 4 (S25). The RAG system 4 performs a knowledge search process based on the prompt input from the medical record management system 3 (S26).

[0111] Here, the knowledge search process performed by the RAG system 4 will be described with reference to Fig. 14. Fig. 14 is a flowchart showing an example of the knowledge search process performed by the RAG system 4. 4 receives a prompt input from the medical record management system 3, the knowledge search unit 44 inputs the prompt as a search query to the embedding unit 43 (S31). As described above, the prompt includes text or an image.

[0112] Next, the embedding unit 43 vectorizes the search query using the embedding model (S32), and then acquires knowledge that has a high similarity to the vectorized search query from the vector DB 52 (S33).

[0113] Next, the embedding unit 43 determines whether or not knowledge has been acquired from the vector DB 52 (S34). If knowledge has not been acquired from the vector DB 52 in step S34 (NO in S34), the embedding unit 43 ends this process and proceeds to step S27 in FIG.

[0114] On the other hand, if knowledge can be acquired from the vector DB 52 in step S34 (YES in S34), the embedding unit 43 passes the knowledge to the LLM 45. The LLM 45 acquires an arbitrary prompt from the prompt DB 53 based on the knowledge (S35).

[0115] Next, the search query, knowledge, and prompt are input to the LLM 45 (S36). Then, the LLM 45 generates an explanation of the search results and a summary of the knowledge in accordance with the prompt (S37), and the process proceeds to step S27 in FIG.

[0116] Returning to the explanation of FIG. The medical record management unit 31 acquires an answer including an explanation of the search results and a summary of the knowledge from the RAG system 4 (S27). The medical record management unit 31 displays the acquired answer on the screens W1 and W2. Next, the medical record management unit 31 reflects the answer in the electronic medical record and saves the electronic medical record in the medical record DB 33 (S28), and this process ends.

[0117] The dental clinic staff may use voice input instead of operating the input unit 12 to write a prompt. For example, the input unit 12 may capture a conversation between the staff and the patient via a microphone, convert the voice input into text, and output the text information as a prompt to the RAG system 4. By using voice input, the staff does not need to hold the information processing terminal 10 and can concentrate on dealing with the patient.

[0118] In the browsing support system 1 according to the first embodiment described above, staff can use the medical receipt management function and the medical record management function simply by preparing the information processing terminal 10, without having to prepare a dedicated server. The medical record management function incorporates a response support function using the RAG system 4, and each time a staff member makes an input when creating an electronic medical record, information related to this input is displayed. Therefore, dental clinic staff can create an electronic medical record in the correct format while referring to the information displayed on the display unit 11.

[0119] In addition, when dental clinic staff enter a question when creating an electronic medical record, the answer to that question is displayed. The answer is a summary of the original long document (reference information) in LLM45, making it easy for staff to understand. In addition, the reference information of the document that is the source of the answer is also displayed, so when staff want to check more detailed information, they can immediately access the reference information of the document.

[0120] In addition, the service company manages the medical record management system 3, so there is no need to install a server or the like at the dental clinic. This reduces the introduction costs and ongoing costs of the server or the like required for introducing the browsing support system 1. In addition, the information processing terminal 10 does not need to be installed in a specific location.

[0121] For example, dental clinic staff can access the medical receipt management system 2 and the medical record management system 3 via the Internet using an information processing terminal 10 (for example, a notebook PC or tablet terminal) that they have taken outside the dental clinic. This makes it easy for dental clinic staff to check the input status of the electronic medical records and medical receipts, and also makes it easy to check the contents of the electronic medical records.

[0122] Answers to questions entered by dental clinic staff are generated using AI technologies such as LLM45, and include, for example, explanations of search results and knowledge summaries, making it easier for staff to understand complex documents.

[0123] Furthermore, when a new document is published, the knowledge is uploaded. Furthermore, when a document is revised, the knowledge is also revised. Therefore, the RAG system 4 can output answers based on the latest knowledge to the medical record management system 3, and the answers can be reflected in the electronic medical records.

[0124] In the first embodiment described above, the link between the medical record management system 3 and the RAG system 4 was described, but the medical receipt management system 2 and the RAG system 4 are also linked in a similar manner. For example, a medical receipt creation display screen similar to screens W1 and W2 shown in FIGS. 9 and 10 is displayed on the display unit 11. Therefore, when a staff member specifies an unknown item on the screen displayed when using the medical receipt management system 2, the answer obtained from the RAG system 4 is displayed on the display unit 11. In addition, a summary of the appropriate content is displayed from a document containing the medical receipt entry guidelines. This ensures that medical receipts created by staff members are accurate, reducing the possibility of them being returned.

[0125] Furthermore, the knowledge upload unit 41 and the knowledge DB 51 may be removed from the RAG system 4 according to the first embodiment. In this case, the document (knowledge) sent to the RAG system 4 by the medical record management unit 31 of the medical record system 3 is sent to the embedding unit 43 by the knowledge update unit 42. The embedding unit 43 vectorizes the document (knowledge) and stores the vectorized knowledge in the vector DB 52. Even with this configuration, the knowledge search unit 44 can display the chunked text in the vector DB 52 on the screens W1 and W2, allowing the staff member to check the chunked text.

[0126] [Second embodiment] Next, an example of the configuration of a browsing support system according to a second embodiment of the present invention will be described with reference to FIG. 15 is a functional configuration diagram showing an example of the overall configuration of a viewing support system 1A according to the second embodiment. The viewing support system 1A is capable of generating electronic medical records and providing answer support using RAG even in an offline state.

[0127] The browsing support system 1A includes an information processing terminal 10 and a medical record computer 6 for each dental clinic. The medical record computer 6 includes a medical record management system 60 and an RAG system 70. The medical record management system 60 includes a medical record management unit 61, a reference management unit 62, a medical record DB 63, a reference log DB 64, and a medical receipt DB 65.

[0128] The functions of the medical record management unit 61 and the reference management unit 62 are similar to those of the medical record management unit 31 and the reference management unit 32 according to the first embodiment. Therefore, the medical record management unit 61 can generate and manage electronic medical records offline.

[0129] The medical record DB 63 stores information of the electronic medical record created by the medical record computer 6. Since the information of the electronic medical record includes personal information of the patient, it remains within the medical record computer 6. Medical treatment data d1 is sent from the medical record computer 6 to the medical receipt management system 2, and the medical treatment data d1 is registered in the medical receipt DB 22. In addition, reference log data d2 is sent from the medical record computer 6 to the medical record management system 3, and the reference log data d2 is registered in the reference log DB 34.

[0130] The data configurations of the medical record DB 63, the reference log DB 64, and the receipt DB 65 are the same as the data configurations of the medical record DB 33, the reference log DB 34, and the receipt DB 22. The inside of the RAG system 70 is configured in the same way as the RAG system 4 shown in Fig. 4. The RAG system 70 is installed in a dental clinic, and there is no need to output data such as personal information outside the dental clinic.

[0131] The data in each DB constructed in the medical record computer 6 is limited to information that can be referenced by staff. Even if the medical record computer 6 is offline, staff can operate the information processing terminal 10 to view the information recorded in each DB in the medical record computer 6. Furthermore, of the information written in each DB of the medical record computer 6, information other than the medical record DB 63 is periodically synchronized with each DB provided in the medical receipt management system 2 and the medical record management system 3 and used.

[0132] In the browsing support system 1A according to the second embodiment described above, the information in each DB of the medical record computer 6 is synchronized with the information in each DB of the medical receipt management system 2 and the medical record management system 3. Therefore, even if the medical record computer 6 goes offline, the staff can check the information recorded in each DB of the medical record computer 6.

[0133] [Variations] In the above-described embodiments, the creation of medical records (electronic medical records) and prescriptions in dental treatment has been described, but the present invention can also be applied when creating medical records (electronic medical records) and prescriptions for treatment by doctors, nurses, physical therapists, chiropractors, etc. For example, not only in dentistry but also in medical, pharmaceutical, and veterinary care departments, staff from each department can check the electronic medical records.

[0134] LLM45 may also provide data summarizing the electronic medical record to patients recorded in the electronic medical record. Patients can check the details of their treatment by checking the summarized data. Furthermore, if a patient visits another dental clinic, they can bring the summarized data with them to continue receiving treatment from their previous dental clinic.

[0135] The present invention is not limited to the above-described embodiments, and it goes without saying that various other applications and modifications are possible without departing from the gist of the present invention as set forth in the claims. For example, the above-described embodiments have described the configuration of the device and system in detail and specifically in order to clearly explain the present invention, and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of the embodiments described here with the configuration of other embodiments, and it is also possible to add the configuration of one embodiment to the configuration of another embodiment. Furthermore, it is also possible to add, delete, or replace part of the configuration of each embodiment with other configurations. In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0136] 1, 1A...viewing support system, 2...receipt management system, 3...medical record management system, 4...RAG system, 10...information processing terminal, 11...display unit, 12...input unit, 21...receipt management unit, 31...medical record management unit, 41...knowledge upload unit, 42...knowledge update unit, 43...embedding unit, 44...knowledge search unit, 45...LLM

Claims

1. A browsing support system in which an information processing terminal, a medical record management system that manages electronic medical records, and an input support system are connected via a network, The information processing terminal a display unit having an information display area and an answer display area for displaying answers related to the content displayed in the information display area, and displaying an electronic medical record creation display screen used for creating the electronic medical record; an input unit for inputting a question, The medical record management system includes: a creation support unit that outputs creation information for creating the electronic medical record, which is input by the information processing terminal, to the input support system, receives the response from the input support system, and supports creation of the electronic medical record; The input support system includes: a vector database in which vectorized knowledge embedded in a vector space is stored; a knowledge search unit that searches the vector database for the knowledge based on the vectorized creation information, and outputs the answer formed from the searched knowledge to the creation support unit. Browsing assistance system.

2. the information display area displays medical record information of the electronic medical record; the answer display area displays the questions related to the medical record information and the answers to the questions; The created information is information included in the question or an item selected from the information display area. The browsing support system according to claim 1 .

3. The answer includes at least one of the following: the name of the book or file that is the basis of the answer; a portion of the content described in the book or file that is the basis of the answer; a description page that describes the basis of the answer; and link information that includes a URL (Uniform Resource Locator) that can access the file that is the basis of the answer. The browsing support system according to claim 1 .

4. The display unit displays a plurality of answers selectable by the input unit in descending order of the certainty of the answer. The browsing support system according to claim 1 .

5. The electronic medical record creation display screen has an oral cavity information display area for displaying oral cavity information. The browsing support system according to claim 1 .

6. the information display area displays input items to be input into the electronic medical record; the answer display area displays, as the answer, the knowledge related to the input item selected from the information display area by the input unit; The created information is information included in the input item selected from the information display area. The browsing support system according to claim 1 .

7. The knowledge searched based on a screenshot of the information display area is displayed as the answer. The browsing support system according to claim 6.

8. The knowledge search unit extracts the vectorized knowledge based on similarity between the vectorized knowledge stored in the vector database and the vectorized creation information. The browsing support system according to any one of claims 1 to 7.

9. The input support system includes: a large-scale language model that reads reference information and summarizes the reference information based on text or image prompts; The knowledge search unit outputs a summary document summarized by the large-scale language model to the medical record management system. The browsing support system according to claim 8.

10. The answer includes the summary document and information about the source of the reference information summarized by the large-scale language model. The browsing support system according to claim 9 .

11. The production information includes at least one of text, audio, and image. The browsing support system according to claim 10.

12. The input support system includes: a knowledge update unit that updates the knowledge; an embedding unit that vectorizes the knowledge to be updated, embeds it in the vector space, and stores the vectorized knowledge in the vector database. The browsing support system according to claim 11.

13. The input support system includes: a knowledge database that stores the knowledge; a knowledge upload unit that uploads the knowledge to the knowledge database. The browsing support system according to claim 11.

14. The input support system includes: a knowledge database that stores the knowledge; a knowledge upload unit that uploads the knowledge to the knowledge database. The browsing support system according to claim 12.

15. A browsing assistance method performed in a browsing assistance system in which an information processing terminal having a display unit and an input unit, a medical record management system that manages electronic medical records, and an input assistance system are connected via a network, a step in which a creation support unit of the medical record management system outputs creation information for creating the electronic medical record, which is input by the information processing terminal, to the input support system; a step of vectorizing the creation information by the input support system; A step of searching for the knowledge based on the vectorized creation information from a vector database in which the knowledge that has been vectorized and embedded in a vector space is stored; a step of outputting an answer formed from the retrieved knowledge to the creation support unit; a step in which the creation support unit receives the response from the input support system and supports creation of the electronic medical record; The display unit has an information display area and an answer display area for displaying answers related to the content displayed in the information display area, and includes a step of displaying an electronic medical record creation display screen used for creating the electronic medical record. Browsing assistance methods.

16. A procedure for vectorizing information to be created for creating an electronic medical record, which information is input by an information processing terminal; A step of searching for the knowledge based on the vectorized creation information from a vector database in which the knowledge that has been vectorized and embedded in a vector space is stored; a step of outputting an answer formed from the retrieved knowledge to the information processing terminal; a procedure for displaying an electronic medical record creation display screen on a display unit of the information processing terminal, the electronic medical record creation display screen having an information display area and an answer display area for displaying answers related to the content displayed in the information display area, the electronic medical record creation display screen being used for creating the electronic medical record; A program that is executed by a computer.

Images