Medical interview system and medical interview terminal

Abstract

To provide a medical interview system and a terminal for medical interview that enable a patient to easily answer questions about the contents of a medical interview. [Solution] The medical interview terminal 5 is operated by a patient undergoing 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 about the contents of the medical interview in conjunction with the movement of the character image displayed on the terminal display unit 53. The terminal input unit 55 accepts the patient's response input to the medical interview contents. The terminal communication unit 56 transmits the response input information to a management device as medical interview information.

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, in the interview conducted before treatment, patients generally fill out a paper questionnaire prepared by the patient using a writing instrument. In addition to personal information such as the patient's name and date of birth, various information such as the patient's condition and whether or not they are taking medication is written on the questionnaire. Filling out such a questionnaire is troublesome, and is a heavy burden especially for patients who are not in good condition, so a system that allows patients to easily answer the questionnaire is desired. In addition, it is also common to answer the questionnaire online after making a reservation through a reservation system. There are a certain number of patients who do not fill out the questionnaire at the time of reservation, and the questionnaire content (condition, etc.) at the time of reservation and the questionnaire content (condition, etc.) at the time of actual visit may change over time, so a system that allows patients to easily answer the questionnaire when visiting is desired.

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

[0004] [Patent Document 1] JP 2014-89650 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, when the patient is elderly, for example, it is 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 enable a patient to easily answer questions about the contents of a medical interview. [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 about the contents of 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 contents. The communication unit transmits information of the response input to the management device as the medical interview information.

[0008] According to this configuration, the character image is displayed on the medical interview terminal, and the patient can be asked about the medical interview contents in conjunction with the movement of the character image, so that the patient can easily understand the medical interview contents. Therefore, the patient can easily answer the medical interview contents.

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

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

[0011] The medical interview processing unit may cause the display unit to display the contents of the medical interview and information of the responses input by the patients to the medical interview contents in different threads for each patient.

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

[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 making it possible to accept an answer input from the patient from the continuation of the thread by the input unit.

[0014] With this configuration, the data of the thread corresponding to the patient is read from the management device, and the patient can continue inputting answers from the thread, so it is possible to omit re-inputting answers to information that was previously input in the thread for each patient. Therefore, it becomes 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 cause a list of the input answers to be displayed on the display unit as the medical interview information.

[0016] With this configuration, the patient's responses to all the preset questions are displayed in a list on the display as easy-to-understand information. If this list of questions is directly transferred to the medical record, the burden on medical personnel can be reduced.

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

[0018] According to this configuration, the patient can be identified based on the interview information received from the interview terminal and the information identifying the patient, and the patient can be accepted for examination. 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, locks the entrance to the room, and is unlocked 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, in each of the multiple rooms whose entrances can be locked with electronic locks, patients who enter the room can easily use the interview terminal to answer questions about the medical interview. Also, since each of the multiple rooms is a private room, even if the medical interview is conducted by voice, the privacy of the patient can be prevented from being violated.

[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] According to this configuration, the character image is displayed on the medical interview terminal, and the patient can be asked about the medical interview contents in conjunction with the movement of the character image, so that the patient can easily understand the medical interview contents. Therefore, the patient can easily answer the medical interview contents. Effect 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 description of the drawings]

[0024] [Figure 1] FIG. 2 is a block diagram showing the hardware configuration of the system (diagnosis system) of the present embodiment. [Diagram 2] 2 is a block diagram showing a hardware configuration and a software configuration of a management device; [Diagram 3] 1 is an example of data stored in a reservation status database. [Figure 4] 1 is an example of data stored in a medical care content database. [Diagram 5] 1 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 rooms are located. [Figure 7] 2 is a block diagram showing the hardware and software configurations of an electronic lock. FIG. [Figure 8] 1 is an example of data stored in a code list. [Figure 9] 13 is an example of data stored in an electronic lock unlocking code database. [Figure 10] 2 is a block diagram showing a hardware configuration and a software configuration of the inquiry terminal; FIG. [Figure 11A] FIG. 4 is a diagram showing an example of a display screen on a terminal display unit of the inquiry terminal. [Figure 11B] FIG. 11 is a diagram showing another example of the display screen on the terminal display unit of the inquiry terminal. [Figure 11C] FIG. 11 is a diagram showing another example of the display screen on the terminal display unit of the inquiry terminal. [Figure 12] 4 is a main flowchart showing an example of a preferable flow of a management process executed by the management device of the present embodiment. [Figure 13] This is a continuation from Figure 12. [Figure 14] This is a continuation from Figure 13. [Figure 15] This is a continuation from 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 from Figure 17. [Figure 19] This is a continuation from Figure 18. [Figure 20] This is a continuation from Figure 19. [Figure 21] This is a continuation from Figure 20. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Hereinafter, an example of an embodiment of the present invention will be described in detail 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 for locking the entrance of each of the rooms 2, and a network N for connecting the management device 1 and the electronic locks 3 so that they can communicate with each other. The management device 1 is capable of communicating 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 is further configured to include an electronic lock management device 4 for managing 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 each software component shown in Fig. 2 by each hardware component shown in Fig. 2. Then, the management device 1 executes a management process by each software component to guide a patient who has made a reservation to an examination room and perform treatment without going through a waiting room shared by a large number of people, while reducing the labor of staff and the waiting time of patients. The type of the management device 1 is not particularly limited. The type of the 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), and a read only memory (ROM).

[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 realizes the software components of the program of this embodiment executed by the management device 1, such as a reservation request receiving unit 111, a reservation decision unit 112, a code acquisition unit 113, a reservation transmission 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 content receiving unit 119, a medicine information receiving unit 120, a medical fee calculation unit 121, a bill transmission unit 122, a prescription generation unit 123, a prescription transmission unit 124, a question reception unit 125, and a response generation 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 to 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, a reservation 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 the multiple rooms 2. The reservation status includes information for identifying the patient, the reservation time period, 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 period 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 is 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 of the example shown in Fig. 3 stores a reservation status associated with a reservation ID "R0001", a reservation status associated with a reservation ID "R0002", a reservation status associated with a reservation ID "R0003", and the like.

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

[0035] Since the reservation status is stored in the reservation status database 131, the management device 1 can provide different codes for each time period obtained by referring to the code list 331, which will be described later, to patients who have reserved the same reserved room for different time periods. In the example shown in FIG. 3, the patient identified by the patient card number "12345" and the patient identified by the patient card number "67890" correspond to this. In addition, the management device 1 can provide different codes for each room obtained by referring to the code list 331, which will be described later, to patients who have reserved different reserved rooms for the same time period. In the example shown in FIG. 3, the patient identified by the patient card number "12345" and the patient identified by the patient card number "11223" correspond to this. In this way, the management device 1 can manage each room 2 as if it were a private room different from 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 medical care provided to the patient, information on medicines prescribed to the patient, medical fees to be charged to the patient, and information to identify the patient. In order to have a configuration separated by function, the medical care content database 132 may be stored in an electronic medical record system different from the management device 1. The information to identify the patient may be, for example, a patient card number. The format of the medical care provided to the patient, information on medicines prescribed to the patient, medical fees to be charged to the patient, and the like is not particularly limited. For convenience of retrieval and storage from the medical care content database 132, it is preferable that the above-mentioned data is stored in association with a medical care ID that identifies the data. In addition, the above-mentioned data may include various information related to the patient after visiting the hospital, such as the confirmation status of the health insurance card, the input status of the questionnaire, the accounting status, and the like.

[0037] Incidentally, the medical details stored in the medical details database 132 are personal information and therefore require a high level of confidentiality. In addition, the medical details stored in the medical 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 a database, partly or entirely, 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. In addition, 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 will not become inaccessible due to a failure in 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 of the example shown in Fig. 4 stores data associated with a medical care ID "M0001", data associated with a medical care ID "M0002", and the like.

[0040] The medical ID "M0001" is associated with the medical treatment details "Consultation, ..." of the patient identified by the medical card number "12345," the medicine information prescribed for the patient "Dexamethasone cipesilate capsule topical, once a day, for 14 days," and the medical fee "1,100 yen" billed to the patient. The medical ID "M0002" is associated with the medical treatment details "Hay fever patch test, ..." of the patient identified by the medical card number "67890," the medicine information prescribed for the patient "Fluticasone propionate nasal spray, twice a day, for 14 days," and the medical fee "4,600 yen" billed to the patient.

[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 medicine information and provide it to the patient.

[0042] (Large-scale language models) The large-scale language model of the present embodiment is not particularly limited as long as it is a language model that executes natural language processing to generate a response to an input prompt. The "language model" referred to here is a type of probability model used in natural language processing, and is a model for probabilistically predicting how likely a given word or sentence is to occur as natural language. Specifically, the language model predicts the next sentence by calculating the occurrence probability of a given sentence, etc., comparing the occurrence probability of multiple sentences, etc. In this way, the language model can automatically generate the most likely sentence based on the context related to the given sentence, etc. The large-scale language model may be stored in a device different from the management device 1 (for example, a device on a call center system) so as to have a configuration separated by function.

[0043] The large-scale language model of the present 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, as exemplified by ChatGPT-3.5 and ChatGPT-4 from OpenAI, LLaMa from Meta AI, etc. With such a large-scale language model, when a prompt including a question related to an appointment and / or medical treatment is input, the management device 1 can generate an appropriate answer to the question.

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

[0045] (Thread Database 133) The thread database 133 stores data of threads (thread data) used when conducting a medical interview with a patient. The thread data includes the contents (thread contents) and names (thread names) of threads conducted in a chat format in which the contents of the medical interview are inquired one by one 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 the thread data of each patient in association with each patient. The thread contents include information on the contents of the patient's answers to the medical interview contents (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, like the medical care content database 132, it is preferable that a part or all of the thread data is stored in a database configured by 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 appointment card number "12345", data associated with patient appointment card number "67890", data associated with patient appointment card number "11223", and the like.

[0047] In the case of a first-time patient, since there is no thread data used in previous interviews, new thread data is created and stored in thread database 133 in association with the patient's assigned 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 interviews is read from thread database 133 and used, and thread data including the patient's new answer input information is overwritten in thread database 133. This makes it possible to omit re-entering answers for information previously input in each patient's thread. This makes it even easier for returning patients to answer questions.

[0048] [Device communication section 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 a building B in which a room 2 is located. In the building B of the system S of this embodiment, a plurality of rooms 2 serving as waiting rooms where patients wait for treatment are provided (for example, reference numbers 2A to 2H in FIG. 6). The building B is not particularly limited. The building B may be, for example, a medical facility exemplified by a hospital or clinic, or a large commercial facility. In addition to the room 2, various other rooms may be provided in the building B. Other parts provided in the building B include, for example, an examination room in which examination equipment is installed, a treatment room in which medical equipment related to treatment is installed, and a storeroom in which 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 installed on the outside of the medical institution. Room 2 preferably has an inner door installed on the inside of the medical institution through which medical personnel can enter. Entrance 21 of 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 can wait for their consultation.

[0051] An image 22 is posted inside the room 2, providing room identification information for identifying the room 2 relating to the room. The room identification information provided by the image 22 is not particularly limited as long as it is information for identifying the room 2. The image 22 provides the room identification information via, for example, a two-dimensional code (e.g., reference symbol 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 the image 22 inside the room 2, the patient terminal T can provide the management device 1 with information that reliably indicates that the patient has entered the room 2. This prevents the patient from being mixed up.

[0052] Furthermore, an interview terminal 5 is installed inside each room 2 to be operated by a patient who enters the room. A different interview terminal 5 (for example, reference symbol 5A in FIG. 6) is installed in each room 2, and each patient who enters each room 2 can undergo an interview using a different interview terminal 5. Each interview terminal 5 can communicate with the management device 1 by wire or wirelessly, and interview information inputted by each interview terminal 5 is transmitted to the management device 1 and managed in 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 be provided to lock the entrance of the examination room and / or the medical treatment room. This allows the system S to realize automated private examinations using the examination room and / or the medical treatment room as a private room. The type of the 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 code for each time period to the management device 1. The type of the electronic lock 3 may be, for example, a smart lock or the like 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 essential, 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 input 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, and the like.

[0056] [Electronic lock control unit 31] The electronic lock control unit 31 includes a central processing unit (CPU), a random access memory (RAM), a 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 an electronic lock locking / unlocking unit 32, an electronic lock storage unit 33, an electronic lock communication unit 34, and / or an electronic lock input unit 35 as necessary. The electronic lock control unit 31 then realizes software components executed by the electronic lock 3, such as a code management unit 311, a code provision unit 312, an unlocking instruction receiving unit 313, and an 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 in which at least the medical institution treats patients, divided into a given time unit such as one hour. In order to allow some leeway in the timing of visits, ensure sufficient treatment time, and make it easy for patients to understand the time period, it is preferable that the "given time unit" is one hour. The code managed by the code management unit 311 is preferably composed of elements that can be input from the electronic lock input unit 35. The code is, for example, a PIN 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 the code providing unit 312 is 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 the viewpoint of security, 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. The reception may be reception of communication via the electronic lock communication unit 34, or reception of input via the electronic lock input unit 35. After receiving the unlock instruction, the unlock instruction receiving unit 313 transfers the process 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 collates 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 / unlock unit 32 controls the electronic lock 3 between a locked state and an unlocked state in response to control from the electronic lock control unit 31. There is no particular limitation on the type of the electronic lock / unlock unit 32. The type of the electronic lock / unlock 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 memory 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 a time period with a code for unlocking the electronic lock 3 during that time period. The code is preferably composed of elements that can be input from the electronic lock input unit 35. The code is, for example, a PIN number consisting of multiple numbers. The code corresponding to the same time period is different for each electronic lock 3. In other words, the code corresponding to the same time period is different for each room 2. The code is 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. In the example shown in Fig. 8, codes corresponding to time periods such as a code "112233" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" in the time period "2023 / 12 / 29 10:00-11:00", a code "456456" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" in the time period "2023 / 12 / 29 11:00-12:00", and a code "789078" for unlocking the electronic lock 3 identified by the electronic lock ID "K0001" in the time period "2023 / 12 / 29 12:00-13:00" are stored.

[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 or not it has received a code corresponding to the time period. Then, when a different code is received for each room 2 and time period, the electronic lock 3 can unlock the entrance 21 of the room 2. The management device 1 that 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 made a reservation 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 in a time period different from the time period, for example, "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 can connect the electronic lock 3 to the network N and communicate with the management device 1, etc. An example of the electronic lock communication unit 34 is a wireless communication device that connects to a wireless LAN.

[0068] Although not essential, 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 instruction 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 so that the patient or the like can input an unlocking command including a code. The electronic lock input unit 35 is realized, for example, by a keypad or a touch panel for inputting numbers, symbols, letters, etc. The electronic lock input unit 35 may also be realized by an optical reader that reads various optically readable codes, exemplified by two-dimensional codes, bar codes, codes consisting of letters and / or numbers, etc.

[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 in which a program executed by the lock management device control unit 41 and an electronic lock unlocking code database 421 are stored, 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 the same as 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, which is a process for managing the electronic lock 3 that locks the room 2 and the electronic lock unlocking code database 421, by 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 referring to 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 for unlocking the electronic lock 3 that locks the 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. As shown in FIG. In the example shown in Figure 9, codes corresponding to time periods are stored, such as the code "112233" to unlock the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 10:00-11:00", the code "456456" to unlock the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 11:00-12:00", the code "789078" to unlock the electronic lock 3 identified by the electronic lock ID "K0001" during the time period "2023 / 12 / 29 12:00-13:00", and the code "445566" to unlock the electronic lock 3 identified by the 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 or not a code corresponding to the room 2 and the time period has been received. Then, when a code different for each room 2 and time period is received, the electronic lock 3 can unlock the entrance 21 of the room 2. The management device 1 provided with 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 the 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 in a time period different from 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 the electronic lock ID "K0002", even if it is during the same time period as the patient in question, for example, "11:00-12:00".

[0073] [Stakeholder terminal C] There is no particular limitation on the type of the related party terminal C. The related party terminal C is, 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 a process of notifying the medical practitioner using the related party terminal C of the reception of the notification via a screen display and / or a voice output, etc.

[0074] [Network N] The type of the 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 interview terminal 5. The type of the network N is, for example, the Internet, a mobile phone network, a wireless LAN, etc.

[0075] [Patient terminal T] The type of the patient terminal T is not particularly limited. The patient terminal T is, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, etc. The patient terminal T is configured to execute a process of transmitting a reservation request to the management device 1, a process of receiving, storing, and displaying information related to the reservation transmitted from the management device 1, a process of transmitting room identification information, etc. to the management device 1, etc.

[0076] [Medical interview terminal 5] FIG. 10 is a block diagram showing the hardware configuration and the software configuration of the medical interview terminal 5. The medical interview terminal 5 realizes each software component shown in FIG. 10 by each hardware component shown in FIG. 10. The type of the medical interview terminal 5 is not particularly limited. The type of the medical interview terminal 5 may be, for example, a personal computer, a tablet terminal, etc. The medical interview terminal 5 includes 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, etc. as its hardware components. However, the medical interview terminal 5 may not be configured to include all of these units, and may be configured such that at least some of them are not included in the medical interview terminal 5. For example, the terminal control unit 51 and the terminal memory unit 52 may be realized by another server. In this case, the medical interview terminal 5 may be configured to include only the terminal display unit 53, the terminal output unit 54, the terminal input unit 55, and the terminal communication unit 56 that perform input and output, and to 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), and a Read Only Memory (ROM).

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

[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 through the terminal input unit 55, and the input response information is displayed on the terminal display unit 53. In this way, the medical interview processing unit 511 can inquire the patient about the medical interview content by at least one of voice and display. The medical interview processing unit 511 displays the medical interview content and the input response information of the patient to the medical interview content on the terminal display unit 53 in a different thread for each patient.

[0081] The character image is a so-called avatar, and is an image of a character with a human or animal motif in a virtual space. The character image is displayed so that a part of the body such as the mouth moves in accordance with the timing of display of the medical interview contents 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 inquires of the patient about the medical interview contents 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 inquired about the medical interview contents in conjunction with the movement of the character image, so that the medical interview contents are easy for the patient to understand. Therefore, the patient can easily answer the medical interview contents.

[0082] The medical interview contents displayed sequentially in the thread can be realized using a large-scale language model. This large-scale language model is exemplified by ChatGPT-3.5 and ChatGPT-4 by OpenAI, LLaMa by Meta AI, etc., but is not particularly limited as long as it is a language model that executes natural language processing to generate a response to an input prompt. By using such a large-scale language model, when a prompt including a patient's response to the medical interview contents 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 answers input 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 finishes inquiring of the patient about the contents of the medical interview, 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 an interview with 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 is 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, etc., input by the patient at the start of the interview. In this case, thread data 521 associated with the patient's appointment card number of the identified patient is read from management device 1 and stored in terminal storage unit 52. In this way, management device 1 stores the appointment card number, which is information for identifying the patient, for each patient, and can identify the patient based on the interview information and the appointment card number received from interview terminal 5. However, the patient may input the appointment card number as an answer at the start of the interview. In this case, if even one of the name, date of birth, etc., associated with the appointment card number is different from the information input as an answer, a notification to that effect may be provided. In addition, the patient may be identified by various biometric authentication methods such as face recognition and voice recognition, or by reading an insurance card, etc.

[0087] [Terminal storage unit 52] The terminal storage unit 52 is a device in which data and / or files are stored, and has a storage unit that non-temporarily stores data using a hard disk, a semiconductor memory, a recording medium, a memory card, etc. The terminal storage unit 52 also stores a program 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 an 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. The terminal display unit 53 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, for example, by a speaker or the like. The terminal output unit 54 outputs sound in conjunction with the movement of the character image displayed by the terminal display unit 53, so that the terminal output unit 54 can ask the patient 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 contents of the medical interview. 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 can connect the interview terminal 5 to the network N and communicate with the management device 1, etc. An example of the terminal communication unit 56 is a wireless communication device that connects 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, and the like.

[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 the 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] Thread name display area 533 displays the thread name of the thread displayed in 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 thread database 133 together with the contents of the thread displayed in thread display area 532 in association with the patient card number. Therefore, when the contents of the thread corresponding to each patient are read from thread database 133, the thread name is also read and displayed in thread name display area 533. Note that the thread name displayed in thread name display area 533 cannot be modified on the screen.

[0095] In the thread display area 532, a plurality of medical interview contents 532A, 532B, ... are displayed in sequence. The character image 531A in the character display area 531 moves in conjunction with the display timing of each medical interview content 532A, 532B, ..., so that the patient can receive the medical interview feeling as if the character is talking to him / her. The medical interview contents may include at least one of the patient's name, date of birth, sex, body temperature, health condition of family members living together, symptoms, whether or not they are taking medication, whether or not they have allergies, and the form of the desired medicine. However, the medical interview contents are not limited to these, and any item can be queried to the patient as the medical interview contents. Moreover, each item of the medical interview contents may be predetermined or may be arbitrarily set.

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

[0097] When the patient's answer input to the answer input area 534 is accepted for all the preset 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 transmitted to the management device 1 and stored in the thread database 133, thereby realizing transmission of the 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 chart (electronic medical chart), the burden on medical practitioners can be reduced. However, the configuration is not limited to manual transcription of the medical interview information, and the management device 1 may automatically transcribe the medical interview information.

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

[0099] Fig. 11B and Fig. 11C are diagrams showing other examples of the display screen on the terminal display unit 53 of the interview terminal 5. Fig. 11A shows an example of the display screen of a personal computer or a tablet terminal, while Fig. 11B and Fig. 11C show an example of the display screen of a mobile terminal. Fig. 11B and Fig. 11C show a display example when the display screen is turned vertically, but when the display screen is turned horizontally, the arrangement of each area in 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. Descriptions of each area are omitted as they are similar to those in Fig. 11A. However, if the display screen is small, the number of characters 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. Descriptions of each are omitted because they are similar to those in FIG. 11A. In this example, the character display area 531 and the thread display area 532 overlap in part or in whole, and threads are displayed so as to overlap the character image 531. This allows many contents to be displayed even if the display screen is small. In this case, the contents of the medical interview are 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 contents of the medical interview.

[0102] [Main Flowchart of Management Processing] Fig. 12 is a main flow chart 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 to the patient terminal T together with information on the reserved rooms 2, thereby guiding each patient whose reservation time slots overlap to another 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 executes the reservation request receiving unit 111 in cooperation with the device storage unit 13 and the device communication unit 14. Then, the device control unit 11 executes a process of determining whether a reservation request (reservation request) including at least a desired time period 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 moves the process to step S2. If it is determined that a reservation request has not been received, the device control unit 11 moves the process 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 period, such as a medical department and a person in charge desired by the patient, in addition to the desired time period.

[0105] [Step S2: Determine whether a reservation is available during the desired time slot] The device control unit 11 executes 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 of referring to the reservation status database 131 by the reservation decision unit 112 to determine 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 possibility determination step). If it is determined that the reservation is possible, the device control unit 11 moves the process to step S3. If it is not determined that the reservation is possible, the device control unit 11 notifies the patient terminal T involved in the reservation request receiving step that the 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 enables the patient to request another reservation for another 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 further refer to information other than the desired time period, such as closed days, medical department, and the patient's desired 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 decides a reserved time slot and a 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 is a room 2 that is to be allocated to a reservation for the reserved time slot out of the multiple rooms 2. The device control unit 11 moves the process to step S4.

[0108] [Step S4: Get the code from the electronic lock] The device control unit 11 executes the code acquisition unit 113 in cooperation with the device memory unit 13 and the device communication unit 14. Then, the device control unit 11 executes a process of acquiring 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, using the code acquisition unit 113 (step S4, code acquisition step). The "code for the reserved time slot" here is a 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 of sending information related to the reservation decided in the reservation decision step to the patient terminal T related to the reservation request receiving step by the reservation sending unit 114 (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 moves the process 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 related to the reservation to the medical personnel terminal C in addition to the patient terminal T.

[0111] [Step S6: Store information related to reservation] The device control unit 11 cooperates 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 moves the process 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 has transmitted the room identification information. Through this series of processes, when the management device 1 receives room identification information, etc., provided in the reserved room and identifying the reserved room, transmitted from the patient terminal T of the patient who has entered the reserved room 2, the management device 1 notifies the related party terminal C that the patient is waiting in the reserved room. In this way, the management device 1 of this embodiment allows each patient to wait in a number of rooms 2 that is greater 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. In this way, the management device 1 of this embodiment can prevent patients who have made a reservation from having to wait unnecessarily.

[0113] [Step S7: Determine whether check-in 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 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 check-in information has been received, the device control unit 11 moves the process to step S8. If it is determined that the check-in information has not 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 specifying information, information specifying the patient, etc. The room specifying information in the check-in step is, for example, information acquired by reading an image 22 posted in the reserved room 2 with the patient terminal T.

[0115] (Regarding confirmation of health insurance card, etc.) The management device 1 preferably executes a series of processes for checking various documents required for medical treatment, such as health insurance cards. The processes include a process of referring to information on the checking status of various documents stored in the device storage unit 13, and proceeding with the checking procedure for documents that have not been checked. "Various documents required for medical treatment" includes, for example, various documents that are checked monthly, such as health insurance cards, My Number cards with registered health insurance card usage, and ceiling application certificates related to the high-cost medical care system. "Checking procedures" include, for example, a procedure for reading health insurance card information on My Number cards using a My Number card reader, a procedure for sending instructions to medical institution staff to check the documents, and the like.

[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 (step S8, notification step) by the notification unit 117. 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 enable 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 medical 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 unique to medical treatment at medical institutions, such as the number of doctors and other medical personnel being fewer than the number of patients receiving treatment during the scheduled time slot, and the time required for treatment may be 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 relation to the above, although this is 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 step, which is 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 and receives treatment in an appropriate room based on the extended time slot, extended room, and extension time 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 by 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 transfers the process to step S10. If it is not determined that a reservation extension is necessary, the device control unit 11 transfers the process to step S13.

[0121] In the extension necessity determination step, the procedure for determining whether the reservation extension is necessary is not particularly limited. In order to enable automatic extension, the procedure preferably includes a procedure for determining that the reservation extension is necessary when, for example, the time remaining until the end of the reservation time slot for a patient who has entered the reserved room falls below a given time, and information indicating that the medical treatment for the patient has ended has not been received from the related party terminal C. In addition, in order to enable extension by the medical treatment related party, the procedure preferably includes a procedure for determining that the reservation extension is necessary when an instruction to extend the reservation 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 through 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 following the current reservation time slot, and the extended room is set to the same room as the reserved room as far as possible.

[0123] [Step S11: Obtain the code from the electronic lock] The device control unit 11 executes the code acquisition unit 113 in cooperation with the device storage unit 13 and the device communication unit 14. 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 reservation extension execution step, from the electronic lock 3 that locks the entrance 21 of the extension room related to the reservation extension execution step, using the code acquisition unit 113 (step S11, extension code acquisition step). The "extension time period code" here is a 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 moves the process to step S13.

[0125] Although not essential, it is preferable that the management device 1 executes a series of processes related to database creation of medical treatment details and billing for medical fees (steps S13 to S21). This allows the management device 1 to bill patients for medical fees not only in the process of booking a medical treatment and treating the patient, but also in the process of billing for medical fees without the patient having to go through a waiting room for accounting, which is shared by a large number of patients. This also allows the management device 1 to reduce staff labor and patient waiting time not only in the process of booking a medical treatment and treating the patient, but also in the procedure of billing for medical fees. In order to have a configuration separated by function, it is preferable that the series of processes is executed on an electronic medical record system different from the management device 1.

[0126] The series of processes preferably includes processes related to issuing a prescription (steps S15 to S16 and steps S20 to S21). In this way, the management device 1 can ensure that patients can purchase medicine based on a prescription without having to go through a waiting room for payment shared by a large number of people, not only in the process from booking a medical appointment to receiving medical treatment, but also in the procedure for providing a prescription. In addition, with the above-mentioned configuration, the management device 1 can reduce the labor of staff and the waiting time of patients, not only in the process from booking a medical appointment to receiving medical treatment, but also in the procedure for 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 details receiving unit 119. Then, the device control unit 11 executes a process to determine whether the medical treatment details have been received by the medical treatment details receiving unit 119 (step S13, medical treatment details receiving step). If it is determined that the medical treatment details have been received, the device control unit 11 transfers the process to step S14. If it is determined that the medical treatment details have not been received, the device control unit 11 transfers 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 stored in the medical care details database 132 in association with information identifying the patient, information indicating the timing of medical care, etc. 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 transfers the process to step S16. If it is determined that the information has not been received, the device control unit 11 transfers the process to step S17.

[0130] [Step S16: Store drug information] The device control unit 11 executes a process of storing the medicine information received in the medicine information receiving step in the medical treatment content database 132 by the medicine information receiving unit 120 (step S16, medicine information storage step). The device control unit 11 moves the process to step S17. In the medicine information storage step, the medicine information is stored in the medical treatment content database 132 in association with information for identifying the patient, information indicating the timing of medical treatment, etc. Note that, in order to maintain confidentiality of the medicine information and improve its reliability, if a part or all of the medical treatment content database 132 is realized by the blockchain technology, the medicine information is preferably stored in the medical treatment content database 132 realized by the 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 or not to calculate a medical fee by the medical fee calculation unit 121 (step S17, medical fee calculation determination step). If it is determined that a calculation should be performed, the device control unit 11 shifts the process to step S18. If it is determined that a calculation should not be performed, the device control unit 11 shifts the process to step S20.

[0132] The process of determining whether or not to calculate the medical fee in the medical fee calculation determination step includes, for example, a procedure of determining that the medical fee will 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 of calculating 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 the medical fees stored in the device storage 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 transmission unit 122. Then, the device control unit 11 executes a process of transmitting an invoice requesting the medical fee calculated in the medical fee calculation step to the patient terminal T by the invoice transmission unit 122 (step S19, invoice transmission step). The device control unit 11 shifts the process to step S20.

[0135] [Step S20: Determine whether to send the prescription] The device control unit 11 executes the prescription generation unit 123 in cooperation with the device storage unit 13 and the device communication unit 14. Then, the device control unit 11 executes a process of determining whether to send a prescription by 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 by the prescription generation unit 123 based on the drug information stored in the drug information storage step. Then, the device control unit 11 transfers the process to step S21. If it is not determined that the prescription should be sent, the device control unit 11 transfers 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 is instructed to send the prescription 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 a process of transmitting 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 process to step S22. It is preferable that the destination of the prescription data is the above-mentioned pharmacy.

[0137] Incidentally, it is believed that patients with injuries or illnesses are more likely to ask questions of medical institutions about appointments or medical treatment than those who are not worried about injuries or illnesses. In addition, it is expected that patients who are not familiar with the new medical treatment format provided by the system S of the present invention are more likely to ask questions about appointments and medical treatment in that medical treatment format. Responding to such questions can require a great deal of effort from medical institution staff. In addition, 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 making staff spend time on them. In this case, the management device 1 provides answers without occupying staff time, thereby reducing the time that patients wait for answers. In order to achieve a configuration separated by function, it is preferable that the series of processes is executed on a call center system different from the management device 1.

[0139] [Step S22: Determine whether a question 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 related to 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 moves the process to step S23. If it is determined that a question has not 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 of generating an answer to the question determined to have been received in the question receiving step by processing using a large-scale language model with the answer generation unit 126 (step S23, answer generating step). The device control unit 11 shifts the process 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 attributes of the patient so as to generate an answer according to the attributes of the patient.

[0142] [Step S24: Send reply] 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 generating step to the patient terminal T related to the question receiving step (step S24, answer transmitting 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 allow 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 a desire 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 automatic response, the answer sending step preferably further sends a link configured to enable reference to the history of the automatic 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 on a credit card used by a 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 of, when a reservation change request (reservation change request) including at least the desired time slot is received from the patient terminal T, changing the reserved room and reserved time slot by the same procedures as steps S1 to S6, obtaining a code corresponding to the changed reserved room and reserved time slot, and transmitting this code together with information on room 2, which is the changed reserved room, to the patient terminal T. This allows the management device 1 to automatically respond to the reservation change request from the patient.

[0146] [Reservation status display step] In order to allow the medical practitioner to grasp the reservation status, the management process preferably includes an appointment status display step of instructing the medical practitioner 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 includes 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] Since the system S of this embodiment has the above-mentioned configuration, the management device 1 can provide the patient with a reservation code, exemplified by a PIN number or the like. This reservation code is a code for unlocking the electronic lock 3 installed in the reserved room 2 during the reserved time period. Therefore, for example, a patient who has reserved the reserved room 2A can unlock the electronic lock 3A installed in the reserved room 2A during the reserved time period using the reservation code provided. Since the reservation code is a different code for each room 2 and time period, the electronic lock 3 installed in a room 2 other than the reserved room 2A cannot be unlocked even during the reserved time period. 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 support protection of the patient's privacy and measures against infectious diseases.

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

[0150] [Main flow chart of medical interview process] 16 is a flowchart showing an example of a preferable flow of the interview process executed by the interview terminal 5 of this embodiment. The interview terminal 5 executes a series of processes related to the interview with 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 cooperates with the terminal input unit 55 to perform a process of determining whether the patient has entered the room 2 (step S101, entry determination step). For example, the terminal control unit 51 may determine that the patient has entered the room 2 based on the operation of the terminal input unit 55, or may determine that the patient has entered the room 2 based on the input of information identifying the patient using the terminal input unit 55. The patient's entry may be determined by a camera or the like, or may be determined 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 determine that the patient has entered the room 2 based on data received from the management device 1 in conjunction with the reading of the image 22 posted in the room 2 by the patient terminal T. When it is determined that the patient has entered the room 2, the terminal control unit 51 moves the process 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, since the thread data 521 does not yet exist, the thread data 521 is newly created at this point. The terminal control unit 51 moves the process 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 of the patient about the medical interview content in the 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 medical interview contents set in advance 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 is completed] The terminal control unit 51 performs a process of determining whether the patient has inputted answers to all of the multiple medical interview contents set in advance and the inquiry to the patient regarding the medical interview contents has been completed by the medical interview processing unit 511 (step S104, medical interview completion determination step). The medical interview processing step continues until it is determined that the inquiry to the patient regarding the medical interview contents has been completed. When it is determined that the inquiry to the patient regarding the medical interview contents has been completed, the terminal control unit 51 shifts 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 transmission unit 512. Then, the terminal control unit 51 transmits thread data 521 used for the patient inquiry to the management device 1 by the thread transmission unit 512 (step S105, thread data transmission step). This thread data includes the patient's answer content as interview information, and the series of processes related to the interview with the patient before medical treatment is completed by the management device 1 receiving the thread data.

[0156] <Usage example> Fig. 17 is a flowchart showing an example of a 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, an explanation is given 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 constitutes 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 period. A building B in which the medical institution is located has multiple rooms 2. The patient sees the reserved room sent to the patient terminal T and visits the specific room 2 that is the reserved room from the multiple rooms 2. The patient then sees the reservation code sent to the patient terminal T and unlocks the electronic lock 3 installed at the entrance 21 of the specific room 2 that is the reserved room with the code (reservation code). After unlocking, the patient enters the specific room 2 that is the reserved room and has the patient terminal T read the image 22 installed in 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 that the patient is waiting in the reserved room. The medical treatment related party recognizes the reception status.

[0159] [Medical interview] The patient operates the interview terminal 5 installed in the room 2 where the patient has entered. In response to this, the 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 interview terminal 5. The interview terminal 5 that has received the thread data 521 starts interviewing the patient using a thread, and when the patient has finished inputting answers to all of the preset interview contents, transmits the thread data 521 to the management device 1. The management device 1 that has received the thread data 521 updates the thread database 133 by storing the thread data 521 in the device storage unit 13.

[0160] [Medical Treatment] The medical staff, who recognizes 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.

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

[0162] [Returning Home] The patient purchases medicine at the pharmacy. Then, the patient returns home. With the configuration of the system S of this embodiment, the patient can receive medical treatment by only meeting the minimum number of staff members, namely medical professionals and pharmacy employees, from the time of arrival at the hospital to the time of returning home.

[0163] In the above embodiment, a configuration has been described in which the interview terminal 5 is provided separately from the patient terminal T. However, the 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 interview terminal 5 to input a response to the interview content.

[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 can be used not only in a configuration in which multiple patients who have made reservations wait in different rooms 2, but also in a configuration in which multiple patients wait in a common waiting room. In this case, one or multiple 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, a person skilled in the art may come up with various modifications and alterations. 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 the design of the above-described embodiment, or adds, omits, or modifies the conditions of a process, these modifications and alterations are included in the scope of the present invention as long as they include the gist of the present invention. [Explanation of symbols]

[0166] S System 1 Management device 11 Device control section 111 Reservation request receiving department 112 Reservation Decision Department 113 Code Acquisition Department 114 Reservation Transmission Unit 115 Reservation Status Management Department 116 Check-in Section 117 Notification Department 13 Device storage 131 Reservation status database 132 Medical Treatment Database 14 Device communication section B Building 2 rooms 21 Entrance 22 images 3. Electronic Lock 31 Electronic lock control unit 311 Code Management Department 312 Code Provision Department 313 Unlock command 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 unit 54 Terminal output section 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 to be interviewed; a management device for managing the medical interview information inputted by the medical interview terminal, The interview terminal includes: A display unit that displays a character image; a medical interview processing unit that asks the patient about a medical interview content in conjunction with the movement of the character image displayed on the display unit; an input unit for receiving an 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; an electronic lock is provided in each of a plurality of rooms into which different patients enter before medical treatment, the electronic lock locks the entrances of the rooms and is unlocked with a different code for each room and for each time period; an image is displayed in the room that provides room identification information for identifying the room and that can be read by a patient terminal; The medical interview system, wherein the medical interview terminal is provided in each of the plurality of rooms.

2. The medical interview system according to claim 1 , wherein the medical interview processing unit queries 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 causes the display unit to display the contents of the medical interview and information of the responses input by the patients to the contents of the medical interview 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 the patient's answer from the continuation of the thread by the input unit.

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

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

Images