Medical interview system and medical interview terminal

Abstract

To provide a medical interview system and a medical interview terminal that enable a patient to easily answer interview questions.SOLUTION: A medical interview terminal 5 is operated by a patient who undergoes a medical interview. The medical interview terminal 5 has a terminal display unit 53, a medical interview processing unit 511, a terminal input unit 55, and a terminal communication unit 56. The terminal display unit 53 displays a character image. The medical interview processing unit 511 asks the patient interview questions in conjunction with movements of the character image displayed on the terminal display unit 53. The terminal input unit 55 receives input of answers to the interview questions from the patient. The terminal communication unit 56 transmits information of the answer input as interview information to a management device.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a medical interview system and a medical interview terminal used for a medical interview before medical treatment. [Background technology]

[0002] In hospitals, clinics, and other medical institutions, the medical interview conducted before treatment typically involves patients filling out a paper medical questionnaire with a writing instrument. The medical questionnaire includes personal information such as the patient's name and date of birth, as well as various other information such as their medical condition and whether or not they are taking medication. Filling out such a medical questionnaire is cumbersome, placing a significant burden on patients who are not feeling well. Therefore, a system that allows patients to easily respond to the medical questionnaire is desirable. Another common method is to complete the medical questionnaire online after making a reservation through a reservation system. Because a certain number of patients do not complete the medical questionnaire at the time of booking, and because the medical interview content (medical condition, etc.) at the time of booking and the medical interview content (medical condition, etc.) at the time of the actual visit may change over time, a system that allows patients to easily respond to the medical interview content when they visit is desirable.

[0003] Meanwhile, in recent years, a medical interview system has been proposed that allows patients to answer questions using a terminal that can be operated by the patient, such as a tablet terminal (see, for example, Patent Document 1 below). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-89650 Summary of the Invention [Problem to be solved by the invention]

[0005] However, when the patient is elderly, it may be difficult for the patient to understand how to operate the terminal to answer the questions displayed on the screen, and the patient may not be able to easily answer the questions.

[0006] The present invention has been made in consideration of the above circumstances, and an object of the present invention is to provide a medical interview system and a medical interview terminal that allow patients to easily answer questions about medical interview content. [Means for solving the problem]

[0007] The medical interview system according to the present invention comprises a medical interview terminal and a management device. The medical interview terminal is operated by a patient undergoing a medical interview. The management device manages medical interview information input by the medical interview terminal. The medical interview terminal has a display unit, a medical interview processing unit, an input unit, and a communication unit. The display unit displays a character image. The medical interview processing unit asks the patient questions about the medical interview in conjunction with the movement of the character image displayed on the display unit. The input unit accepts the patient's response input to the medical interview content. The communication unit transmits the response input information to the management device as the medical interview information.

[0008] With this configuration, a character image is displayed on the medical interview terminal, and the patient can be asked about the medical interview content in conjunction with the movement of the character image, making the medical interview content easy for the patient to understand. Therefore, the patient can easily answer the medical interview content.

[0009] The medical interview processing unit may ask the patient about the medical interview content by at least one of voice and display.

[0010] According to this configuration, the patient can be asked questions about the medical interview content in an easy-to-understand manner using at least one of voice and display, so that the patient can more easily respond to the medical interview content.

[0011] The medical interview processing unit may cause the display unit to display the contents of the medical interview and information on the patient's input answers to the medical interview in different threads for each patient.

[0012] According to this configuration, a different thread is displayed on the display unit for each patient, and the patient is asked questions about the medical interview content one by one, allowing the patient to easily answer multiple medical interview content.

[0013] The management device may store the thread data in association with each patient. In this case, the interview processing unit may read out the thread data corresponding to the patient from the management device and display it on the display unit, thereby enabling the input unit to accept a response from the patient from the continuation of the thread.

[0014] With this configuration, the thread data corresponding to the patient can be read from the management device, and the patient can continue inputting answers from that thread, which means that it is possible to avoid having to input answers again for information that was previously input in answers for each patient's thread.This makes it even easier for returning patients to answer questions.

[0015] When the medical interview processing unit receives answers input by the patient via the input unit for all of the predetermined medical interview contents, the medical interview processing unit may display a list of the input answers on the display unit as the medical interview information.

[0016] With this configuration, the patient's responses to all pre-set medical interview questions are displayed in a list on the display unit in an easy-to-understand format. If this list of medical interview information is directly transcribed into the patient's medical record, the burden on medical personnel can be reduced.

[0017] The management device may store patient-identifying information for each patient, and identify the patient based on the medical interview information received from the medical interview terminal and the patient-identifying information.

[0018] With this configuration, the patient can be identified based on the medical interview information received from the medical interview terminal and the patient identification information, and the patient can be accepted for treatment. Therefore, there is no need for a separate reception, and the burden on the patient and medical personnel can be reduced.

[0019] The medical interview system may include an electronic lock. The electronic lock is provided in each of a plurality of rooms into which different patients enter before their consultation, locking the entrance to the room and unlocking it with a different code for each room and time period. In this case, the medical interview terminal may be provided in each of the plurality of rooms.

[0020] With this configuration, patients can easily answer questions about their medical history using a medical interview terminal when they enter each of the multiple rooms, the entrances of which can be locked electronically. Furthermore, because each of the multiple rooms is a private room, even if patients are asked about their medical history by voice, it is possible to prevent the loss of privacy of the patients.

[0021] The medical interview terminal according to the present invention includes a display unit, a medical interview processing unit, an input unit, and a communication unit. The display unit displays a character image. The medical interview processing unit asks the patient about the medical interview content in conjunction with the movement of the character image displayed on the display unit. The input unit accepts the patient's response input to the medical interview content. The communication unit transmits the response input information to a management device as medical interview information.

[0022] With this configuration, a character image is displayed on the medical interview terminal, and the patient can be asked about the medical interview content in conjunction with the movement of the character image, making the medical interview content easy for the patient to understand. Therefore, the patient can easily answer the medical interview content. [Effects of the Invention]

[0023] According to the present invention, it is possible to provide a medical interview system and a medical interview terminal that allow a patient to easily respond to the contents of a medical interview. [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 is a block diagram showing the hardware configuration of a system (diagnosis system) according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating a hardware configuration and a software configuration of a management device. [Figure 3] 10 is an example of data stored in a reservation status database. [Figure 4] 10 is an example of data stored in a medical care content database. [Figure 5] 10 is an example of data stored in a thread database. [Figure 6] FIG. 1 is a plan view showing an outline of a building in which a room is located. [Figure 7] 1 is a block diagram showing the hardware and software configurations of an electronic lock; [Figure 8] This is an example of data stored in a codelist. [Figure 9] 10 is an example of data stored in an electronic lock unlocking code database. [Figure 10] FIG. 2 is a block diagram showing the hardware and software configurations of the medical interview terminal. [Figure 11A] FIG. 10 is a diagram showing an example of a display screen on a terminal display unit of the medical interview terminal. [Figure 11B] FIG. 10 is a diagram showing another example of the display screen on the terminal display unit of the medical interview terminal. [Figure 11C] FIG. 10 is a diagram showing another example of the display screen on the terminal display unit of the medical interview terminal. [Figure 12] 10 is a main flowchart showing an example of a preferable flow of a management process executed by the management device of this embodiment. [Figure 13] This is a continuation of Figure 12. [Figure 14] This is a continuation of Figure 13. [Figure 15] This is a continuation of Figure 14. [Figure 16] 10 is a flowchart showing an example of a preferable flow of a medical interview process executed by the medical interview terminal of the present embodiment. [Figure 17] 1 is a flowchart showing an example of a flow of medical treatment using the system of this embodiment (flow of system use). [Figure 18] This is a continuation of Figure 17. [Figure 19] This is a continuation of Figure 18. [Figure 20] This is a continuation of Figure 19. [Figure 21] This is a continuation of Figure 20. DETAILED DESCRIPTION OF THE INVENTION

[0025] An example of an embodiment of the present invention will be described in detail below with reference to the drawings.

[0026] <System S> FIG. 1 is a block diagram showing the hardware configuration of a system S (medical treatment system) of this embodiment. The system S of this embodiment is configured to include a management device 1, a plurality of rooms 2, an electronic lock 3 that locks the entrance to each of the rooms 2, and a network N that connects the management device 1 and the electronic locks 3 so that they can communicate with each other. The management device 1 can communicate with a related party terminal C, a patient terminal T, and a medical interview terminal 5 via the network N. The rooms 2 are provided, for example, inside a building B. It is preferable that the system S further includes an electronic lock management device 4 that manages the electronic locks 3.

[0027] [Management device 1] FIG. 2 is a block diagram showing the hardware and software configurations of the management device 1. As shown in FIG. The management device 1 realizes the software components shown in Fig. 2 using the hardware components shown in Fig. 2. The management device 1 then executes management processing using the software components to guide patients who have made appointments to an examination room and provide treatment without having to go through a waiting room shared by a large number of people, while reducing staff labor and patient waiting time. The type of management device 1 is not particularly limited. The type of management device 1 may be, for example, various types of server devices, cloud servers, etc. The management device 1 includes, as its hardware components, a device control unit 11, a device storage unit 13, a device communication unit 14, etc.

[0028] [Device Control Unit 11] The device control unit 11 includes a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), and the like.

[0029] The device control unit 11 cooperates with the device storage unit 13 and / or the device communication unit 14 as necessary. The device control unit 11 then implements the following software components of the program of this embodiment executed by the management device 1: a reservation request receiving unit 111, a reservation decision unit 112, a code acquisition unit 113, a reservation sending unit 114, a reservation status management unit 115, a check-in unit 116, a notification unit 117, a reservation extension unit 118, a medical treatment details receiving unit 119, a drug information receiving unit 120, a medical fee calculation unit 121, an invoice sending unit 122, a prescription generation unit 123, a prescription sending unit 124, a question receiving unit 125, and a response generating unit 126. The functions provided by each of the software components of the program related to the management device 1 of this embodiment will be described in the description of a preferred flow of management processing, which will be described later.

[0030] [Device storage section 13] The device storage unit 13 is a device in which data and / or files are stored, and includes a storage unit that stores data non-temporarily using a hard disk, a semiconductor memory, a recording medium, a memory card, or the like.

[0031] The device storage unit 13 stores a program executed by the CPU, an appointment status database 131, patient information, etc. Although not essential, the device storage unit 13 may also store a medical treatment content database 132, a correspondence relationship between medical treatment content and medical fees, a large-scale language model, etc. Furthermore, the device storage unit 13 stores a thread database 133.

[0032] (Reservation Status Database 131) The reservation status database 131 stores the reservation status of each of a plurality of rooms 2. The reservation status includes information for identifying the patient, the reservation time slot, and information for identifying the reserved room 2 (reserved room). The information for identifying the patient is not particularly limited. The information for identifying the patient may be, for example, a patient card number. The format of the information for identifying the reservation time slot and the reserved room 2 is not particularly limited. For ease of retrieval from and storage in the reservation status database 131, it is preferable that the reservation status be stored in association with a reservation ID that identifies the reservation status.

[0033] Fig. 3 is an example of data stored in the reservation status database 131. The reservation status database 131 in the example shown in Fig. 3 stores the reservation status associated with reservation ID "R0001", the reservation status associated with reservation ID "R0002", the reservation status associated with reservation ID "R0003", etc.

[0034] Appointment ID "R0001" is associated with the reservation status that a patient identified by patient card number "12345" has reserved room 2 (reference symbol 2A in FIG. 6) identified by room number "1" for the reservation time slot "2023 / 12 / 29 11:00-12:00." Appointment ID "R0002" is associated with the reservation status that a patient identified by patient card number "67890" has reserved room 2 (reference symbol 2A in FIG. 6) identified by room number "1" for the reservation time slot "2023 / 12 / 29 12:00-13:00." In addition, appointment ID "R0003" is associated with the reservation status that a patient identified by patient card number "11223" has reserved room 2 (reference symbol 2D in FIG. 6) identified by room number "4" for the reservation time slot "2023 / 12 / 29 11:00-12:00."

[0035] Because the reservation status described above is stored in the reservation status database 131, the management device 1 can provide patients who have reserved the same reserved room for different time periods with different codes for each time period, obtained by referencing the code list 331 (described later) or the like. In the example shown in FIG. 3, this applies to the patient identified by the patient card number "12345" and the patient identified by the patient card number "67890." Furthermore, the management device 1 can provide patients who have reserved different reserved rooms for the same time period with different codes for each room, obtained by referencing the code list 331 (described later) or the like. In the example shown in FIG. 3, this applies to the patient identified by the patient card number "12345" and the patient identified by the patient card number "11223." This allows the management device 1 to manage each room 2 as if it were a private room, rather than a waiting room shared by a large number of people.

[0036] (Medical Treatment Database 132) The medical care content database 132 stores data that associates the details of medical care provided to a patient, information on medications prescribed to the patient, medical fees billed to the patient, and information identifying the patient. In order to achieve a configuration separated by function, the medical care content database 132 may be stored on an electronic medical record system different from the management device 1. The information identifying the patient may be, for example, a patient card number. The format of the details of medical care provided to a patient, information on medications prescribed to the patient, medical fees billed to the patient, etc. is not particularly limited. For ease of retrieval and storage from the medical care content database 132, it is preferable that the above data be stored in association with a medical care ID that identifies the data. In addition, the above data may include various information related to the patient after visiting the hospital, such as the status of health insurance card verification, the status of filling out a medical questionnaire, and the status of payment.

[0037] Incidentally, the medical treatment details stored in the medical treatment details database 132 are personal information and therefore require a high level of confidentiality. In addition, the medical treatment details stored in the medical treatment details database 132 are essential data for medical institutions and therefore require reliability that prevents access to the data.

[0038] For these reasons, it is preferable that the medical care content database 132 is stored in part or in its entirety in a database constructed using blockchain technology. Blockchain technology stores transaction history together with hash values. This makes it easy to detect tampering with data in the medical care content database 132 using blockchain technology. Furthermore, blockchain technology realizes data storage and transaction execution through a P2P network that does not have a supernode that manages the entire system. This allows the medical care content database 132 using blockchain technology to achieve reliability that prevents it from becoming inaccessible due to the failure of a single supernode.

[0039] Fig. 4 is an example of data stored in the medical care content database 132. The medical care content database 132 in the example shown in Fig. 4 stores data associated with medical care ID "M0001", data associated with medical care ID "M0002", and the like.

[0040] Medical ID "M0001" is associated with the medical details "Consultation, ..." for the patient identified by medical card number "12345," the medication information for the patient "dexamethasone cipesilate capsule topical, once daily, 14 days' supply," and the medical fee for the patient billed "1,100 yen." Medical ID "M0002" is associated with the medical details "Hay fever patch test, ..." for the patient identified by medical card number "67890," the medication information for the patient "fluticasone propionate nasal spray, twice daily, 14 days' supply," and the medical fee for the patient billed "4,600 yen."

[0041] Since the above data is stored in the medical care content database 132, the management device 1 can calculate medical fees according to the medical care content and bill the patient for the medical fees. In addition, the management device 1 can generate prescription data based on the drug information and provide it to the patient.

[0042] (Large-scale language model) The large-scale language model of this embodiment is not particularly limited as long as it is a language model that performs natural language processing to generate a response to an input prompt. The "language model" referred to here is a type of probabilistic model used in natural language processing, and is a model that probabilistically predicts how likely a given word or sentence is to occur in natural language. Specifically, the language model predicts the next sentence by calculating the occurrence probability of a given sentence, etc., comparing the occurrence probabilities of multiple sentences, etc. This allows the language model to automatically generate the most likely sentence based on the context of the given sentence, etc. To achieve a separate configuration for each function, the large-scale language model may be stored in a device different from the management device 1 (e.g., a device in a call center system).

[0043] The large-scale language model of this embodiment is preferably a large-scale language model that is trained on a large amount of text of at least 500 GB or more and has a large number of parameters of at least 10 billion or more, such as OpenAI's ChatGPT-3.5, ChatGPT-4, Meta AI's LLaMa, etc. Such a large-scale language model enables the management device 1 to generate appropriate answers to questions when a prompt including a question related to an appointment and / or medical treatment is input.

[0044] In order to generate more appropriate answers, the large-scale language model of this embodiment is preferably pre-trained using training data that associates questions about appointments and / or medical treatment with answers to those questions. More specifically, the large-scale language model of this embodiment is preferably pre-trained using training data that uses questions about appointments and / or medical treatment as explanatory variables and answers to those questions as target variables.

[0045] (Thread Database 133) The thread database 133 stores data (thread data) of threads used when conducting medical interviews with patients. The thread data includes the content (thread content) and name (thread name) of threads conducted in a chat format in which medical interview details are inquired one question at a time with the patient, and these are stored in the thread database 133 in association with information identifying the patient. That is, the management device 1 stores thread data for each patient in association with each patient. The thread content includes information on the patient's responses to the medical interview details (medical interview information). The thread name can be set arbitrarily. The information identifying the patient may be, for example, a patient card number. The thread data stored in the thread database 133 may include personal information, and therefore, similar to the medical care content database 132, it is preferable that part or all of the thread data be stored in a database constructed using blockchain technology.

[0046] Fig. 5 is an example of data stored in thread database 133. Thread database 133 shown in Fig. 5 stores data associated with patient card number "12345," data associated with patient card number "67890," data associated with patient card number "11223," and the like.

[0047] In the case of a first-time patient, since there is no thread data used in previous medical interviews, new thread data is created and stored in thread database 133 in association with the patient's patient card number. On the other hand, in the case of a patient who has previously visited the hospital, the thread data used in previous medical interviews is read from thread database 133 and used, and thread data including the patient's new response input information is overwritten in thread database 133. This makes it possible to avoid having to input responses again for information that was previously input in each patient's thread. This makes it even easier for returning patients to respond to the medical interviews.

[0048] [Device Communication Unit 14] The device communication unit 14 is not particularly limited as long as it connects the management device 1 to the network N and enables communication with the related party terminal C, the patient terminal T, the interview terminal 5, etc. An example of the device communication unit 14 is a network card compatible with the Ethernet standard.

[0049] [Building B] FIG. 6 is a plan view showing an outline of building B in which room 2 is located. Building B in system S of this embodiment is provided with a plurality of rooms 2 serving as waiting rooms where patients wait for treatment (for example, reference numerals 2A to 2H in FIG. 6). Building B is not particularly limited. Building B may be, for example, a medical facility such as a hospital or clinic, or a large commercial facility. Building B may be provided with various other rooms in addition to room 2. Other parts provided in building B include, for example, an examination room where examination equipment is installed, a treatment room where medical equipment related to treatment is installed, and a storage room where various portable medical equipment is stored.

[0050] [Room 2] Room 2 is a place where patients who have made an appointment enter before their consultation to wait and receive treatment. System S includes multiple rooms 2. Room 2 has one or more entrances, including entrance 21, which is an outer door located on the outside of the medical institution. Room 2 preferably has an inner door located inside the medical institution for medical personnel to enter. Entrance 21 to room 2 is locked with an electronic lock 3, so that only the patient who has made a reservation for room 2 and medical personnel can enter. In other words, room 2 is used as a private room where patients who have made an appointment wait for their treatment.

[0051] An image 22 is posted inside room 2, providing room identification information for identifying room 2 relating to the room. The room identification information provided by image 22 is not particularly limited as long as it is information for identifying room 2. Image 22 provides the room identification information via, for example, a two-dimensional code (e.g., reference numeral 22A in FIG. 6), exemplified by a QR code (registered trademark), a barcode, a code consisting of letters and / or numbers, or the like. By posting image 22 inside room 2, patient terminal T can provide information to management device 1 that reliably indicates that a patient has entered room 2. This prevents patients from being mistaken for other patients.

[0052] Furthermore, a medical interview terminal 5 is installed inside each room 2 to be operated by a patient who enters the room. A different medical interview terminal 5 (for example, symbol 5A in FIG. 6) is installed in each room 2, and one patient who enters each room 2 can undergo a medical interview using a different medical interview terminal 5. Each medical interview terminal 5 can communicate with the management device 1 via wired or wireless communication, and medical interview information input by each medical interview terminal 5 is transmitted to the management device 1 and managed by the management device 1.

[0053] [Electronic Lock 3] The electronic lock 3 is provided to lock the entrance 21 of the room 2. The electronic lock 3 may also be provided to lock the entrance to the examination room and / or medical treatment room. This allows the system S to realize automated private examinations by using the examination room and / or medical treatment room as a private room. The type of electronic lock 3 is not particularly limited as long as it is configured to be unlocked with a different code for each room 2 and time period and to provide the codes for each time period to the management device 1. The type of electronic lock 3 may be, for example, a smart lock that is configured to automatically generate a different unlocking code for each time period and provide a list of the unlocking codes in response to a command from an external device. Each electronic lock 3 is identified by an electronic lock ID, which is information that uniquely identifies the electronic lock 3.

[0054] Although not an essential feature, the electronic lock 3 may have a mechanism similar to a so-called master key, which allows medical personnel to enter the room 2 via the master key mechanism without having to enter different unlock codes for each room 2 and each time period.

[0055] 7 is a block diagram showing the hardware and software configurations of the electronic lock 3. The electronic lock 3 includes, as its hardware components, an electronic lock control unit 31, an electronic lock locking / unlocking unit 32, an electronic lock memory unit 33, an electronic lock communication unit 34, an electronic lock input unit 35, etc.

[0056] [Electronic lock control unit 31] The electronic lock control unit 31 includes a central processing unit (CPU), random access memory (RAM), and read only memory (ROM), etc. The electronic lock control unit 31 controls the electronic lock / unlock unit 32 between a locked state and an unlocked state.

[0057] The electronic lock control unit 31 cooperates with the electronic lock locking / unlocking unit 32, the electronic lock storage unit 33, the electronic lock communication unit 34, and / or the electronic lock input unit 35 as necessary. The electronic lock control unit 31 then realizes the software components executed by the electronic lock 3, such as the code management unit 311, the code provision unit 312, the unlocking instruction receiving unit 313, and the unlocking unit 314.

[0058] The code management unit 311 is realized by the electronic lock control unit 31 and the electronic lock storage unit 33 working together. The code management unit 311 manages the codes for each time period stored in the code list 331. It is preferable that the code management unit 311 automatically generates a different code for each room 2 and time period. The "time period" here refers to each time period divided into a given time unit, such as one hour, during which a medical institution treats patients. It is preferable that the "given time unit" is one hour, so as to allow some leeway in timing for visits, ensure sufficient treatment time, and make it easier for patients to understand the time period. It is preferable that the code managed by the code management unit 311 consists of elements that can be input from the electronic lock input unit 35. The code is, for example, a personal identification number consisting of multiple numbers.

[0059] The code providing unit 312 is realized by the cooperation of the electronic lock control unit 31, the electronic lock storage unit 33, and the electronic lock communication unit 34. When requested to provide the above-mentioned code by an external device such as the management device 1, the code providing unit 312 refers to the code list 331 and provides data in which a time period is associated with a code for that time period to the outside. From a security standpoint, it is preferable that the code providing unit 312 provides codes only to authenticated devices. The authentication is realized by various procedures, for example, a procedure using an encryption key, a procedure for identifying an address on the network N, etc.

[0060] The unlock instruction receiving unit 313 is realized by cooperation between the electronic lock control unit 31, the electronic lock storage unit 33, etc. The unlock instruction receiving unit 313 receives an unlock instruction including a code. This reception may be by receiving communication via the electronic lock communication unit 34, or by receiving input via the electronic lock input unit 35. After receiving the unlock instruction, the unlock instruction receiving unit 313 transfers processing to the unlocking unit 314.

[0061] The unlocking unit 314 is realized by the cooperation of the electronic lock control unit 31, the electronic lock operation / unlocking unit 32, and the electronic lock storage unit 33. The unlocking unit 314 compares the code included in the unlocking instruction received by the unlocking instruction receiving unit 313 with the codes stored in the code list 331. Then, the unlocking unit 314 unlocks the entrance 21 if the code included in the received unlocking instruction is a code associated with the time zone to which the current date and time belongs. This unlocking is realized by controlling the electronic lock operation / unlocking unit 32 of the electronic lock 3 to the unlocked state.

[0062] [Electronic Lock / Unlock Unit 32] The electronic lock locking / unlocking unit 32 controls the electronic lock 3 between a locked state and an unlocked state in accordance with control from the electronic lock control unit 31. There are no particular limitations on the type of the electronic lock locking / unlocking unit 32. The type of the electronic lock locking / unlocking unit 32 may be the same as, for example, various conventionally known electronic locks and various electronic locks based on them.

[0063] [Electronic Lock Memory Unit 33] The electronic lock storage unit 33 stores programs executed by the CPU, a code list 331, and the like.

[0064] (Code Listing 331) The code list 331 stores data associating time periods with codes for unlocking the electronic locks 3 during those time periods. The codes are preferably made up of elements that can be input from the electronic lock input unit 35. The codes are, for example, a PIN number consisting of multiple numbers. The codes corresponding to the same time period are different for each electronic lock 3. In other words, the codes corresponding to the same time period are different for each room 2. The codes are preferably stored in association with an electronic lock ID, which is information that identifies the electronic lock 3.

[0065] Fig. 8 is an example of data stored in the code list 331. The example shown in Fig. 8 stores codes corresponding to time periods, such as code "112233" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 10:00-11:00", code "456456" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 11:00-12:00", and code "789078" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 12:00-13:00".

[0066] By storing these codes, the electronic lock 3 that locks the entrance 21 of the room 2 can refer to the code list 331 to determine whether it has received a code corresponding to the time period. The electronic lock 3 can then unlock the entrance 21 of the room 2 when it receives a code that differs for each room 2 and time period. The management device 1, which has received the code via the code providing unit 312 of the electronic lock 3, provides the code "456456" corresponding to the time period "2023 / 12 / 29 11:00-12:00." This code differs for each room 2 and time period. Therefore, the patient cannot unlock the electronic lock 3 during time periods other than the time period, such as "10:00-11:00" or "12:00-13:00."

[0067] [Electronic Lock Communication Section 34] The electronic lock communication unit 34 is not particularly limited as long as it connects the electronic lock 3 to the network N and enables communication with the management device 1, etc. An example of the electronic lock communication unit 34 is a wireless communication device connected to a wireless LAN.

[0068] Although not an essential aspect, it is preferable that the electronic lock communication unit 34 is configured to enable communication between the related party terminal C and the patient terminal T and the electronic lock 3. This allows the electronic lock communication unit 34 to receive the above-mentioned unlocking instructions from the related party terminal C and the patient terminal T. The electronic lock 3 configured in this manner may not include the electronic lock input unit 35.

[0069] [Electronic lock input unit 35] The electronic lock input unit 35 is configured to allow the patient or the like to input unlocking instructions including a code. The electronic lock input unit 35 is realized, for example, by a keypad or touch panel for inputting numbers, symbols, letters, etc. The electronic lock input unit 35 may also be realized, for example, by an optical reader that reads various optically readable codes, such as two-dimensional codes, barcodes, and codes consisting of letters and / or numbers.

[0070] [Electronic lock management device 4] The electronic lock management device 4 includes a lock management device control unit 41, a lock management device storage unit 42 that stores programs executed by the lock management device control unit 41 and an electronic lock unlocking code database 421, and a lock management device communication unit 43. The hardware configurations of the lock management device control unit 41, the lock management device storage unit 42, and the lock management device communication unit 43 may be similar to those of the device control unit 11, the device storage unit 13, and the device communication unit 14, respectively. The electronic lock management device 4 executes an electronic lock management process that manages the electronic lock 3 that locks room 2 and the electronic lock unlocking code database 421 through cooperation of the lock management device control unit 41, the lock management device storage unit 42, and the lock management device communication unit 43. The electronic lock management process includes a procedure for referencing the electronic lock unlocking code database 421 in response to a command from the management device 1 and providing the management device 1 with a code that unlocks the electronic lock 3 that locks room 2 during a specified time period. The electronic lock management process also includes a procedure for automatically updating data stored in the electronic lock unlocking code database 421 in cooperation with the electronic lock 3. The procedure for automatically updating data preferably includes a procedure for automatically generating a different code for each room 2 and time period. The electronic lock unlocking code database 421 stores data that associates an electronic lock ID, which is information that uniquely identifies the electronic lock 3, information that identifies the room 2 whose entrance is locked by the electronic lock 3, a time period, and a code (unlocking code) that unlocks the electronic lock 3 during that time period.

[0071] FIG. 9 is an example of data stored in the electronic lock unlocking code database 421. In the example shown in Figure 9, codes corresponding to time periods are stored, such as code "112233" to unlock the electronic lock 3 identified by electronic lock ID "K0001" during the time period "2023 / 12 / 29 10:00-11:00", code "456456" to unlock the electronic lock 3 identified by electronic lock ID "K0001" during the time period "2023 / 12 / 29 11:00-12:00", code "789078" to unlock the electronic lock 3 identified by electronic lock ID "K0001" during the time period "2023 / 12 / 29 12:00-13:00", and code "445566" to unlock the electronic lock 3 identified by electronic lock ID "K0002" during the time period "2023 / 12 / 29 11:00-12:00".

[0072] By storing these codes, the management device 1 can refer to the electronic lock unlocking code database 421 via the electronic lock management device 4 to determine whether it has received a code corresponding to the room 2 and time period. The electronic lock 3 can unlock the entrance 21 of the room 2 when a different code is received for each room 2 and time period. The management device 1, which has received the code via the code providing unit 312 of the electronic lock 3, provides the code "456456" corresponding to the time period to a patient who has reserved a room 2 locked by the electronic lock 3 identified by the electronic lock ID "K0001" for the time period "2023 / 12 / 29 11:00-12:00." This code is different for each room 2 and time period. Therefore, the patient cannot unlock the electronic lock 3 corresponding to the room 2 during a time period other than the time period, for example, "10:00-11:00" or "12:00-13:00." Furthermore, the patient cannot unlock an electronic lock 3 corresponding to a different room 2, for example, an electronic lock 3 identified by electronic lock ID "K0002", even if it is during the same time period as the patient, for example, "11:00-12:00".

[0073] [Stakeholder terminal C] There is no particular limitation on the type of related party terminal C. The related party terminal C may be, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, etc. The related party terminal C executes a process of receiving a notification from the management device 1, and, when the notification is received, a process of notifying the medical personnel using the related party terminal C of the reception of the notification via a screen display and / or audio output, etc.

[0074] [Network N] The type of network N is not particularly limited as long as it enables communication between the management device 1, the electronic lock 3, the patient terminal T, the related party terminal C, and the medical interview terminal 5. The type of network N is, for example, the Internet, a mobile phone network, a wireless LAN, etc.

[0075] [Patient terminal T] There are no particular limitations on the type of the patient terminal T. The patient terminal T may be, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, etc. The patient terminal T is configured to execute processes such as sending a reservation request to the management device 1, receiving, storing, and displaying information related to the reservation sent from the management device 1, and sending room identification information, etc. to the management device 1.

[0076] [Medical interview terminal 5] FIG. 10 is a block diagram showing the hardware and software configurations of the medical interview terminal 5. The medical interview terminal 5 realizes the software components shown in FIG. 10 using the hardware components shown in FIG. 10. The type of the medical interview terminal 5 is not particularly limited. The medical interview terminal 5 may be, for example, a personal computer, a tablet terminal, or the like. The medical interview terminal 5 includes, as its hardware components, a terminal control unit 51, a terminal storage unit 52, a terminal display unit 53, a terminal output unit 54, a terminal input unit 55, a terminal communication unit 56, and the like. However, the medical interview terminal 5 is not limited to a configuration in which all of these units are included in the medical interview terminal 5; at least some of these units may not be included in the medical interview terminal 5. For example, the terminal control unit 51 and the terminal memory unit 52 may be realized by a separate server. In this case, the medical interview terminal 5 may include only the terminal display unit 53, the terminal output unit 54, the terminal input unit 55, and the terminal communication unit 56, which perform input and output, and may only use a browser.

[0077] [Terminal control unit 51] The terminal control unit 51 includes a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), and the like.

[0078] The terminal control unit 51 cooperates with the terminal storage unit 52, the terminal display unit 53, the terminal output unit 54, the terminal input unit 55, and / or the terminal communication unit 56 as necessary. The terminal control unit 51 then realizes the software components of the program of this embodiment executed on the medical interview terminal 5, such as the medical interview processing unit 511, the thread sending unit 512, and the thread receiving unit 513.

[0079] The medical interview processing unit 511 is realized by the cooperation of the terminal storage unit 52, the terminal display unit 53, the terminal output unit 54, and the terminal input unit 55. The medical interview processing unit 511 displays threads associated with each patient on the terminal display unit 53 based on the thread data stored in the terminal storage unit 52. Furthermore, not only the threads but also character images are displayed on the terminal display unit 53. At this time, sound is output from the terminal output unit 54 as necessary.

[0080] The patient inputs a response to the medical interview content queried by display and / or voice using the terminal input unit 55, and the information of the input response is displayed on the terminal display unit 53. In this way, the medical interview processing unit 511 can inquire about the medical interview content to the patient by at least one of voice and display. The medical interview processing unit 511 displays the medical interview content and the information of the patient's input response to the medical interview content on the terminal display unit 53 in different threads for each patient.

[0081] The character image is a so-called avatar, and is an image of a character in a virtual space that is based on a human or a human-like animal. The character image is displayed so that parts of the body, such as the mouth, move in accordance with the timing of the display of the medical interview content displayed sequentially in the thread. At this time, sound may be output from the terminal output unit 54 in accordance with the movement of the character image. In this way, the medical interview processing unit 511 queries the patient about the medical interview content on the thread in conjunction with the movement of the character image displayed on the terminal display unit 53. In this way, the character image is displayed on the medical interview terminal 5, and the patient can be asked about the medical interview content in conjunction with the movement of the character image, making the medical interview content easy for the patient to understand. Therefore, the patient can easily answer the medical interview content.

[0082] The medical interview content displayed sequentially in the thread can be realized using a large-scale language model. Examples of such a large-scale language model include ChatGPT-3.5 and ChatGPT-4 from OpenAI, and LLaMa from Meta AI, but the language model is not particularly limited as long as it performs natural language processing to generate a response to an input prompt. With such a large-scale language model, when a prompt including a patient's response to the medical interview content is input, the medical interview terminal 5 can generate an appropriate response to the input.

[0083] A plurality of medical interview contents are set in advance, and when the patient has input answers to all the set medical interview contents, the medical interview processing unit 511 ends the inquiry to the patient about the medical interview contents. Then, the medical interview processing unit 511 displays a list of the input answers to the plurality of medical interview contents as medical interview information on the terminal display unit 53. Data of the thread used by the medical interview processing unit 511 to inquire about the medical interview contents to the patient is stored in the terminal storage unit 52 as thread data 521.

[0084] The thread sending unit 512 is realized by the terminal storage unit 52 and the terminal communication unit 56 working together. After the medical interview processing unit 511 has finished inquiring about the contents of the medical interview with the patient, the thread sending unit 512 reads out the thread data used for the inquiry from the terminal storage unit 52 and sends it to the management device 1. This thread data includes the patient's response as medical interview information. The management device 1 stores the thread data 521 received from the medical interview terminal 5 in the thread database 133.

[0085] The thread receiving unit 513 is realized by the cooperation of the terminal storage unit 52 and the terminal communication unit 56. When starting to interview a patient, the thread receiving unit 513 reads thread data 521 associated with the patient from the management device 1 and stores it in the terminal storage unit 52. By reading the thread data 521 corresponding to the patient from the management device 1 and storing it in the terminal storage unit 52, and displaying the thread on the terminal display unit 53, it becomes possible to accept an answer input from the patient from the continuation of the thread.

[0086] The patient may be identified based on the name, date of birth, and other information input by the patient at the start of the medical interview. In this case, thread data 521 associated with the patient's patient card number is read from management device 1 and stored in terminal storage unit 52. In this way, management device 1 stores the patient card number, which is information identifying the patient, for each patient, and can identify the patient based on the medical interview information and the patient card number received from medical interview terminal 5. However, the patient may also input the patient card number as an answer at the start of the medical interview. In this case, a configuration may be adopted in which if even one of the name, date of birth, and other information associated with the patient card number differs from the information input as an answer, a notification to that effect is issued. The patient may also be identified using various biometric authentication methods, such as facial recognition and voice recognition, or by reading an insurance card or the like.

[0087] [Terminal storage unit 52] The terminal storage unit 52 is a device for storing data and / or files, and includes a storage unit for non-temporarily storing data using a hard disk, a semiconductor memory, a recording medium, a memory card, etc. The terminal storage unit 52 also stores programs executed by the CPU, thread data 521, etc. The thread data 521 may be read from the management device 1 and stored in the terminal storage unit 52 only when a medical interview is conducted with a patient.

[0088] [Terminal display unit 53] The terminal display unit 53 is configured to be able to display character images and threads, and is realized by, for example, a liquid crystal display, an organic EL display, or the like.

[0089] [Terminal output unit 54] The terminal output unit 54 is configured to be able to output sound. The terminal output unit 54 is realized by, for example, a speaker. The terminal output unit 54 outputs sound in conjunction with the movement of the character image displayed on the terminal display unit 53, so that the patient can be asked about the contents of the medical interview by voice.

[0090] [Terminal input unit 55] The terminal input unit 55 is configured to be able to accept input of a patient's response to the medical interview content. The terminal input unit 55 is realized by, for example, a keypad or a touch panel for inputting numbers, symbols, letters, etc. The terminal display unit 53 and the terminal input unit 55 may be integrally configured by a display with a touch panel.

[0091] [Terminal communication unit 56] The terminal communication unit 56 is not particularly limited as long as it connects the interview terminal 5 to the network N and enables communication with the management device 1, etc. An example of the terminal communication unit 56 is a wireless communication device connected to a wireless LAN.

[0092] [Display screen of the medical interview terminal] 11 is a diagram showing an example of a display screen on the terminal display unit 53 of the medical interview terminal 5. The display screen of the terminal display unit 53 includes a character display area 531, a thread display area 532, a thread name display area 533, an answer input area 534, a conversation button 535, etc.

[0093] Character image 531A is displayed in character display area 531. Character image 531A is, for example, an avatar with a human motif, and includes at least a head as part of its body. When making an inquiry about the contents of a medical interview with a patient in thread display area 532, it is preferable that at least the mouth of character image 531A moves, and it is more preferable that parts other than the facial expression and face also move.

[0094] The thread name display area 533 displays the thread name of the thread displayed in the thread display area 532. The thread name is, for example, a patient ID, but is not limited to this and may be another name such as a patient number. As described with reference to FIG. 5, this thread name is stored in the thread database 133 in association with the patient card number along with the content of the thread displayed in the thread display area 532. Therefore, when the content of the thread corresponding to each patient is read from the thread database 133, the thread name is also read and displayed in the thread name display area 533. Note that the thread name displayed in the thread name display area 533 cannot be modified on the screen.

[0095] A plurality of medical interview contents 532A, 532B, etc. are displayed in sequence in the thread display area 532. The character image 531A in the character display area 531 moves in sync with the display timing of each medical interview content 532A, 532B, etc., allowing the patient to receive the medical interview as if the character were talking to them. The medical interview contents may include at least one of the patient's name, date of birth, sex, body temperature, health conditions of family members living together, symptoms, whether or not the patient is taking medication, whether or not the patient has allergies, and the form of desired medication. However, the medical interview contents are not limited to these, and the patient can be asked about any item as the medical interview contents. Furthermore, each item of the medical interview contents may be predetermined or may be freely settable.

[0096] The patient answers each of the medical interview contents 532A, 532B, etc. individually by inputting answers in the answer input area 534. That is, when the medical interview content 532A for "Name" is displayed in the thread, the patient inputs his / her own name in the answer input area 534. When the medical interview content 532B for "Date of Birth" is displayed in the thread, the patient inputs his / her own date of birth in the answer input area 534.

[0097] When the patient's answer input in the answer input area 534 is accepted for all of the pre-set medical interview contents 532A, 532B, ..., a list of answer input contents 532Z is ​​displayed as medical interview information in the thread display area 532. The contents of this thread are sent to the management device 1 and stored in the thread database 133, thereby realizing transmission of medical interview information from the medical interview terminal 5 to the management device 1. If the management device 1 directly transcribes this list of medical interview information into the medical record (electronic medical record), the burden on medical personnel can be reduced. However, the medical interview information is not limited to being manually transcribed, and may be automatically transcribed in the management device 1.

[0098] Instead of inputting answers to the answer input area 534 as described above, answers to each of the medical interview contents 532A, 532B, etc. can be individually input by voice by selecting the conversation button 535. In this case, since there is a possibility that the name cannot be converted correctly by voice input, the name may be accepted only by input to the answer input area 534, or the name of a patient identified in advance may be displayed in the thread display area 532 for the patient to confirm.

[0099] 11B and 11C are diagrams showing other examples of the display screen on the terminal display unit 53 of the medical interview terminal 5. While Fig. 11A shows an example of the display screen of a personal computer or a tablet terminal, Figs. 11B and 11C show an example of the display screen of a mobile terminal. Figs. 11B and 11C show display examples when the display screen is turned vertically, but when the display screen is turned horizontally, the arrangement of each area on the display screen may be changed.

[0100] The display screen of the terminal display unit 53 shown in Fig. 11B includes a character display area 531, a thread display area 532, a thread name display area 533, a reply input area 534, a conversation button 535, etc. Explanation of each area is omitted as it is the same as in Fig. 11A. However, if the display screen is small, the number of characters to be displayed may be limited, such as by displaying only the most recent round of conversation in the thread display area 532, or the thread display area 532 itself may not be displayed.

[0101] The display screen of the terminal display unit 53 shown in FIG. 11C includes a character display area 531, a thread display area 532, a thread name display area 533, a response input area 534, a conversation button 535, and the like. Description of each area is omitted as it is the same as that of FIG. 11A. In this example, the character display area 531 and the thread display area 532 overlap in part or in whole, and the thread is displayed so as to overlap the character image 531. This allows a large amount of content to be displayed even if the display screen is small. In this case, the medical interview content is displayed on the left side of the thread display area 532, and the patient's response is displayed on the right side. An icon corresponding to the character image 531A may be added to each display of the medical interview content.

[0102] [Main flowchart of management process] Fig. 12 is a main flowchart showing an example of a preferable flow of the management process executed by the management device 1 of this embodiment. Fig. 13 is a diagram continuing from Fig. 12. Fig. 14 is a diagram continuing from Fig. 13. Fig. 15 is a diagram continuing from Fig. 14. The following is an example of a preferable flow of the management process executed by the management device 1 of this embodiment, using Figs. 12 to 15.

[0103] The management device 1 executes a series of processes related to medical appointment reservations in steps S1 to S6. Through this series of processes, the management device 1 manages the reservation status of each of the multiple rooms 2, obtains a code corresponding to the reservation time slot, such as a PIN number, from the electronic lock 3, and transmits this code along with information about the reserved rooms 2 to the patient terminal T, thereby guiding each patient with overlapping reservation time slots to a different room 2. Each of these rooms 2 is locked by an electronic lock 3 that is unlocked with a different code for each time slot. Therefore, the management device 1 of this embodiment can manage so that only patients and medical personnel who unlock the electronic lock 3 using the reservation code corresponding to the reservation time slot can enter the reserved room 2.

[0104] [Step S1: Determine whether a reservation request has been received] The device control unit 11 operates in cooperation with the device storage unit 13 and the device communication unit 14 to execute the reservation request receiving unit 111. Then, the device control unit 11 executes a process of determining whether a reservation request (reservation request) including at least a desired time slot has been received from the patient's terminal (patient terminal T) by the reservation request receiving unit 111 (step S1, reservation request receiving step). If it is determined that a reservation request has been received, the device control unit 11 proceeds to step S2. If it is not determined that a reservation request has been received, the device control unit 11 proceeds to step S7. In order to reflect various requests in the reservation, it is preferable that the reservation request further includes information other than the desired time slot, such as the medical department and the person in charge desired by the patient, in addition to the desired time slot.

[0105] [Step S2: Determine whether a reservation is available for the desired time slot] The device control unit 11 operates the reservation decision unit 112 in cooperation with the device storage unit 13 and the device communication unit 14. The device control unit 11 then executes a process in which the reservation decision unit 112 refers to the reservation status database 131 and determines whether or not a reservation is possible for the desired time slot included in the reservation request received in the reservation request receiving step (step S2, reservation availability determination step). If it is determined that a reservation is possible, the device control unit 11 moves the process to step S3. If it is not determined that a reservation is possible, the device control unit 11 notifies the patient terminal T involved in the reservation request receiving step that a reservation is not possible for the desired time slot, and returns the process to step S1. By notifying as described above and returning the process, the management device 1 allows the patient to request another reservation for a different desired time slot.

[0106] In order to accommodate the circumstances of the medical institution and the patient's more detailed wishes, the appointment availability determination step may also refer to information other than the desired time period, such as closed days, medical departments, and the patient's preferred staff member, to determine whether an appointment can be made.

[0107] [Step S3: Determine the reservation time slot and room] The device control unit 11 executes a process in which the reservation decision unit 112 refers to the reservation status database 131 and determines a reserved time slot and reserved room corresponding to the desired time slot included in the reservation request received in the reservation request receiving step (step S3, reservation decision step). The "reserved room" here refers to a room 2 among multiple rooms 2 that is allocated to a reservation for the reserved time slot. The device control unit 11 proceeds to step S4.

[0108] [Step S4: Obtain the code from the electronic lock] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the code acquisition unit 113. Then, the device control unit 11 executes a process to acquire, by the code acquisition unit 113, a reservation code, which is the code for the reserved time slot related to the reservation confirmation step, from the electronic lock 3 that locks the entrance 21 of the reserved room related to the reservation confirmation step (step S4, code acquisition step). The "code for the reserved time slot" here is the code that unlocks the electronic lock 3 during the reserved time slot. The device control unit 11 moves the process to step S5. Note that the acquisition of the reservation code in the code acquisition step may be performed via the electronic lock management device 4 that manages the electronic lock 3.

[0109] [Step S5: Send reservation information] The device control unit 11 executes the reservation sending unit 114 in cooperation with the device storage unit 13 and the device communication unit 14. Then, the device control unit 11 executes a process in which the reservation sending unit 114 sends information related to the reservation decided in the reservation decision step to the patient terminal T involved in the reservation request receiving step (step S5, reservation sending step). The "information related to the reservation" here includes at least the reservation time slot and reserved room decided in the reservation decision step, and the reservation code acquired in the code acquisition step. The device control unit 11 proceeds to step S6.

[0110] In order to allow the medical personnel to be aware of the reservation status, the reservation sending step preferably sends information about the reservation to the patient terminal T as well as the medical personnel terminal C.

[0111] [Step S6: Store reservation information] The device control unit 11 operates in cooperation with the device storage unit 13 and the device communication unit 14 to execute the reservation status management unit 115. Then, the device control unit 11 executes a process of storing information related to the reservation transmitted in the reservation transmission step by the reservation status management unit 115 (step S6, reservation status management step). The device control unit 11 then proceeds to step S7.

[0112] In steps S7 to S8, the management device 1 executes a series of processes to notify the terminal of the medical personnel (related party terminal C) of the entry of the patient who transmitted the room identification information. Through this series of processes, when room identification information, etc., provided in the reserved room and transmitted from the patient terminal T of the patient who entered the reserved room 2 is received by the management device 1, the management device 1 notifies the related party terminal C that the patient is waiting in the reserved room. As a result, the management device 1 of this embodiment allows patients to wait in rooms 2 that are greater in number than the number of medical personnel, while allowing the medical personnel to treat the patient when the room identification information, etc., is received and treatment becomes possible. As a result, the management device 1 of this embodiment prevents patients with reservations from having to wait unnecessarily.

[0113] [Step S7: Determine whether check-in information has been received] The device control unit 11 operates in cooperation with the device storage unit 13 and the device communication unit 14 to execute the check-in unit 116. Then, the device control unit 11 executes a process of determining whether check-in information including room identification information has been received from the patient terminal T by the check-in unit 116 (step S7, check-in step). If it is determined that the information has been received, the device control unit 11 proceeds to step S8. If it is not determined that the information has been received, the device control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S8.

[0114] The check-in information in the check-in step includes room identification information, information identifying the patient, etc. The room identification information in the check-in step is, for example, information acquired by reading an image 22 posted in room 2, which is the reserved room, with the patient terminal T.

[0115] (Regarding confirmation of insurance card, etc.) The management device 1 preferably executes a series of processes for verifying various documents required for medical treatment, such as health insurance cards. This process includes a process of referencing information on the verification status of various documents stored in the device storage unit 13 and proceeding with verification procedures for documents that have not yet been verified. "Various documents required for medical treatment" includes, for example, various documents that are verified monthly, such as health insurance cards, My Number cards with registered health insurance card usage, and high-cost medical care fee limit application certificates. "Verification procedures" include, for example, a procedure for reading health insurance card information from My Number cards using a My Number card reader, a procedure for sending instructions to medical institution staff to verify the documents, etc.

[0116] [Step S8: Notify the medical personnel's terminal] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the notification unit 117. Then, the device control unit 11 executes a process of notifying the terminal of the medical care related person (related person terminal C) that the patient related to the check-in step is waiting in the reserved room related to the step by the notification unit 117 (step S8, notification step). The device control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S8.

[0117] In order to allow medical personnel to enter the reserved room without using a system similar to a master key, it is preferable that the notification step notify the personnel terminal C of the code to unlock the electronic lock 3 installed at the entrance 21 of the reserved room.

[0118] However, due to circumstances specific to medical treatment at medical institutions, such as the number of doctors and other medical personnel providing care during the scheduled time slot being fewer than the number of patients receiving treatment during the scheduled time slot, and the time required for treatment being longer than expected depending on symptoms, etc., there may be cases where medical personnel are unable to treat patients during the scheduled time slot.

[0119] In the above situation, although not a required aspect, the management device 1 may execute a series of processes related to extending an appointment (steps S9 to S12). By executing the appointment extension steps, which are a series of processes related to extending an appointment, the management device 1 can extend the appointment of a patient who was unable to receive treatment during the scheduled time slot. In this extension, the management device 1 determines an extension room to be assigned to the appointment during the extended time slot, thereby preventing the effort of moving another patient who has already been assigned a room. The management device 1 can manage so that a patient who was unable to receive treatment during the scheduled time slot waits for treatment in an appropriate room and receives treatment, based on the extended time slot, extension room, and extension code sent to the patient's terminal.

[0120] [Step S9: Determine whether reservation extension is required] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the reservation extension unit 118. Then, the device control unit 11 executes a process to determine whether a reservation extension is necessary using the reservation extension unit 118 (step S9, extension necessity determination step). If it is determined that a reservation extension is necessary, the device control unit 11 proceeds to step S10. If it is not determined that a reservation extension is necessary, the device control unit 11 proceeds to step S13.

[0121] In the extension necessity determining step, the procedure for determining whether an appointment extension is necessary is not particularly limited. To enable automatic extension, the procedure preferably includes a procedure for determining that an appointment extension is necessary when, for a patient who has entered the reserved room, the time remaining until the end of the reserved time slot falls below a given time and information indicating that the medical treatment for that patient has ended has not been received from the related party terminal C. Furthermore, to enable extension by the medical treatment related party, the procedure preferably includes a procedure for determining that an appointment extension is necessary when an instruction to extend the appointment is received from the related party terminal C.

[0122] [Step S10: Determine the extension time period and extension room] The device control unit 11 executes a process of determining an extended time slot and an extended room by referring to the reservation status database 131 using the reservation extension unit 118 (step S10, reservation extension execution step). The device control unit 11 moves the process to step S11. The reservation extension execution step may be similar to the reservation determination step, except that the extended time slot is a time slot that follows the current reserved time slot, and the extended room is set to the same room as the reserved room whenever possible.

[0123] [Step S11: Obtain the code from the electronic lock] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the code acquisition unit 113. Then, the device control unit 11 executes a process to acquire an extension code, which is the code for the extension time period related to the reserved extension execution step, from the electronic lock 3 that locks the entrance 21 of the extension room related to the reserved extension execution step, using the code acquisition unit 113 (step S11, extension code acquisition step). The "extension time period code" here is the code that unlocks the electronic lock 3 during the extension time period. The device control unit 11 moves the process to step S12.

[0124] [Step S12: Transmit information related to extension] The device control unit 11 executes the reservation transmission unit 114 in cooperation with the device storage unit 13 and the device communication unit 14. Then, the device control unit 11 executes a process of transmitting information related to the extension determined in the reservation extension execution step to the patient terminal T by the reservation transmission unit 114 (step S12, extension transmission step). The "information related to the extension" here includes at least the extension time slot and extension room determined in the reservation extension execution step, and the extension code acquired in the extension code acquisition step. The device control unit 11 proceeds to step S13.

[0125] Although not a required feature, it is preferable that the management device 1 executes a series of processes related to database creation of medical treatment details and medical fee billing (steps S13 to S21). This allows the management device 1 to bill patients for medical fees not only during the process from appointment to appointment, but also during the medical fee billing process, without requiring patients to go through a waiting room for payment, which is shared by a large number of patients. This also allows the management device 1 to reduce staff effort and patient waiting time, not only during the process from appointment to appointment, but also during the medical fee billing process. In order to achieve a separate configuration for each function, it is preferable that this series of processes be executed on an electronic medical record system different from the management device 1.

[0126] This series of processes preferably includes processes related to issuing a prescription (steps S15 to S16 and steps S20 to S21). As a result, the management device 1 not only ensures that patients can purchase medicines based on a prescription without having to go through a waiting room for payment, which is shared by many people, but also ensures that patients can purchase medicines based on a prescription without having to go through a waiting room for payment, which is shared by many people. Furthermore, with the above-mentioned configuration, the management device 1 can reduce staff labor and patient waiting time not only in the process of making an appointment and receiving a consultation, but also in the procedure of providing a prescription.

[0127] [Step S13: Determine whether medical treatment details have been received] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the medical treatment content receiving unit 119. Then, the device control unit 11 executes a process to determine whether the medical treatment content has been received by the medical treatment content receiving unit 119 (step S13, medical treatment content receiving step). If it is determined that the medical treatment content has been received, the device control unit 11 shifts the process to step S14. If it is not determined that the medical treatment content has been received, the device control unit 11 shifts the process to step S15.

[0128] [Step S14: Store medical treatment details] The device control unit 11 executes a process of storing the medical care details received in the medical care details receiving step in the medical care details database 132 by the medical care details receiving unit 119 (step S14, medical care details storing step). The device control unit 11 moves the process to step S15. In the medical care details storing step, the medical care details are associated with information that identifies the patient, information that indicates the timing of the medical care, etc., and stored in the medical care details database 132. Note that, in order to maintain confidentiality of the medical care details and improve reliability, if part or all of the medical care details database 132 is realized by blockchain technology, it is preferable that the medical care details be stored in the medical care details database 132 realized by blockchain technology.

[0129] [Step S15: Determine whether drug information has been received] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the drug information receiving unit 120. Then, the device control unit 11 executes a process to determine whether drug information has been received by the drug information receiving unit 120 (step S15, drug information receiving step). If it is determined that the information has been received, the device control unit 11 proceeds to step S16. If it is not determined that the information has been received, the device control unit 11 proceeds to step S17.

[0130] [Step S16: Store drug information] The device control unit 11 executes a process of storing the drug information received in the drug information receiving step in the medical care content database 132 by the drug information receiving unit 120 (step S16, drug information storage step). The device control unit 11 moves the process to step S17. In the drug information storage step, the drug information is associated with information identifying the patient, information indicating the timing of medical treatment, etc., and stored in the medical care content database 132. Note that, in order to maintain the confidentiality of the drug information and improve its reliability, if part or all of the medical care content database 132 is realized by blockchain technology, it is preferable that the drug information be stored in the medical care content database 132 realized by blockchain technology.

[0131] [Step S17: Determine whether to calculate medical fees] The device control unit 11 cooperates with the device storage unit 13 to execute the medical fee calculation unit 121. Then, the device control unit 11 executes a process to determine whether to calculate medical fees using the medical fee calculation unit 121 (step S17, medical fee calculation determination step). If it is determined that calculation should be performed, the device control unit 11 shifts the process to step S18. If it is not determined that calculation should be performed, the device control unit 11 shifts the process to step S20.

[0132] The process of determining whether or not to calculate medical fees in the medical fee calculation determination step includes, for example, a procedure of determining that medical fees should be calculated when information indicating the end of medical treatment is received from the related party terminal C.

[0133] [Step S18: Calculate medical fees] The device control unit 11 executes a process to calculate the medical fee determined to be calculated in the medical fee calculation determination step by the medical fee calculation unit 121 (step S18, medical fee calculation step). The device control unit 11 moves the process to step S19. The medical fee calculation step calculates the medical fee based on the medical details stored in the medical details storage step, by referring to the correspondence between the medical details and medical fees stored in the device memory unit 13, various medical fee reductions and exemptions related to the patient, etc.

[0134] [Step S19: Send invoice] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the bill sending unit 122. Then, the device control unit 11 executes processing to send an invoice requesting the medical fee calculated in the medical fee calculation step to the patient terminal T by the invoice sending unit 122 (step S19, invoice sending step). The device control unit 11 proceeds to step S20.

[0135] [Step S20: Determine whether to send the prescription] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the prescription generation unit 123. Then, the device control unit 11 executes a process of determining whether to send the prescription using the prescription generation unit 123 (step S20, prescription generation step). If it is determined that the prescription should be sent, the device control unit 11 generates prescription data using the prescription generation unit 123 based on the drug information stored in the drug information storage step. Then, the device control unit 11 shifts the process to step S21. If it is not determined that the prescription should be sent, the device control unit 11 shifts the process to step S22. The determination of whether to send the prescription in the prescription generation step includes, for example, a procedure of determining that the prescription should be sent when the patient terminal T specifies that the prescription should be sent to a pharmacy.

[0136] [Step S21: Send prescription] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the prescription transmission unit 124. Then, the device control unit 11 executes processing to transmit data of the prescription generated in the prescription generation step by the prescription transmission unit 124 (step S21, prescription transmission step). The device control unit 11 moves the processing to step S22. It is preferable that the destination of the prescription data is the above-mentioned pharmacy.

[0137] Incidentally, patients with injuries or illnesses are thought to be more likely to ask medical institutions questions about appointments or medical treatment than those who are not worried about injuries or illnesses. Furthermore, patients who are unfamiliar with the new medical treatment format provided by the system S of the present invention are expected to be more likely to ask questions about appointments and medical treatment in that format. Responding to such questions can require a great deal of work from medical institution staff. Furthermore, there is a concern that a flood of questions will result in patients having to wait longer for answers to their questions.

[0138] Although not essential, it is preferable that the management device 1 executes a series of processes related to automatic responses to questions (steps S22 to S24). This allows the management device 1 to provide patients with automatically generated answers to questions without requiring staff to spend time on them. In this case, the management device 1 provides answers without occupying staff time, thereby reducing the time patients have to wait for answers. In order to achieve a configuration separated by function, it is preferable that this series of processes be executed on a call center system different from the management device 1.

[0139] [Step S22: Determine whether a query has been received] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute the question receiving unit 125. Then, the device control unit 11 executes a process to determine whether a question regarding a reservation and / or medical treatment has been received from the patient terminal T by the question receiving unit 125 (step S22, question receiving step). If it is determined that a question has been received, the device control unit 11 proceeds to step S23. If it is not determined that a question has been received, the device control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S24.

[0140] [Step S23: Generate answer] The device control unit 11 cooperates with the device storage unit 13 to execute the answer generation unit 126. Then, the device control unit 11 executes a process in which the answer generation unit 126 generates an answer to the question determined to have been received in the question receiving step by processing using a large-scale language model (step S23, answer generation step). The device control unit 11 proceeds to step S24.

[0141] The answer generating step is realized by providing a prompt including at least the question determined to have been received in the question receiving step to the large-scale language model. Note that the prompt preferably includes the patient's attributes so that an answer according to the patient's attributes is generated.

[0142] [Step S24: Send response] The device control unit 11 cooperates with the device storage unit 13 and the device communication unit 14 to execute a process of transmitting the answer generated in the answer generation step to the patient terminal T involved in the question reception step (step S24, answer transmission step). The device control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S24.

[0143] In order to enable the patient to have a conversation with a human staff member, the answer sending step preferably further sends a link configured to send information indicating that the patient wishes to have a conversation with a human staff member. Also, in order to make it easier for the patient to explain the situation when asking a question about the automated response, the answer sending step preferably further sends a link configured to enable reference to the history of the automated response.

[0144] [Payment information registration step] The management process preferably includes a payment information registration step for registering payment information, which is information required for online payment of medical fees. The payment information is, for example, information about the credit card used by the patient for online payment. This allows the management device 1 to settle medical fees without going through an accounting system shared by a large number of people.

[0145] [Reservation change steps] The management process preferably includes a reservation change step in which, when a reservation change request (reservation change request) including at least the desired time slot is received from the patient terminal T, the reserved room and reserved time slot are changed using the same procedures as steps S1 to S6, a code corresponding to the changed reserved room and reserved time slot is obtained, and this code is sent to the patient terminal T together with information about room 2, which is the changed reserved room. This allows the management device 1 to automatically respond to reservation change requests from patients.

[0146] [Reservation status display step] In order to enable the medical personnel to grasp the reservation status, the management process preferably includes an appointment status display step of instructing the medical personnel terminal C to display the reservation status. The appointment status display step is realized by referring to the appointment status database 131.

[0147] [Receipt sending step] In order to protect patient privacy and support infectious disease prevention measures even when sending receipts related to medical fees, it is preferable that the management process include a receipt sending step of sending receipts related to medical fees to the patient terminal T.

[0148] [Effects of the configuration of the system S of this embodiment] The system S of this embodiment has the above-described configuration, and the management device 1 can provide the patient with a reservation code, such as a personal identification number. This reservation code is a code that unlocks the electronic lock 3 installed in the reserved room 2 during the reserved time slot. Therefore, for example, a patient who has reserved the reserved room 2A can use the provided reservation code to unlock the electronic lock 3A installed in the reserved room 2A during the reserved time slot. Because the reservation code is a different code for each room 2 and time slot, it cannot unlock the electronic lock 3 installed in a room 2 other than the reserved room 2A, even during the reserved time slot. Therefore, the system S prevents anyone other than the patient associated with the reserved room 2A from unlocking the electronic lock 3A. This allows the system S to protect the patient's privacy and support infection control measures.

[0149] Furthermore, with the above-described configuration, the system S can provide the patient terminal T with room identification information related to the reserved room 2A via an image 22A such as a two-dimensional code. This allows the management device 1, which receives check-in information including the room identification information, to reliably identify that the patient has entered the reserved room 2A related to the patient's reservation. This prevents the system S from mistaking the patient who is guided to the room 2. In other words, the system S enables patients to receive medical treatment by meeting only the minimum number of staff members necessary.

[0150] [Main flowchart of medical interview process] 16 is a flowchart showing an example of a preferable flow of the medical interview process executed by the medical interview terminal 5 of this embodiment. The medical interview terminal 5 executes a series of processes related to the medical interview of the patient before medical treatment in steps S101 to S105.

[0151] [Step S101: Determine whether a patient has entered the room] The terminal control unit 51, in cooperation with the terminal input unit 55, performs processing to determine whether a patient has entered room 2 (step S101, entry determination step). For example, it may determine that a patient has entered room 2 based on an operation of the terminal input unit 55, or it may determine that a patient has entered room 2 based on a response input of information identifying the patient using the terminal input unit 55. Furthermore, it may determine that a patient has entered room 2 using a camera or the like, or it may determine that a patient has entered room 2 based on the unlocking of the electronic lock 3 or the opening and closing of the door of the entrance 21. However, the terminal control unit 51 may also determine that a patient has entered room 2 based on data received from the management device 1 in conjunction with reading an image 22 posted inside room 2 on the patient terminal T. If it is determined that a patient has entered room 2, the terminal control unit 51 proceeds to step S102.

[0152] [Step S102: Receive thread data] The terminal control unit 51 cooperates with the terminal storage unit 52 and the terminal communication unit 56 to execute the thread receiving unit 513. Then, the terminal control unit 51 receives thread data 521 associated with the patient card number of the identified patient from the management device 1 by the thread receiving unit 513 (step S102, thread data receiving step). Note that in the case of a first-time patient, thread data 521 does not yet exist, so new thread data 521 is created at this point. The terminal control unit 51 proceeds to step S103.

[0153] [Step S103: Start medical interview] The terminal control unit 51 executes the medical interview processing unit 511 in cooperation with the terminal storage unit 52, the terminal display unit 53, the terminal output unit 54, and the terminal input unit 55. Then, the terminal control unit 51 uses the medical interview processing unit 511 to inquire about the medical interview content in a thread in conjunction with the movement of the character image displayed on the terminal display unit 53 (step S103, medical interview processing step). At this time, sound is output from the terminal output unit 54 in conjunction with the movement of the character image. A plurality of predetermined medical interview contents are displayed in sequence in the thread, and the patient answers each medical interview content by inputting a response to the terminal input unit 55. The terminal control unit 51 moves the process to step S104.

[0154] [Step S104: Determine whether the medical interview has ended] The terminal control unit 51 performs a process in which the patient inputs answers to all of the plurality of pre-set medical interview contents through the medical interview processing unit 511, and determines whether the inquiries to the patient regarding the medical interview contents have been completed (step S104, medical interview completion determination step). The medical interview processing step continues until it is determined that the inquiries to the patient regarding the medical interview contents have been completed. When it is determined that the inquiries to the patient regarding the medical interview contents have been completed, the terminal control unit 51 moves the process to step S105.

[0155] [Step S105: Send thread data] The terminal control unit 51 cooperates with the terminal storage unit 52 and the terminal communication unit 56 to execute the thread sending unit 512. Then, the terminal control unit 51 causes the thread sending unit 512 to send thread data 521 used for the patient inquiry to the management device 1 (step S105, thread data sending step). This thread data includes the patient's response content as medical interview information, and the reception of the thread data by the management device 1 completes a series of processes related to the medical interview with the patient before medical treatment.

[0156] <Usage example> Fig. 17 is a flowchart showing an example of the flow of medical treatment using the system S of this embodiment (flow of system use). Fig. 18 is a diagram continuing from Fig. 17. Fig. 19 is a diagram continuing from Fig. 18. Fig. 20 is a diagram continuing from Fig. 19. Fig. 21 is a diagram continuing from Fig. 20. Below is an explanation of an example of use of the system S of this embodiment using Figs. 17 to 21.

[0157] 〔reservation〕 First, a patient makes a reservation using system S. The patient accesses management device 1, which is part of system S, via patient terminal T. The patient then inputs the desired reservation date (reservation time slot), medical department, etc. via patient terminal T. The patient terminal T transmits the input information to management device 1. Management device 1 receives the information. Then, management device 1 determines the reservation time slot (reservation time slot) and room (reserved room). Management device 1 obtains a code (reservation code) corresponding to the time slot and room from electronic lock 3. Then, management device 1 transmits reservation information such as the reservation time slot, reserved room, and reservation code. The information is transmitted to patient terminal T and related party terminal C. As a result, the patient and related party recognize the reservation information.

[0158] [Visiting the hospital] A patient visits a medical institution during a reserved time slot. There are multiple rooms 2 in a building B where the medical institution is located. The patient looks at the reserved room number sent to the patient terminal T and chooses the specific reserved room 2 from the multiple rooms 2. The patient then looks at the reservation code sent to the patient terminal T and unlocks the electronic lock 3 installed at the entrance 21 of the specific reserved room 2 with the code (reservation code). After unlocking the door, the patient enters the specific reserved room 2 and has the patient terminal T read the image 22 installed inside the room. The patient terminal T transmits check-in information including the room identification information provided by the image 22 to the management device 1. The management device 1 receives this information and registers the information in the device storage unit 13. The management device 1 then notifies the related party terminal C of the reception status, indicating that the patient is waiting in the reserved room. The medical party is aware of the reception status.

[0159] [Medical interview] The patient operates the medical interview terminal 5 installed in the room 2 into which the patient has entered. In response to this, the medical interview terminal 5 requests the management device 1 to transmit thread data 521, and upon receiving the request, the management device 1 transmits the thread data 521 associated with the patient to the medical interview terminal 5. Upon receiving the thread data 521, the medical interview terminal 5 starts interviewing the patient using a thread, and when the patient has finished inputting answers to all of the preset medical interview contents, transmits the thread data 521 to the management device 1. Upon receiving the thread data 521, the management device 1 stores the thread data 521 in the device storage unit 13, thereby updating the thread database 133.

[0160] [Medical Treatment] The medical staff member, who has recognized the reception status, moves to the patient's room 2 (reserved room). The patient moves to the examination room and receives medical treatment from the medical staff member.

[0161] 〔accounting〕 The patient terminal T then settles the medical fee after the fact using the credit card information registered by the patient in advance. The patient receives a receipt for the settlement via the patient terminal T.

[0162] [Returning home] The patient purchases medicine at a pharmacy and then goes home. The configuration of the system S of this embodiment allows the patient to receive medical treatment by meeting only the minimum number of staff members, such as medical professionals and pharmacy employees, from the time the patient arrives at the hospital until the time the patient goes home.

[0163] In the above embodiment, a configuration has been described in which the medical interview terminal 5 is provided separately from the patient terminal T. However, the medical interview terminal 5 may be realized by the patient terminal T. In this case, after the patient enters the room 2, the patient may use the patient terminal T as the medical interview terminal 5 to input answers to the medical interview contents.

[0164] In the above embodiment, the medical interview terminal 5 is installed in a room 2 with an electronic lock 3 at the entrance 21. However, the medical interview system according to the present invention is not limited to a configuration in which multiple patients who have made appointments wait in different rooms 2, and can also be used in a configuration in which multiple patients wait in a common waiting room, for example. In this case, one or more medical interview terminals 5 may be installed at the reception desk and handed to patients who visit the hospital.

[0165] It should be noted that within the scope of the concept of the present invention, those skilled in the art may conceive of various modifications and alterations. Therefore, it is understood that such modifications and alterations fall within the scope of the present invention. For example, even if a person skilled in the art appropriately adds, deletes, or modifies components of the above-described embodiment, or adds, omits, or modifies the conditions of a process, such modifications are also included within the scope of the present invention as long as they maintain the gist of the present invention. [Explanation of symbols]

[0166] S System 1 Management device 11 Device control section 111 Reservation Request Reception Department 112 Reservation Decision Department 113 Code Acquisition Department 114 Reservation Transmission Unit 115 Reservation Status Management Department 116 Check-in Department 117 Notification Department 13 Device storage 131 Reservation Status Database 132 Medical Treatment Database 14 Device communication unit Building B 2 rooms 21 Entrance 22 images 3. Electronic Lock 31 Electronic lock control unit 311 Code Management Department 312 Code Provision Department 313 Unlock instruction receiving unit 314 Unlocking section 32 Electronic lock / unlock unit 33 Electronic lock memory unit 331 Code List 34 Electronic Lock Communication Unit 35 Electronic lock input unit 4 Electronic lock management device 41 Lock management device control section 42 Lock management device storage section 421 Electronic Lock Unlocking Code Database 43 Lock management device communication unit 5. Medical interview terminal 51 Terminal control unit 511 Medical interview processing unit 512 Thread Transmitter 513 Thread Receiver 52 Terminal memory section 521 Thread Data 53 Terminal display 54 Terminal Output Unit 55 Terminal input section 56 Terminal communication unit C. Stakeholder terminal N Network T Patient terminal

Claims

1. a medical interview terminal operated by a patient undergoing a medical interview; a management device that manages the medical interview information input by the medical interview terminal, The medical interview terminal includes: a display unit that displays a character image; a medical interview processing unit that asks the patient about the contents of a medical interview in conjunction with the movement of the character image displayed on the display unit; an input unit that accepts input of a patient's response to the medical interview content; a communication unit that transmits the answer input information to the management device as the medical interview information.

2. The medical interview system according to claim 1 , wherein the medical interview processing unit asks the patient about the medical interview content by at least one of voice and display.

3. The medical interview system according to claim 1 , wherein the medical interview processing unit displays the medical interview content and the information of the patient's input answers to the medical interview content on the display unit in different threads for each patient.

4. the management device stores the thread data in association with each patient; The medical interview system according to claim 3, wherein the medical interview processing unit reads out data of the thread corresponding to the patient from the management device and displays it on the display unit, thereby enabling the input of patient responses from the patient via the input unit from the continuation of the thread.

5. 2. The medical interview system according to claim 1, wherein when the medical interview processing unit receives answers input from the patient via the input unit for all of the predetermined medical interview contents, the medical interview processing unit displays a list of the input answers as the medical interview information on the display unit.

6. 2. The medical interview system according to claim 1, wherein the management device stores patient-identifying information for each patient, and identifies the patient based on the medical interview information and the patient-identifying information received from the medical interview terminal.

7. an electronic lock that is provided in each of a plurality of rooms into which different patients enter before medical treatment, locking the entrance to the room and unlocking it with a different code for each room and time period; The medical interview system according to claim 1 , wherein the medical interview terminal is provided in each of the plurality of rooms.

8. a display unit that displays a character image; a medical interview processing unit that asks the patient about the contents of a medical interview in conjunction with the movement of the character image displayed on the display unit; an input unit that accepts input of a patient's response to the medical interview content; and a communication unit that transmits the answer input information to a management device as medical interview information.

Images