Program, method and information processing device

JP2024173587A5Pending Publication Date: 2026-06-11FAST DOCTOR CO LTD

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
FAST DOCTOR CO LTD
Filing Date
2023-10-26
Publication Date
2026-06-11

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide a program for smoothly switching affiliation of a doctor and responding to a medical examination request from a patient at necessary timing.SOLUTION: There is provided a program causing a computer including a processor (39) and a storage part (37) to execute processing, and causing the storage part to store information of date / time of a medical treatment provided by a medical institution to a patient of the medical institution. The program causes the processor to execute: a step (S654) of presenting first information representing work conditions of performing medical treatment for a patient to a first user, the doctor who does not belong to the medical institution, before the patient's treatment date / time arrives, the first information including temporarily belonging to the medical institution of the patient; a step (S601) of receiving an operation to agree to the first information from the first user, before the medical treatment date / time arrives; and a step (S655) of, upon receiving the operation to agree thereto, storing the first information in the storage part.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, and an information processing device. [Background technology]

[0002] Depending on the size of a medical institution, it may not be possible to provide nighttime or holiday medical care based on an urgent request from a patient. When a medical institution is unable to respond to an urgent request for medical care or medical treatment, a technique is known that arranges for a doctor to respond.

[0003] Patent Document 1 describes a technology related to a matching system that instantly and reliably presents specialists to medical institutions that temporarily need employees. The matching system describes how the system refers to the recruitment conditions of the medical institution that needs employees and information on specialists, and displays information on specialists that fit the recruitment conditions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-38660 Summary of the Invention [Problem to be solved by the invention]

[0005] However, while the technology of Patent Document 1 can find a specialist who meets the recruitment requirements of a medical institution seeking to hire in the event of an emergency medical response, the doctor must be affiliated with the medical institution in order to actually treat the patient on behalf of the medical institution's attending physician. Therefore, even if a specialist is found, a separate process must be performed to switch the specialist's affiliation. In such a case, if it takes time to switch the doctor's affiliation, the doctor will not be able to treat the patient at the required time.

[0006] Therefore, the present disclosure provides a technology that enables smooth switching of the affiliation of a doctor who provides medical treatment on behalf of a medical institution's primary physician, and enables the doctor to provide medical treatment to a patient at the necessary timing. [Means for solving the problem]

[0007] According to one embodiment, a program is provided to be executed by a computer having a processor and a storage unit, the storage unit storing information on a consultation date and time when a medical institution will provide medical care to a patient of the medical institution. The program causes the computer to execute the steps of: presenting, to a first user who is a doctor not affiliated with the medical institution, first information indicating working conditions for providing medical care to the patient, the first information including that the patient is temporarily affiliated with the medical institution, before the consultation date and time of the patient arrives; accepting an operation to agree to the first information from the first user before the consultation date and time arrives; and storing the first information in the storage unit by accepting the operation to agree. Effect of the Invention

[0008] According to the present disclosure, a smooth change in a doctor's affiliation can be achieved by presenting information indicating the working conditions of the medical institution to a doctor who provides medical treatment on behalf of the medical institution's attending physician at the time of a patient's request for medical treatment or at a time based on a pre-registered medical treatment date and time. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram showing an overall configuration of a medical treatment request system 1 according to an embodiment. [Diagram 2] 2 is a block diagram showing the functional configuration of a doctor's terminal device 20. FIG. [Diagram 3] FIG. 2 is a block diagram showing the functional configuration of a server 30. [Figure 4] FIG. 3 is a diagram showing the data structure of a medical request information management database 3021. [Diagram 5] FIG. 13 is a diagram showing the data structure of a scheduled medical treatment information management database 3022. [Figure 6] FIG. 3 is a diagram showing the data structure of a patient medical information management database 3023. [Figure 7] 3 is a diagram showing the data structure of a medical institution information management database 3024. FIG. [Figure 8] FIG. 3 is a diagram showing the data structure of a doctor information management database 3025. [Figure 9] FIG. 3 is a diagram showing the data structure of a consent information management database 3026. [Figure 10] 13 is a flowchart showing an example (operation example 1) of a process flow for obtaining consent to the working conditions notice information from a corresponding doctor. [Figure 11] 13 is a flowchart showing another example (operation example 2) of the process flow for obtaining consent to the working conditions notice information from a corresponding doctor. [Figure 12] 13 is a flowchart showing another example (operation example 3) of the processing flow for obtaining consent to the working conditions notice information from a corresponding doctor. [Figure 13] FIG. 13 is a diagram showing an example of a screen of working conditions notice information presented on a doctor's terminal device. [Figure 14] FIG. 13 is a diagram showing an example of a screen for performing an operation to agree to working conditions notice information. [Figure 15] FIG. 13 is a diagram showing an example of a screen for performing an operation to not agree to the working conditions notice information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

[0011] <First embodiment> In this embodiment, information on the consultation date and time when the medical institution will treat patients at the medical institution is stored, and to a user who is a doctor not affiliated with the medical institution, information indicating the working conditions for performing medical treatment on the patient, which information includes the doctor's belonging to the medical institution, is presented before the patient's consultation date and time arrives in order to request treatment, and the working conditions notice information is stored in association with the medical treatment for the patient in response to an operation by the doctor who has received the information, and

[0012] <1.1 Overall configuration of medical treatment request system> Fig. 1 is a block diagram showing an example of the overall configuration of a medical treatment request system 1 according to an embodiment. As shown in Fig. 1, the medical treatment request system 1 includes a patient-side terminal device 10, a doctor-side terminal device 20, a server 30, and a medical institution-side terminal device 40, which are connected to each other via a network 80 so as to be able to communicate with each other.

[0013] The patient-side terminal device 10 is a device operated by a patient who requests medical treatment. The patient-side terminal device 10 is, for example, a mobile terminal such as a smartphone or a tablet, or a PC (Personal Computer).

[0014] The patient-side terminal device 10 executes a program to provide the user with an environment for operating the medical treatment request system 1 according to the program. The patient-side terminal device 10 reads and executes the program to establish a communication connection with the server 20 and the medical institution-side terminal device 40. The patient-side terminal device 10 then transmits information related to the medical treatment request to the server 20 and the medical institution-side terminal device 40 via the network 80.

[0015] The doctor's terminal device 20 is a device operated by a doctor who is a user. The doctor's terminal device 20 is, for example, a mobile terminal such as a smartphone or a tablet, or a PC (Personal Computer).

[0016] The doctor's terminal device 20 executes the program to provide the user with an environment for operating the medical request system 1 according to the program. The doctor's terminal device 20 reads and executes the program to establish a communication connection between the doctor's terminal device 20 and the server 30. The doctor's terminal device 20 also receives working conditions notice information from the server 30 and transmits information regarding consent to work based on the working conditions notice information to the server 30.

[0017] As shown in FIG. 1, the doctor's terminal device 20 includes a communication IF (Interface) 22, an input device 23, an output device 24, a memory 27, a storage unit 28, and a processor 29.

[0018] The communication IF 22 is an interface for inputting and outputting signals so that the doctor's terminal device 20 can communicate with an external device.

[0019] The input device 23 is a device for receiving an input operation from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0020] The output device 24 is a device (such as a display or a speaker) for presenting information to a user.

[0021] The memory 27 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0022] The storage unit 28 is for storing data, and is, for example, a flash memory or a HDD (Hard Disc Drive).

[0023] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0024] The server 30 is a device that manages a series of processes related to the medical treatment request system 1. The server 30 performs a process of presenting the working conditions notice information to the doctor's terminal device 20 of the doctor who will be treating the patient at the timing of receiving a medical treatment request from the patient or at a timing based on the medical treatment date and time of the patient who is registered in advance. The server 30 communicates with the doctor's terminal device 20 and performs a process of storing the working conditions notice information in response to an operation agreed to by the doctor. The server 30 manages various data such as medical treatment requests from patients, scheduled medical treatment to be registered, and doctor information to be registered.

[0025] The server 30 includes a communication IF 32 , an input / output IF 33 , a memory 35 , a storage 36 , and a processor 39 .

[0026] The communication IF 32 is an interface for inputting and outputting signals so that the server 30 can communicate with external devices.

[0027] The input / output IF 33 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0028] The memory 35 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0029] The storage 36 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0030] The processor 39 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0031] The medical institution side terminal device 40 includes a communication IF (Interface) 42 , an input device 43 , an output device 44 , a memory 45 , a storage unit 46 , and a processor 49 .

[0032] The communication IF 42 is an interface for inputting and outputting signals so that the medical institution side terminal device 40 can communicate with external devices.

[0033] The input device 43 is a device for receiving an input operation from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0034] The output device 44 is a device (such as a display or a speaker) for presenting information to a user.

[0035] The memory 45 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0036] The storage unit 46 is for storing data, and is, for example, a flash memory or a HDD (Hard Disc Drive).

[0037] The processor 49 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0038] <1.2 Functional configuration of the doctor's terminal device 20> FIG. 2 is a diagram showing the functional configuration of the doctor's terminal device 20. The doctor's terminal device 20 includes a plurality of antennas (antenna 211, antenna 212), wireless communication units (first wireless communication unit 221, second wireless communication unit 222) corresponding to each antenna, an operation reception unit 230, a voice processing unit 240, a microphone 241, a speaker 242, a position information sensor 250, a camera 260, a storage unit 270, and a control unit 280. The doctor's terminal device 20 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not particularly shown in FIG. 2. As shown in FIG. 2, each block included in the doctor's terminal device 20 is electrically connected by a bus or the like.

[0039] The antenna 211 radiates the signal generated by the doctor's terminal device 20 into space as radio waves. The antenna 211 also receives the radio waves from space and provides the received signal to the first wireless communication unit 221.

[0040] The antenna 212 radiates the signal generated by the doctor's terminal device 20 into space as radio waves. The antenna 212 also receives the radio waves from space and provides the received signal to the second wireless communication unit 222.

[0041] The first wireless communication unit 221 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 211 so that the doctor's terminal device 20 can communicate with other wireless devices. The second wireless communication unit 222 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 212 so that the doctor's terminal device 20 can communicate with other wireless devices. The first wireless communication unit 221 and the second wireless communication unit 222 are communication modules including a tuner, a Received Signal Strength Indicator (RSSI) calculation circuit, a Cyclic Redundancy Check (CRC) calculation circuit, a high-frequency circuit, and the like. The first wireless communication unit 221 and the second wireless communication unit 222 perform modulation and demodulation and frequency conversion of wireless signals transmitted and received by the doctor's terminal device 20, and provide the received signals to the control unit 280.

[0042] The operation reception unit 230 has a mechanism for receiving an input operation by a user. Specifically, the operation reception unit 230 is configured as a touch screen, and includes a touch-sensitive device 231 and a display 232. The touch-sensitive device 231 receives an input operation by a user of the doctor side terminal device 20. The touch-sensitive device 231 detects the user's touch position on the touch panel by using, for example, a capacitive touch panel. The touch-sensitive device 231 outputs a signal indicating the user's touch position detected by the touch panel to the control unit 280 as an input operation.

[0043] Display 232 displays data such as images, videos, and text under the control of control unit 280. Display 232 is realized by, for example, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like.

[0044] The voice processing unit 240 modulates and demodulates a voice signal. The voice processing unit 240 modulates a signal provided from a microphone 241 and provides the modulated signal to the control unit 280. The voice processing unit 240 also provides the voice signal to a speaker 242. The voice processing unit 240 is realized, for example, by a processor for voice processing. The microphone 241 accepts voice input and provides a voice signal corresponding to the voice input to the voice processing unit 240. The speaker 242 converts the voice signal provided from the voice processing unit 240 into voice and outputs the voice to the outside of the doctor's side terminal device 20.

[0045] The position information sensor 250 is a sensor that detects the position of the doctor's terminal device 20, and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. In the satellite positioning system, signals are received from at least three or four satellites, and the current position of the doctor's terminal device 20 equipped with the GPS module is detected based on the received signals.

[0046] The camera 260 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 260 is, for example, a depth camera that can detect the distance from the camera 260 to a subject being photographed.

[0047] The storage unit 270 is configured with, for example, a flash memory, and stores data and programs used by the doctor side terminal device 20. In one aspect, the storage unit 270 stores user information 271 and working conditions notice information 272.

[0048] The user information 271 is information about a user who is a doctor who performs an operation such as consenting to a medical treatment request using the doctor's terminal device 20. The user information includes information about a user ID, information about the user's name, information about the affiliated medical institution ID, information about the user's contact information, and the like.

[0049] The working conditions notice information 272 is information sent from the server 30 in response to an operation of consenting to a medical treatment request. The information includes information on the patient who will be treated, information on the date and time of the medical treatment, information on working conditions, information on the medical institution to which the patient belongs, and the like.

[0050] The control unit 280 reads a program stored in the storage unit 270 and executes commands included in the program to control the operation of the doctor's terminal device 20. The control unit 280 is, for example, an application that is pre-installed in the doctor's terminal device 20. The control unit 280 operates according to the program to fulfill the functions of an input operation reception unit 281, a transmission / reception unit 282, a notification control unit 283, and a data processing unit 284.

[0051] The input operation reception unit 281 performs processing for receiving a user's input operation on an input device such as the touch-sensitive device 231. The input operation reception unit 281 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on information on the coordinates where the user touches the touch-sensitive device 231 with a finger or the like.

[0052] The transmitting / receiving unit 282 performs processing for the doctor's terminal device 20 to transmit and receive data to and from an external device such as the server 30 in accordance with a communication protocol.

[0053] The notification control unit 283 performs a process of presenting information to a doctor who is a user. The notification control unit 283 performs a process of displaying a display image on the display 232, a process of outputting sound to the speaker 242, and the like.

[0054] The data processing unit 284 performs calculations on the data received by the doctor's terminal device 20 according to a program, and outputs the calculation results to a memory or the like.

[0055] <1.3 Functional configuration of server 30> 3 is a diagram showing a functional configuration of the server 30. As shown in FIG. 3, the server 30 fulfills the functions of a communication unit 301, a storage unit 302, and a control unit 303.

[0056] The communication unit 301 performs processing for the server 30 to communicate with external devices.

[0057] The memory unit 302 stores a medical treatment request information management database 3021, a scheduled medical treatment information management database 3022, a patient medical information management database 3023, a medical institution information management database 3024, a doctor information management database 3025, a consent information management database 3026, working conditions notice information 3027, etc.

[0058] The medical treatment request information management database 3021 is a database for managing various information related to medical treatment requests from patients, which will be described in detail later.

[0059] The scheduled medical treatment information management database 3022 is a database for managing various information related to scheduled medical treatment such as home visits that has been registered in advance, as will be described in detail later.

[0060] The patient medical information management database 3023 is a database for managing various types of medical information relating to the past medical history of a patient, as will be described in detail later.

[0061] The medical institution information management database 3024 is a database for managing various information related to medical institutions to which patients are referred for medical treatment, as will be described in detail later.

[0062] The doctor information management database 3025 is a database for managing various information related to doctors who provide medical treatment in response to requests from medical institutions. Details will be described later.

[0063] The consent information management database 3026 is a database for managing various information related to consent to medical treatment received from a doctor in response to a request from a medical institution. Details will be described later.

[0064] The working conditions notice information 3027 is a database that includes information regarding the working conditions notice agreed to by the doctor. Details will be described later.

[0065] The control unit 303 is realized by the processor 39 reading a program stored in the storage unit 302 and executing instructions included in the program. By operating in accordance with the program, the control unit 303 exerts functions indicated as a reception control module 3031, a transmission control module 3032, a medical treatment request information acquisition module 3033, a scheduled medical treatment information acquisition module 3034, a patient medical information acquisition module 3035, a medical institution information acquisition module 3036, a doctor information acquisition module 3037, a working conditions notice information generation module 3038, a consent information acquisition module 3039, and a working conditions notice information presentation module.

[0066] The reception control module 3031 controls the process in which the server 30 receives a signal from an external device in accordance with a communication protocol.

[0067] The transmission control module 3032 controls the process in which the server 30 transmits signals to external devices in accordance with a communication protocol.

[0068] The medical treatment request information acquisition module 3033 performs a series of processes for managing information regarding medical treatment requests from patients. The information regarding medical treatment requests includes information regarding the patient's name, information regarding the patient's age, information regarding the patient's sex, information regarding the patient's address, information regarding the patient's contact information, information regarding the date and time of the medical treatment request, information regarding the ID of the medical institution that received the request, information regarding whether or not the medical institution that received the request can provide treatment, etc. The medical treatment request information acquisition module 3033 stores the acquired information regarding the medical treatment request in the medical treatment request information management database 3021.

[0069] The scheduled medical treatment information acquisition module 3034 performs a series of processes for managing information regarding scheduled medical treatment such as home visits that has been registered in advance. The information regarding scheduled medical treatment includes information regarding the patient's name, information regarding the patient's age, information regarding the patient's sex, information regarding the patient's address, information regarding the patient's contact information, information regarding the scheduled medical treatment date and time, information regarding the ID of the medical institution in charge of the patient, information regarding the availability of medical treatment at the medical institution in charge, etc. The scheduled medical treatment information acquisition module 3034 stores the acquired information regarding the medical treatment request in the scheduled medical treatment information management database 3022.

[0070] The patient medical information acquisition module 3035 performs a series of processes for managing medical information related to the patient's past medical history. The medical information related to the patient's past medical history includes information related to the patient ID, information related to the patient's name, information related to the medical institution ID in charge, information related to the date and time of each medical treatment, and information related to the medical content of each medical treatment. The medical information related to the patient's past medical history is information held by the medical institution that is originally in charge of the patient, and can be viewed by, for example, a doctor who agrees to the working conditions notice information and temporarily belongs to the medical institution. The patient medical information acquisition module 3035 is acquired from each medical institution's terminal device 40, etc. The patient medical information acquisition module 3035 stores the acquired medical information related to the patient's past medical history in the patient medical information management database 3023.

[0071] The medical institution information acquisition module 3036 performs a series of processes for managing information about the medical institution to which medical treatment is requested. The information about doctors includes information about the name of the medical institution, information about the contact information of the medical institution, information about the first designated doctor ID, information about the second designated doctor ID, information about the third designated doctor ID, etc. The medical institution information acquisition module 3036 stores the acquired information about the medical institution in the medical institution information management database 3024. The designated doctor ID does not necessarily have to include the first to third pieces of information. Furthermore, the designated doctor ID may include four or more designated doctor IDs.

[0072] The doctor information acquisition module 3037 performs a series of processes for managing information about doctors. The information about doctors includes information about the name of the user who is a doctor, information about the ID of the medical institution to which the user usually belongs, information about the user's contact information, information about the first designated medical institution ID, information about the second designated medical institution ID, information about the time period when medical treatment is available, information about whether or not home visit medical treatment is available, and information about whether or not online medical treatment is available. The doctor information acquisition module 3037 stores the acquired information about doctors in the doctor information management database 3025. The designated medical institution ID does not necessarily need to include the first to second pieces of information. The designated doctor ID may also include three or more designated medical institution IDs.

[0073] The working conditions notice information generation module 3038 performs a series of processes for generating working conditions notice information to be presented to a doctor. The generated working conditions notice information includes information indicating working conditions for performing medical treatment on a patient and indicating temporary membership in a medical institution. The working conditions notice information generation module 3038 generates working conditions notice information based on information about the medical institution in charge of the patient who is the subject of medical treatment and information about the doctor who is the subject of a medical treatment request. The working conditions notice information generation module 3038 stores the generated working conditions notice information in the storage unit 302.

[0074] In addition, "temporarily belonging" means that a doctor user belongs to a specific medical institution during the working period (contract period), which is one of the working conditions included in the working conditions notice information, and that the user does not belong to a specific medical institution outside of the working period. For example, a doctor can access and view medical information of patients held by a medical institution during the period when he or she belongs to a specific medical institution, but after the period of affiliation has passed, he or she will no longer belong to a specific medical institution and will be unable to view the information.

[0075] The consent information acquisition module 3039 performs a series of processes for managing information regarding consent to a medical treatment request from a doctor. The information regarding consent to a medical treatment request includes information regarding the user ID of the doctor, information regarding the affiliated medical institution ID to which the user usually belongs, information regarding consent to the medical treatment request, information regarding the date and time of consent to the beverage request, information regarding the affiliated institution ID of the switching destination when switching affiliation, etc. The consent information acquisition module 3039 stores the acquired information regarding consent to a medical treatment request in the consent information management database 3026.

[0076] <2 Data Structure> Figures 4 to 7 are diagrams showing the data structures of the databases stored in the server 30. Note that Figures 4 to 7 are merely examples, and do not exclude data that is not shown.

[0077] 4 is a diagram showing the data structure of the medical treatment request information management database 3021. Each record of the medical treatment request information management database 3021 includes the following items: "medical treatment request ID," "patient name," "patient age," "patient sex," "patient address," "patient contact information," "medical treatment request date and time," "receiving medical institution ID," and "availability of medical treatment at the receiving medical institution." The illustrated example shows an example in which three medical treatment requests can be accepted, but is not limited to this.

[0078] The item "treatment request ID" is information for identifying each treatment request received from a patient.

[0079] The item "patient name" is information indicating the name of the patient who has made a medical treatment request.

[0080] The item "patient age" is information indicating the age of the patient.

[0081] The item "patient gender" is information indicating the gender of the patient.

[0082] The item "Patient Contact Information" is information indicating the contact information of the patient. The information indicating the contact information of the patient includes an email address, a telephone number, etc.

[0083] The item "treatment request date and time" is information indicating the date and time when the treatment request was accepted.

[0084] The item "ID of the medical institution accepting the medical treatment" is information for identifying the medical institution that accepted the medical treatment request.

[0085] The item "Can the medical institution that accepted the medical treatment provide treatment?" is information that indicates whether the medical institution that accepted the medical treatment request can provide treatment. Specifically, if the medical institution can provide treatment for the accepted medical treatment request, "Yes" is displayed, whereas if the medical institution cannot provide treatment, "No" is displayed.

[0086] 5 is a diagram showing the data structure of the scheduled medical treatment information management database 3022. Each record of the scheduled medical treatment information management database 3022 includes the following items: "scheduled medical treatment ID," "patient name," "patient age," "patient sex," "patient address," "patient contact information," "scheduled medical treatment date and time," "medical institution ID," and "availability of medical treatment at medical institution." The illustrated example shows an example that can accommodate three scheduled medical treatments, but is not limited to this.

[0087] The item "scheduled medical treatment ID" is information that identifies each scheduled medical treatment that is registered in advance.

[0088] The item "patient name" is information indicating the name of the patient to be treated.

[0089] The item "patient age" is information indicating the age of the patient.

[0090] The item "patient gender" is information indicating the gender of the patient.

[0091] The item "Patient Contact Information" is information indicating the contact information of the patient. The information indicating the contact information of the patient includes an email address, a telephone number, etc.

[0092] The item "scheduled medical treatment date and time" is information indicating the date and time of a medical treatment that is scheduled.

[0093] The item "medical institution ID" is information for identifying each medical institution that is originally responsible for the patient.

[0094] The item "Availability of medical institution in charge" is information indicating whether the medical institution in charge can provide medical treatment. Specifically, if the medical institution in charge can provide medical treatment at the scheduled medical treatment date and time, "Available" is displayed, whereas if the medical institution in charge cannot provide medical treatment, "Not available" is displayed.

[0095] 6 is a diagram showing the data structure of the patient medical information management database 3023. Each record in the patient medical information management database 3023 includes an item "Patient ID", an item "Patient name", an item "ID of medical institution in charge", an item "Date and time of medical treatment", and an item "Information on medical treatment details at the time of medical treatment". In the example shown in the figure, three examples of medical treatment history are shown, but this is not limited to this.

[0096] The item "patient ID" is information for identifying each patient who is the subject of medical treatment.

[0097] The item "patient name" is information indicating the name of the patient.

[0098] The item "medical institution ID" is information for identifying each medical institution that has treated the patient.

[0099] The item "treatment date and time" is information indicating the treatment date and time when each treatment was performed.

[0100] The item "information on medical treatment content during medical treatment" is information indicating the medical treatment content during each medical treatment. Information indicating the medical treatment content includes information on the patient's symptoms based on diagnosis, information on the patient's medical history, information on prescribed medicines, etc.

[0101] 7 is a diagram showing the data structure of the medical institution information management database 3024. Each record of the medical institution information management database 3024 includes an item "medical institution ID", an item "medical institution name", an item "medical institution contact information", an item "first designated doctor ID", an item "second designated doctor ID", and an item "third designated doctor ID". In the illustrated example, three medical institutions are shown, but the present invention is not limited to this.

[0102] The item "medical institution ID" is information that identifies each medical institution.

[0103] The item "Name of medical institution" is information indicating the name of a medical institution.

[0104] The item "medical institution contact information" is information indicating the contact information of a medical institution. The information indicating the contact information of a medical institution includes an email address, a telephone number, etc.

[0105] The item "First designated doctor ID" indicates information for identifying the first doctor designated by a specific medical institution from among those registered as doctors who can provide medical care. The doctor corresponding to the first designated doctor ID can be the doctor with the highest priority requested by the specific medical institution. On the other hand, some medical institutions do not designate a specific doctor, in which case it is classified as "not designated."

[0106] The item "Second designated doctor ID" indicates information for identifying a second doctor designated by a specific medical institution from among those registered as doctors who can provide medical care. The doctor corresponding to the second designated doctor ID can be the second highest priority doctor requested by the specific medical institution. If the medical institution does not designate a doctor as the second designated doctor, it is classified as "not designated."

[0107] The item "Third designated doctor ID" indicates information for identifying a third doctor designated by a specific medical institution from among those registered as doctors who can provide medical care. The doctor corresponding to the second designated doctor ID can be the third highest priority doctor requested by the specific medical institution. If the medical institution does not designate a doctor as the third designated doctor, it is classified as "not designated."

[0108] FIG. 8 is a diagram showing the data structure of the doctor information management database 3025. Each record of the doctor information management database 3025 includes an item "user ID", an item "user name", an item "affiliated medical institution ID", an item "user contact information", an item "first designated medical institution ID", an item "second designated medical institution ID", an item "available time slot for medical treatment", an item "availability of home visit medical treatment", and an item "availability of online medical treatment". Each record is stored as the latest information by inputting information from a user, etc., but is updated to new information if there is a change in the information, such as a change in the available time slot for medical treatment. In the illustrated example, an example of three doctors is shown, but this is not limited to this.

[0109] The item "user ID" is information for identifying each user who is a doctor.

[0110] The item "user name" is information indicating the name of the user.

[0111] The item "affiliated medical institution ID" is information for identifying the medical institution to which the doctor normally belongs.

[0112] The item "user contact information" is information indicating the doctor's contact information, such as an email address and a telephone number.

[0113] The item "First designated medical institution ID" indicates information for identifying the first medical institution when a doctor is designated by a specific medical institution. If there is no medical institution that designates a doctor, it is classified as "Not designated."

[0114] The item "Second designated medical institution ID" indicates information to identify the second medical institution when a doctor is designated by a specific medical institution. If there is no medical institution that designates a doctor, it is classified as "Not designated."

[0115] The item "available time period" is information indicating the time period during which a doctor can provide medical care when a request for medical care is received. Examples of this information include "weekdays: 18:00 - 23:00" and "weekends: 9:00 - 18:00".

[0116] The item "availability of home visits" is information indicating whether or not a doctor can provide home visits. Specifically, if a doctor can provide home visits, "available" is displayed, whereas if a doctor cannot provide home visits, "not available" is displayed.

[0117] The item "Online medical consultation availability" is information indicating whether or not a doctor can provide online medical consultation. Specifically, if a doctor can provide online medical consultation, "Available" is displayed, whereas if a doctor cannot provide online medical consultation, "Not available" is displayed.

[0118] 8 is a diagram showing the data structure of the consent information management database 3026. Each record in the consent information management database 3026 includes an item "management ID", an item "user name", an item "affiliated medical institution ID", an item "whether or not consent is given to the medical treatment request", an item "date and time of consent to the medical treatment request", and an item "switching destination affiliated medical institution ID". In the illustrated example, three management examples are shown, but the present invention is not limited to these.

[0119] The item "management ID" is information that identifies each case of consent information for medical treatment request.

[0120] The item "user name" is information indicating the name of a doctor.

[0121] The item "affiliated medical institution ID" is information for identifying the medical institution to which the doctor normally belongs.

[0122] The item "Agreement to medical treatment request" is information indicating whether the doctor agrees to the information in the working conditions notice presented as a medical treatment request from the medical institution. Specifically, if the doctor agrees to the information in the working conditions notice (medical treatment request), "Yes" is displayed, whereas if the doctor does not agree to the information in the working conditions notice (medical treatment request), "No" is displayed.

[0123] The item "Destination Affiliated Medical Institution ID" is information that identifies the destination medical institution when the doctor agrees to the information (medical treatment request) described in the working conditions notice. The destination Affiliated Medical Institution ID is not displayed when the doctor does not agree to the information (medical treatment request) described in the working conditions notice.

[0124] <3 operations> Next, the operation of each device constituting the medical request system 1 will be described.

[0125] <3.1 Operation example 1> 10 is a diagram showing the flow of processing for obtaining consent to the working conditions notice information from a corresponding doctor via the server 30. In the following example, an example will be described in which the working conditions notice information is presented to a doctor at the timing of accepting a medical treatment request from a patient.

[0126] Operation example 1 corresponds to a case where, for example, a patient has a regular medical institution and requests medical treatment outside the medical institution's treatment facility, such as at night or on holidays, and, at the request of the medical institution, a doctor affiliated with a different medical institution is presented with information on the notice of working conditions so that the doctor can temporarily provide medical treatment as a doctor affiliated with the medical institution.

[0127] In step S651, the server 30 accepts a medical treatment request from a patient.

[0128] In step S652, the server 30 identifies the medical institution in charge of the patient, and extracts a doctor to be requested to treat based on information about the medical institution. When extracting a doctor, if the medical institution has registered a designated doctor, the doctor with the highest priority can be extracted from among the designated doctors. On the other hand, if the medical institution has not registered a designated doctor, the server 30 extracts a doctor from among the registered doctors who are available to treat the patient, by referring to information about the time period during which the doctor is available to treat the patient. The number of doctors extracted by the server 30 is not limited to one. For example, the server 30 can extract a plurality of doctors, select the doctor with the most free time among the extracted doctors, and set this doctor as the doctor to be finally extracted. Before executing the process of step S652, the server 30 can determine whether the medical institution in charge of the patient can treat the patient, and execute the process of step S652 if the medical institution cannot treat the patient.

[0129] In step S653, the server 30 generates working conditions notice information based on the information about the medical institution and the extracted information about the doctor. The working conditions notice information to be presented includes information about the patient's medical care, as well as information about the temporary affiliation to the requested medical institution.

[0130] In step S654, the server 30 presents the generated working conditions notice information to the doctor's terminal device 20 via the network 80.

[0131] In step S601, when the doctor who has received the working conditions notice agrees to the contents of the information, that is, agrees to treat the patient, the doctor's terminal device 20 accepts the consent operation. The doctor user inputs information for consenting to the working conditions notice information using the doctor's terminal device 20 and transmits it to the server 30.

[0132] In step S655, the server 30 stores the working conditions notice information in response to the user's consent operation. In this case, the server 30 updates the consent information management database 3026 based on the consented content and stores the working conditions notice information.

[0133] In step S656, the server 20 transmits the working conditions notice information to which the doctor has agreed, to the doctor user.

[0134] In the above process, in step S652, when server 30 extracts a doctor to whom treatment is to be requested, it can also check whether the request for treatment from the patient is for in-person treatment such as a home visit or online treatment, and extract a doctor who can provide a treatment method that matches the treatment request.

[0135] <3.2 Operation example 2> 11 is a diagram showing another example of the flow of processing for obtaining consent to the working conditions notice information from the corresponding doctor via the server 30. In the following example, an example is described in which the working conditions notice information is presented to the doctor at the timing of the medical treatment date and time of a scheduled medical treatment such as a home visit that has been registered in advance.

[0136] Operation example 2 corresponds to a case where, for example, a patient has a regular medical institution and the consultation date and time for home visits, etc. is registered in advance, but the medical institution is unable to provide medical treatment at the registered consultation date and time, and, at the request of the medical institution, a doctor affiliated with a different medical institution is presented with information on the notice of working conditions so that the doctor can temporarily provide medical treatment as a doctor affiliated with the medical institution.

[0137] In step S6510, the server 30 registers information regarding the scheduled medical treatment such as a home visit, etc. The registered information includes information regarding the patient to be treated, the contents of the medical treatment, the date and time of the medical treatment, and the like.

[0138] In step S6520, the server 30 identifies the medical institution in charge of the patient on the day of the registered scheduled medical appointment, and extracts a doctor affiliated with the medical institution as a medical appointment request target. When extracting a doctor, if the medical institution has registered a designated doctor, the doctor with the highest priority can be extracted from the designated doctors. On the other hand, if the medical institution has not registered a designated doctor, a doctor is extracted from the registered doctors available for medical treatment by referring to information on the time period during which the doctor is available for medical treatment. Before executing the process of step S6520, the server 30 can determine whether the medical institution in charge of the patient can treat the patient on the scheduled medical appointment, and can also execute the process of step S6520 if the medical institution cannot treat the patient.

[0139] In step S6530, the server 30 generates working conditions notice information based on the information about the medical institution and the extracted information about the doctor. The working conditions notice information to be presented includes information about the patient's medical care, as well as information about the temporary affiliation to the requested medical institution.

[0140] In step S6540, the server 30 presents the generated working conditions notice information to the doctor's terminal device 20 via the network 80.

[0141] The subsequent processes (processing after step S601) are the same as those in the first operational example, and therefore the description thereof will be omitted.

[0142] In the above process, in step S6520, when the server 30 extracts a doctor to be requested to treat, it can also check whether the scheduled medical treatment is an in-person medical treatment such as a home visit or an online medical treatment, and extract a doctor who can handle the treatment method that matches the scheduled medical treatment.

[0143] <3.3 Operation example 3> 11 is a diagram showing another example of the process flow for obtaining consent to the working conditions notice information from a corresponding doctor via the server 30. In the following example, an example is described in which the working conditions notice information is presented to a doctor in response to a medical treatment request from a medical institution that has accepted a medical treatment request from a patient.

[0144] Operation example 3 corresponds to a case where, for example, a medical institution in the patient's location (e.g., Fukuoka Prefecture) accepts a request for medical treatment from the patient, but is unable to provide the treatment due to being outside of business hours, and, at the request of the medical institution, a doctor affiliated with a medical institution in another prefecture (e.g., Tokyo) other than the medical institution in question is presented with information on the notice of working conditions so that the doctor can temporarily provide treatment online as a doctor affiliated with the medical institution in question.

[0145] In step S701, the medical institution side terminal device 40 accepts a medical treatment request from a patient.

[0146] In step S702, the medical institution side terminal device 40 transmits information regarding the medical treatment request to the server 30.

[0147] In step S6521, when the server 30 receives information regarding a medical treatment request, it extracts a doctor to whom the medical treatment request is to be made based on information regarding the medical institution to which the medical treatment request is to be made. When extracting a doctor, if the medical institution has registered designated doctors, it is possible to extract the doctor with the highest priority from among the designated doctors. On the other hand, if the medical institution has not registered designated doctors, it extracts a doctor from among those registered as doctors available for medical treatment by referring to information such as the time period during which the doctor is available for medical treatment.

[0148] In step S6531, the server 30 generates working conditions notice information based on the information about the medical institution and the extracted information about the doctor. The working conditions notice information to be presented includes information about the patient's medical care, as well as information about the temporary affiliation to the requested medical institution.

[0149] In step S6541, the server 30 presents the generated working conditions notice information to the doctor's terminal device 20 via the network 80.

[0150] The subsequent processes (processing after step S601) are the same as those in the first operational example, and therefore the description thereof will be omitted.

[0151] In the above process, in step S6521, when server 30 extracts a doctor to whom treatment is to be requested, it can also check whether the request for treatment from the patient is for in-person treatment such as a home visit or online treatment, and extract a doctor who can provide a treatment method that matches the treatment request.

[0152] <4 Screen example> FIG. 13 is a diagram showing an example of a screen of the working conditions notice information presented to the doctor's terminal device.

[0153] 13 is a screen example 801 displayed on the doctor side terminal device 20. This corresponds to the processing in step S653 in FIG 9, step S6530 in FIG 10, and step S6531 in FIG 11.

[0154] As shown in FIG. 13, the doctor's terminal device 20 displays an area 801A for displaying information relating to the name of the doctor requesting medical treatment, an area 801B for displaying information relating to the requester of the medical treatment, an area 801C for displaying information relating to the specific work content, and an area 801D for displaying information for confirming whether or not to agree to the presented working conditions notice information.

[0155] In area 801A, information regarding the name of the doctor to be requested for medical treatment can be displayed. The name of the doctor who received the working conditions notice information is displayed on the screen.

[0156] In the area 801B, information about the requester requesting medical treatment can be displayed. Specifically, information about the business name of the medical institution that is the requester requesting medical treatment, the address of the medical institution, the name and title of the employer of the medical institution, etc. is displayed.

[0157] In the area 801C, information on the specific work content can be displayed. Specifically, information on the contract period, the work location where medical treatment is scheduled, the work content to be performed, wages, etc. can be displayed.

[0158] In the area 801D, information for confirming whether or not to agree to the presented working conditions notice information can be displayed. Specifically, link information (8011D) for performing the process of agreeing to the working conditions notice information and link information (8012D) for performing the process of not agreeing to the working conditions notice information are displayed.

[0159] The doctor checks the information about his / her own name displayed in area 801A, the information about the requesting medical institution displayed in area 801B, and the information about the specific work content displayed in area 801C, and if he / she agrees with the contents of the working conditions notice information, he / she clicks on link information 8011D that reads "Agree." When he / she agrees, he / she moves to the confirmation screen shown in Fig. 13. On the other hand, if he / she does not agree with the contents of the working conditions notice information, he / she clicks on link information 8012D that reads "Do not agree."

[0160] FIG. 14 is a diagram showing an example of a screen for performing an operation to agree to the contents of the working conditions notice information.

[0161] 14 is a screen example 901 displayed on the doctor side terminal device 20. This corresponds to the process of step S601 in FIG.

[0162] As shown in FIG. 14, the doctor's terminal device 20 displays an area 901A for displaying information regarding the doctor's response to the presented working conditions notice information, and an area 901B for displaying information confirming whether or not the information regarding the doctor's response can be sent.

[0163] In the area 901A, information on the doctor's response to the presented working conditions notice information can be displayed. Specifically, when the doctor performs an "Agree" operation on the screen displaying the working conditions notice information shown in FIG. 12, information to the effect that "I agree to the contents of the working conditions notice" is displayed.

[0164] In the area 901B, information for confirming whether or not to transmit information related to the doctor's answer displayed in the area 901A can be displayed. Specifically, link information (9011B) for performing a process for transmitting information related to the content displayed in the area 901A and link information (9012B) for performing a process for not transmitting information related to the content displayed in the area 901A are displayed.

[0165] After confirming the answer that the doctor agrees to the contents displayed in area 901A, i.e., the contents of the notice of working conditions, the doctor performs an operation of clicking on link information 9011B marked "Send" if the doctor wishes to send information related to the contents displayed in area 901A. When the doctor performs the operation of sending, information indicating agreement to the contents of the notice of working conditions is sent to server 30. On the other hand, if the doctor does not wish to send information related to the contents displayed in area 901A, the doctor performs an operation of clicking on link information 9012B marked "Do not send."

[0166] FIG. 15 is a diagram showing an example of a screen for performing an operation to not agree to the contents of the working conditions notice information.

[0167] A screen example 902 in FIG. 15 is a screen displayed on the doctor's terminal device 20.

[0168] As shown in Figure 15, the doctor's terminal device 20 displays an area 902A for displaying information regarding the doctor's response to the presented working conditions notice information, an area 902B for displaying information regarding the reasons for not agreeing with the contents of the working conditions notice, and an area 902C for displaying information confirming whether or not to send the information regarding the doctor's response.

[0169] In the area 902A, information on the doctor's response to the presented working conditions notice information can be displayed. Specifically, when the doctor performs an operation to "disagree" on the screen displaying the working conditions notice information shown in FIG. 12, information to the effect that "I do not agree to the contents of the working conditions notice" is displayed.

[0170] In the area 902B, information regarding the reason for not agreeing to the contents of the working conditions notice can be displayed. Specifically, for example, the reasons for not agreeing are displayed as options, and the doctor can select one of "schedule does not match," "cannot agree to the working conditions," and "other reasons." If "other reasons" is selected, a specific reason can be input.

[0171] In area 901C, information for confirming whether or not to transmit information related to the doctor's answers displayed in areas 902A and 902B can be displayed. Specifically, link information (9021C) for performing a process for transmitting information related to the contents displayed in areas 902A and 902B, and link information (9022C) for performing a process for not transmitting information related to the contents displayed in areas 902A and 902B are displayed.

[0172] After checking the contents displayed in area 901A, i.e., information regarding the response indicating that the doctor does not agree with the contents of the working conditions notice, and information regarding the reason for not agreeing with the contents of the working conditions notice displayed in area 902B, the doctor clicks on link information 9021B marked "Send" if the doctor wishes to send the information regarding the contents displayed in areas 902A and 902B. When the doctor performs the send operation, information indicating that the doctor does not agree with the contents of the working conditions notice is transmitted to server 30. On the other hand, if the doctor does not wish to send the information regarding the contents displayed in areas 902A and 902B, the doctor clicks on link information 9022B marked "Do not send."

[0173] This allows the doctor to quickly respond to the medical treatment request by confirming the information on the working conditions notice presented to him / her and then performing an operation to consent.

[0174] <5. Variations> A modification of this embodiment will now be described.

[0175] (1) Procedures when the doctor does not consent to the information in the notice of working conditions When the server 30 receives a response from a first affiliated doctor (doctor with first priority) affiliated with the requested medical institution stating that the doctor does not agree with the contents of the working conditions notice information, the server 30 may execute a process of presenting the working conditions notice information to a second affiliated doctor (doctor with second priority) affiliated with the requested medical institution.

[0176] (2) Processing to notify the requested medical institution when storing the information on the notice of working conditions When the server 30 receives an operation from a doctor to agree to the working conditions notice information, it may store the working conditions notice information and execute a process to notify the requested medical institution that agreement to the working conditions notice information (medical treatment) has been obtained.

[0177] (3) Processing when a user agrees to the information in the employment conditions notice and their affiliation is temporarily changed When the server 30 receives an operation from the user agreeing to the working conditions notice information, the server 30 may execute a process of presenting the medical information on the patient's past medical history held by the medical institution to the user during the period during which the user temporarily belongs to the requested medical institution. This allows the user to view the medical information on the patient's past medical history stored in the patient medical information management database 2023 during the working period (contract period) included in the working conditions notice information.

[0178] (4) Other processing related to the presentation of information on the notice of working conditions When presenting the working conditions notice information to the user, the server 30 may also execute a process of presenting information necessary for switching the user's affiliation, such as information on the employment contract and information on the non-disclosure agreement. This allows the user to switch the affiliation more smoothly.

[0179] In this case, the server 30 may also receive medical record information related to the medical treatment from the user after the user has completed the medical treatment of the patient, and execute a process of updating medical information related to the patient's past medical treatment history based on the received medical record information.

[0180] As described above, according to the medical care request system 1 of the present disclosure, before the patient's medical care date and time arrives, a user who is a doctor not belonging to a medical institution is presented with working conditions notice information indicating working conditions for performing medical care for the patient, including temporary affiliation to the medical institution of the patient, and an operation to agree to the working conditions notice information is received from the user before the medical care date and time arrives, and by receiving the consent operation, the working conditions notice information is stored in the storage unit. This makes it possible to smoothly switch the doctor's affiliation and to provide medical care to the patient at the necessary timing.

[0181] According to the medical treatment request system 1 of the present disclosure, the timing for accepting a request for medical treatment from a patient is before the arrival of the medical treatment date and time of the patient, and a process for presenting the working conditions notice information to the user is performed at that timing. This allows doctors to smoothly switch affiliations and to respond to patients' medical treatment at the required timing.

[0182] Furthermore, according to the medical treatment request system 1 of the present disclosure, if the medical institution is unable to treat the patient at the time of receiving the medical treatment request from the patient, a process is performed to present the working conditions notice information to the user. Therefore, even if the medical institution in charge of the patient is unable to treat the patient, the doctor's affiliation can be smoothly switched, and the patient can be treated at the required timing.

[0183] According to the medical treatment request system 1 of the present disclosure, the timing is based on the patient's medical treatment date and time, and the processing of presenting the working conditions notice information to the user is performed at that timing. Therefore, when the scheduled medical treatment date and time approaches, the doctor's affiliation can be smoothly switched, and the patient can be treated.

[0184] Furthermore, according to the medical treatment request system 1 of the present disclosure, the timing for accepting a medical treatment request from a medical institution that has accepted the request for medical treatment from a patient is before the arrival of the patient's medical treatment date and time, and a process for presenting the working conditions notice information to a user is performed at that timing. Therefore, at the timing for accepting a medical treatment request from a medical institution that has accepted the request for medical treatment, a doctor's affiliation can be smoothly switched, and medical treatment for the patient can be provided.

[0185] In addition, according to the medical care request system 1 of the present disclosure, when an operation of consent is received from a doctor, a process is performed to have the doctor execute a step of transmitting the working conditions notice information. Therefore, the contents of the working conditions notice information that the doctor consented to can be stored at the doctor's hand.

[0186] In addition, according to the medical care request system 1 of the present disclosure, a process is performed to generate working conditions notice information including temporary affiliation to a medical institution based on information about the medical institution and information about the user. Therefore, the working conditions notice information can be automatically generated and smoothly presented to the doctor.

[0187] According to the medical treatment request system 1 of the present disclosure, the user is registered as a doctor who can provide medical treatment in response to a request from a medical institution. Therefore, by presenting the working conditions notice information to the doctor at the timing when medical treatment is required, such as when a patient requests medical treatment, it is possible to realize smooth medical treatment.

[0188] According to the medical treatment request system 1 of the present disclosure, the user is a medical institution, and is a doctor designated by a specific medical institution, and is registered as a doctor who can treat a medical treatment request from the specific medical institution. Therefore, the medical institution to which the request is made can give priority to making a medical treatment request to a doctor it desires.

[0189] According to the medical treatment request system 1 of the present disclosure, a user is registered together with information regarding the priority level, which indicates the priority level of the doctor to be requested by a specific medical institution. Therefore, the medical institution to which the request is made can preferentially request medical treatment from the doctor of the requester's choice. Even if the medical institution receives a response from the doctor indicating that the medical treatment is not agreed to, the medical treatment request system can execute a process of presenting the medical treatment notice information to the doctor with the next highest priority, thereby realizing a reliable medical treatment request without omissions.

[0190] Furthermore, according to the medical treatment request system 1 of the present disclosure, a user is extracted from among registered doctors who can treat patients based on information about the medical institution, and working conditions notice information including temporary affiliation to the medical institution is generated based on information about the medical institution and information about the extracted user, and the generated working conditions notice information is presented to the user. Therefore, working conditions notice information can be automatically generated and smoothly presented to doctors.

[0191] In addition, according to the medical treatment request system 1 of the present disclosure, the working conditions notice information is information indicating working conditions for performing remote medical treatment for patients and includes information that the medical treatment belongs temporarily to a medical institution. Therefore, it is possible to handle online medical treatment, and the convenience of the user who is a patient can be improved.

[0192] Although several embodiments of the present disclosure have been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.

[0193] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) A computer having a processor (39) and a memory unit (37) to be executed by a computer, the memory unit storing information on the consultation date and time when a medical institution will provide medical treatment to a patient of the medical institution, and the program causes the processor to execute the following steps: presenting (S654) to a first user, who is a doctor not affiliated with the medical institution, first information indicating working conditions for providing medical treatment to the patient, the first information including that the doctor temporarily belongs to the patient's medical institution, before the consultation date and time arrives; accepting (S601) an operation to agree to the first information from the first user before the consultation date and time arrives; and storing the first information in the memory unit by accepting the agreement operation (S655).

[0194] (Appendix 2) 2. The program according to claim 1, wherein in the step of storing the first information, the first information is stored in the storage unit together with information regarding the first user.

[0195] (Appendix 3) 3. The program according to claim 1 or 2, wherein a request for medical treatment from a patient is accepted before the patient's medical treatment date and time arrives.

[0196] (Appendix 4) The program according to claim 3, wherein in the step of presenting the first information, when the medical institution is unable to treat the patient at a timing when the medical treatment request from the patient is received, the first information is presented to the first user.

[0197] (Appendix 5) 3. The program according to claim 1 or 2, wherein the timing is based on the consultation date and time and is before the patient's consultation date and time arrives.

[0198] (Appendix 6) The program according to claim 1 or 2, wherein the timing for accepting a medical treatment request from a medical institution that has accepted a medical treatment request from a patient is before the arrival of the patient's medical treatment date and time.

[0199] (Appendix 7) 7. The program according to any one of appendices 1 to 6, which executes a step (S656) of transmitting first information to the first user when an operation of consent is received from the first user.

[0200] (Appendix 8) A program described in any one of Appendices 1 to 7, which executes, in a step of presenting first information, a step of generating first information including temporary affiliation to a medical institution based on information about the medical institution and information about the first user, and a step of presenting the generated first information to the first user.

[0201] (Appendix 9) A program described in any one of appendices 1 to 8, wherein the first user is registered as a doctor who can provide medical treatment in response to requests for medical treatment from medical institutions.

[0202] (Appendix 10) A program as described in Appendix 9, wherein the first user is a medical institution and a doctor designated by a specific medical institution, and is registered as a doctor who can provide medical treatment in response to a request for medical treatment from the specific medical institution.

[0203] (Appendix 11) 11. The program of claim 10, wherein the first user is registered along with information regarding priority indicating a priority order of doctors to be referred by a particular medical institution.

[0204] (Appendix 12) A program described in any one of Appendices 9 to 11, which executes the steps of: in a step of presenting first information, extracting a first user from among registered doctors who can provide medical treatment based on information about the medical institution; generating first information including temporary affiliation to the medical institution based on information about the medical institution and information about the extracted first user; and presenting the generated first information to the first user.

[0205] (Appendix 13) 13. The program of any one of appendices 1 to 12, wherein the first information is information indicating working conditions for performing remote medical procedures on patients, the information including temporary affiliation to a medical institution.

[0206] (Appendix 14) 14. The program of claim 1, wherein, when an operation to agree to the first information is received from the first user, medical information regarding the patient's past medical history held by the medical institution is presented to the first user during a period in which the first user temporarily belongs to the medical institution.

[0207] (Appendix 15) The program described in Appendix 14, which accepts medical record information regarding the medical treatment from the first user after the first user has completed the medical treatment of the patient, and updates medical information regarding the patient's past medical history based on the accepted medical record information.

[0208] (Appendix 16) A method to be executed by a computer having a processor (39) and a memory unit (37), the memory unit storing information on the consultation date and time when a medical institution will provide medical treatment for a patient of the medical institution, and the processor executes the following steps: a step (S654) of presenting, to a first user who is a doctor not affiliated with the medical institution, first information indicating working conditions for providing medical treatment to the patient, the first information including that the doctor temporarily belongs to the patient's medical institution, before the consultation date and time arrives; a step (S601) of accepting an operation to agree to the first information from the first user before the consultation date and time arrives; and a step (S655) of storing the first information in the memory unit by accepting the agreement operation.

[0209] (Appendix 17) An information processing device comprising a control unit (39) and a memory unit (37), the memory unit storing information on the consultation date and time when a medical institution provides medical treatment for a patient of the medical institution, and the control unit executes the steps of: presenting (S654) to a first user who is a doctor not affiliated with the medical institution, before the patient's consultation date and time arrives, first information indicating working conditions for providing medical treatment to the patient, the first information including a temporary affiliation to the patient's medical institution; accepting (S601) an operation to agree to the first information from the first user before the consultation date and time arrives; and storing the first information in the memory unit by accepting the agreement operation (S655). [Explanation of symbols]

[0210] 1: medical treatment request system, 10: patient side terminal device, 20: doctor side terminal device, 22: communication IF, 23: input device, 24: output device, 27: memory, 28: storage unit, 29: processor, 30: server, 32: communication IF, 33: input / output IF, 35: memory, 36: storage, 39: processor, 40: medical institution side terminal device, 42: communication IF, 43: input device, 44: output device, 45: memory, 46: storage unit , 49: processor, 80: network, 211: antenna, 212: antenna, 221: first wireless communication unit, 222: second wireless communication unit, 230: operation reception unit, 231: touch sensitive device, 232: display, 240: audio processing unit, 241: microphone, 242: speaker, 250: position information sensor, 260: camera, 270: memory unit, 271: user information, 272: working conditions notice information information, 281: input operation reception unit, 282: transmission / reception unit, 283: notification control unit, 284: data processing unit, 301: communication unit, 302: memory unit, 303: control unit, 3021: medical treatment request information management database, 3022: scheduled medical treatment information management database, 3023: patient medical information management database, 3024: medical institution information management database, 3025: doctor information management database, 3026: consent information management database, 3027: working conditions notice information, 3031: reception control module, 3032: transmission control module, 3033: medical treatment request information acquisition module, 3034: scheduled medical treatment information acquisition module, 3035: patient medical information acquisition module, 3036: medical institution information acquisition module, 3037: doctor information acquisition module, 3038: working conditions notice information generation module, 3039: consent information acquisition module

Claims

1. A program to be executed on a computer equipped with a processor, The program is provided to the processor: A step of receiving a request from the patient for medical treatment at a medical institution in the patient's place of residence, The steps include presenting a first user, who is a physician not affiliated with the aforementioned medical institution, with first information indicating the working conditions for performing medical treatment on the patient, which includes the fact that the patient is temporarily affiliated with the aforementioned medical institution, before the scheduled date and time for the patient's consultation. A step of receiving an operation from the first user to consent to the first information before the date and time of the medical consultation arrives, A program that executes something.

2. The program further provides the processor with: The program according to claim 1, which causes the program to perform the step of storing the first information in a storage unit by accepting the aforementioned consent operation.

3. The program according to claim 2, wherein in the step of storing the first information, the first information is stored in the storage unit together with information relating to the first user.

4. The program according to claim 1 or 3, wherein the timing for receiving a medical consultation request from the patient is before the patient's scheduled consultation date and time arrives.

5. The program according to claim 4, wherein, in the step of presenting the first information, if the medical institution is unable to provide medical treatment to the patient at the time of receiving a medical treatment request from the patient, the program presents the first information to the first user.

6. The program according to claim 1 or 3, wherein the timing based on the date and time of the patient's consultation is before the date and time of the consultation arrives.

7. The timing for receiving a medical consultation request from the medical institution that received the medical consultation request from the patient is before the scheduled date and time for the patient's consultation arrives. The program according to claim 1 or 3.

8. The program according to claim 1 or 3, which, when it receives an operation of consent from the first user, causes the program to perform the step of transmitting the first information to the first user.

9. In the step of presenting the first information, A step of generating first information, including temporary affiliation with the medical institution, based on the information relating to the medical institution and the information relating to the first user, The program according to claim 1 or 3, which causes the program to perform the step of presenting the generated first information to the first user.

10. The first user is registered as a physician who can provide medical care in response to a medical request from the medical institution. The program according to claim 1 or 3.

11. The program according to claim 10, wherein the first user is a physician designated by a specific medical institution and is registered as a physician capable of providing medical care in response to a medical request from the specific medical institution.

12. The program according to claim 11, wherein the first user is registered along with priority information representing the priority order of physicians requested by the specific medical institution.

13. In the step of presenting the first information, Based on the information regarding the aforementioned medical institution, the first user is selected from among the registered physicians who are available to provide medical care. The program according to claim 10, which performs the steps of generating first information, including temporary affiliation with the medical institution, based on the information relating to the medical institution and the extracted information relating to the first user, and presenting the generated first information to the first user.

14. The program according to claim 1 or 3, wherein the first information is information indicating working conditions for performing remote medical treatment for the patient, and including information that temporarily belongs to the medical institution.

15. The program according to claim 1 or 3, which, when it receives an operation from the first user to consent to the first information, presents the first user with medical information relating to the patient's past medical history held by the medical institution during the period in which the patient temporarily belongs to the medical institution.

16. After the first user has completed the patient's medical treatment, the system receives medical record information related to the treatment from the first user, and updates the patient's medical information regarding their past medical history based on the received medical record information. The program according to claim 15.

17. A method for causing a computer equipped with a processor to execute, The aforementioned processor, A step of receiving a request from the patient for medical treatment at a medical institution in the patient's place of residence, The steps include presenting a first user, who is a physician not affiliated with the aforementioned medical institution, with first information indicating the working conditions for performing medical treatment on the patient, which includes the fact that the patient is temporarily affiliated with the aforementioned medical institution, before the scheduled date and time for the patient's consultation. A step of receiving an operation from the first user to consent to the first information before the date and time of the medical consultation arrives, How to do it.

18. An information processing device comprising a control unit, The control unit, A step of receiving a request from the patient for medical treatment at a medical institution in the patient's place of residence, The steps include presenting a first user, who is a physician not affiliated with the aforementioned medical institution, with first information indicating the working conditions for performing medical treatment on the patient, which includes the fact that the patient is temporarily affiliated with the aforementioned medical institution, before the scheduled date and time for the patient's consultation. A step of receiving an operation from the first user to consent to the first information before the date and time of the medical consultation arrives, An information processing device that performs the following actions.