Program, method, and information processing device

Abstract

To surely reflect the latest medical content on medical information of a patient acquired from a medical record database of a medical institution.SOLUTION: There is provided a program causing a computer including a processor (29) and a storage unit (25) to perform the following steps of: acquiring first information, which is medical information of a patient stored in a medical record database of a medical institution (S651); presenting the first information to a second user, who is a doctor carrying out medical care of a patient at the timing based on the date and time of the medical care of the patient (S652); accepting medical record information on the medical content of the patient from the first user after the end of the medical care (S653); updating the first information on the basis of the medical record information (S654); and storing the updated first information as second information, which is medical information reflecting the medical content of the patient (S655).SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] When a doctor examines a patient at home, it is common for the doctor to check the patient's medical information during the examination. As a means for checking such medical information, a technique is known in which the doctor refers to the patient's medical information stored in the electronic medical record database of the medical institution.

[0003] Patent Document 1 describes technology related to a system for supporting medical examinations and guidance for patients eligible for home medical care, which shares the patient's medical information with doctors who provide home medical care. This system describes how the home medical care information stored by the patient is sent via a network to the doctor's terminal in charge of the patient at a time based on the patient's scheduled appointment date, and the home medical care information sent to the doctor's terminal is displayed. [Prior art documents] [Patent documents]

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

[0005] However, while the technology of Patent Document 1 allows the patient's medical information to be shared in advance with a doctor providing at-home medical care, etc., the task of updating the medical information before the medical treatment is left to the doctor after the medical treatment is completed, so if the doctor forgets to update the information, the doctor may not be able to provide the correct medical treatment based on the previous medical treatment when the next medical treatment is performed. Even if the doctor updates the information based on the medical treatment, if there is an error in the input content or insufficient information, the doctor may not be able to provide the correct medical treatment when the next medical treatment is performed.

[0006] Therefore, the present disclosure provides a technology that enables a doctor providing medical treatment to receive shared medical information of a patient at an appropriate time and ensures that the latest medical treatment details are reflected in the patient's medical information. [Means for solving the problem]

[0007] According to one embodiment, a computer program is provided that includes a processor and a storage unit, and the storage unit stores information on the date and time of medical treatment at a medical institution for a patient of the medical institution. The computer program is for processing medical information of patients stored in a medical record database of the medical institution, and the storage unit stores information on the date and time of medical treatment at the medical institution for a patient of the medical institution. The computer program executes the following steps: acquiring first information, which is medical information of the patient stored in the medical record database of the medical institution, from the medical record database of the medical institution, presenting the first information to a first user who is a doctor who treats the patient, at a timing based on the date and time of the medical treatment of the patient, accepting medical record information related to the medical treatment of the patient from the first user after the medical treatment of the patient is completed, updating the first information based on the accepted medical record information, and storing the updated first information as second information, which is medical information of the patient reflecting the medical treatment. Effect of the Invention

[0008] According to the present disclosure, a patient's medical information is shared with the doctor treating the patient at the time of the patient's appointment, and after the appointment is completed, medical record information regarding the treatment details is received from the doctor, and the patient's medical information is updated based on the received medical record information, thereby ensuring that the latest treatment details are reflected in the patient's medical information. [Brief description of the drawings]

[0009] [Figure 1]1 is a diagram showing the overall configuration of an electronic medical record system 1 according to an embodiment. [Diagram 2] 2 is a block diagram showing the functional configuration of a doctor's terminal device 10. FIG. [Diagram 3] FIG. 2 is a block diagram showing the functional configuration of a server 20. [Figure 4] FIG. 2 is a diagram showing the data structure of a scheduled medical treatment information management database 2021. [Diagram 5] FIG. 2 is a diagram showing the data structure of a patient medical information management database 2022. [Figure 6] FIG. 2 is a diagram showing the data structure of a doctor information management database 2023. [Figure 7] FIG. 2 is a diagram showing the data structure of a medical institution information management database 2024. [Figure 8] FIG. 2 is a diagram showing the data structure of an approval history information management database 2025. [Figure 9] FIG. 2 is a diagram showing the data structure of a consent information management database 2027. [Figure 10] 13 is a flowchart showing the operation of processing patient medical information stored in a medical record database. [Figure 11] 13 is a flowchart showing another example of processing of medical record information received from a doctor who has treated a patient. [Figure 12] 13 is a flowchart showing another example of a process for presenting medical information of a patient to a doctor. [Figure 13] 13 is a flowchart showing an example of authentication processing for a doctor providing medical care to access information in the electronic medical record system 1. [Figure 14] 13 is a flowchart showing an example of authentication processing for a doctor who has performed medical treatment to transmit medical record information relating to the medical treatment content to the server 20. [Figure 15] FIG. 13 is a diagram showing an example of a screen of patient medical information presented on a doctor's terminal device. [Figure 16] 13 is a diagram showing an example of a screen of medical record information to be transmitted to a server, which is displayed on a doctor's terminal device. FIG. [Figure 17] 13 is a diagram showing an example of a screen displayed on a medical institution's terminal device for requesting approval of a patient's medical information. FIG. 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, the patient's medical information obtained from the medical institution's medical record database is presented to a user, who is the doctor treating the patient, at the time of the patient's consultation date and time, and after the consultation is completed, medical record information regarding the contents of the consultation is received from the doctor, and the patient's medical information is updated based on the received medical record information.

[0012] <1.1 Overall configuration of the electronic medical record system> Fig. 1 is a block diagram showing an example of the overall configuration of an embodiment of an electronic medical record system 1. As shown in Fig. 1, the electronic medical record system 1 includes a doctor's terminal device 10, a server 20, a medical institution's terminal device 30, and a medical record database 40, and these devices are connected to each other via a network 80 so as to be able to communicate with each other.

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

[0014] The doctor's terminal device 10 executes a program to provide the user with an environment for operating the electronic medical record system 1 according to the program. The doctor's terminal device 10 reads and executes the program to establish a communication connection between the doctor's terminal device 10 and the server 20. The doctor's terminal device 10 also accepts the presentation of the patient's medical information from the server 20, and transmits medical record information related to the medical treatment to the server 20 after the medical treatment is completed.

[0015] As shown in FIG. 1, the doctor side terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 17, a storage unit 18, and a processor 19.

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

[0017] The input device 13 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.).

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

[0019] The memory 17 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).

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

[0021] The processor 19 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.

[0022] The server 20 is a device that manages a series of processes related to the electronic medical record system 1. The server 20 presents the patient's medical information obtained from the medical record database 40 of the medical institution to the doctor who treats the patient at a timing based on the date and time of the patient's medical treatment, and after the treatment is completed, performs a process of updating the patient's medical information based on the medical record information received from the doctor. The server 20 manages various data such as scheduled medical treatment information, patient medical treatment information, and doctor information who treats the patient.

[0023] The server 20 includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0024] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0025] The input / output IF 23 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.

[0026] The memory 25 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).

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

[0028] 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.

[0029] The medical institution side terminal device 30 is a device operated by a medical institution. The medical institution side terminal device 30 is, for example, a mobile terminal such as a smartphone or a tablet, a PC (Personal Computer), or the like.

[0030] The medical institution side terminal device 30 includes a communication IF (Interface) 32 , an input device 33 , an output device 34 , a memory 35 , a storage unit 36 ​​, and a processor 39 .

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

[0032] The input device 33 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.).

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

[0034] 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).

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

[0036] 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.

[0037] The medical record database 40 is, for example, a database owned by a medical institution, and stores the medical information of patients. The medical record database 40 is not limited to being owned by a medical institution, but may also be a medical record database on the cloud or other such entity owned by an institution other than a medical institution, such as a cloud-based electronic medical record system. Therefore, in the following explanation, a database owned by a medical institution is exemplified as the medical record database 40, but the database may also be applied to an embodiment in which various processes are performed based on the medical information of patients stored in the database of a cloud-based electronic medical record system.

[0038] <1.2 Functional configuration of the doctor's terminal device 10> FIG. 2 is a diagram showing the functional configuration of the doctor's terminal device 10. The doctor's terminal device 10 includes a plurality of antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to each antenna, an operation reception unit 130, a voice processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a storage unit 170, and a control unit 180. The doctor's terminal device 10 also has functions and configurations (for example, 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 10 is electrically connected by a bus or the like.

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

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

[0041] The first wireless communication unit 121 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 111 so that the doctor's terminal device 10 can communicate with other wireless devices. The second wireless communication unit 122 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 112 so that the doctor's terminal device 10 can communicate with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 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 121 and the second wireless communication unit 122 perform modulation and demodulation and frequency conversion of wireless signals transmitted and received by the doctor's terminal device 10, and provide the received signals to the control unit 180.

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

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

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

[0045] The position information sensor 150 is a sensor that detects the position of the doctor's terminal device 10, 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 10 equipped with the GPS module is detected based on the received signals.

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

[0047] The storage unit 170 is configured with, for example, a flash memory, and stores data and programs used by the doctor side terminal device 10. In one aspect, the storage unit 170 stores user information 171, authentication information 172, and medical record information 173.

[0048] The user information 171 is information about a user who is a doctor who treats patients. The user information includes information about a user ID, information about a user's name, information about a user's age, information about a user's sex, information about a medical institution to which the user usually belongs, information about a user's work schedule, and the like.

[0049] The authentication information 172 is information for authenticating that the user is a doctor who can treat patients and can access the medical information of the patient acquired from the electronic medical record database. The authentication information includes information related to an authentication ID, information related to a password, and the like.

[0050] The medical record information 173 is information about medical treatment contents created by a doctor after the medical treatment is completed. The medical record information 173 includes information about the patient's symptoms according to diagnosis, information about the patient's medical history, information about prescribed medicines, and the like.

[0051] The control unit 180 reads a program stored in the storage unit 170 and executes commands included in the program to control the operation of the doctor's terminal device 10. The control unit 180 is, for example, an application that is pre-installed in the doctor's terminal device 10. The control unit 180 operates according to the program to fulfill the functions of an input operation reception unit 181, a transmission / reception unit 182, a notification control unit 183, and a data processing unit 184.

[0052] The input operation reception unit 181 performs a process of receiving an input operation of a user to an input device such as the touch-sensitive device 131. The input operation reception unit 181 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 131 with a finger or the like.

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

[0054] The notification control unit 183 performs a process of presenting information to a doctor who is a user. The notification control unit 183 performs a process of displaying a display image on the display 132, a process of outputting sound from the speaker 142, and the like.

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

[0056] <1.3 Functional configuration of server 20> 3 is a diagram showing a functional configuration of the server 20. As shown in FIG. 3, the server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

[0057] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0058] The memory unit 202 stores a scheduled medical treatment information management database 2021, a patient medical information management database 2022, a doctor information management database 2023, a medical institution information management database 3024, an approval history information management database 2025, working conditions notice information 3026, a consent information management database 3027, etc.

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

[0060] The patient medical information management database 2022 is a database for managing patient medical information (first information) acquired from the medical institution's medical record database 40. Details will be described later.

[0061] The doctor information management database 2023 is a database for managing various information related to doctors who treat patients. Details will be described later.

[0062] The medical institution information management database 2024 is a database for managing various information related to medical institutions that hold medical information of patients, as will be described in detail later.

[0063] The approval history information management database 2025 is a database for managing information indicating the history of approval from medical institutions for the medical information of patients that reflects the contents of medical treatment. Details will be described later.

[0064] The information on notice of working conditions 2026 is a database that includes information on the notice of working conditions agreed to by a doctor who has been requested to treat a patient when the medical institution requests a doctor other than the medical institution to treat the patient. Details will be described later.

[0065] The consent information management database 2027 is a database for managing various information related to consent to the information on the notice of working conditions received from a doctor in response to a request from a medical institution. Details will be described later.

[0066] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. The control unit 203 operates in accordance with the program to perform functions indicated as a reception control module 2031, a transmission control module 2032, a scheduled medical treatment information acquisition module 2033, a patient medical information acquisition module 2034, a doctor information acquisition module 2035, a medical institution information acquisition module 2036, an approval history information acquisition module 2037, an authentication information generation module 2038, a working conditions notice information generation module 2039, and a consent information acquisition module 2040.

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

[0068] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0069] The scheduled medical treatment information acquisition module 2033 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 ID of the medical institution that holds the patient's medical information, information regarding the patient's ID, information regarding the patient's name, information regarding the patient's age, information regarding the patient's sex, information regarding the patient's contact information, information regarding the scheduled medical treatment date and time, and information regarding the previous medical treatment date and time. The scheduled medical treatment information acquisition module 2033 stores the acquired information regarding scheduled medical treatment in the scheduled medical treatment information management database 2021.

[0070] The patient medical information acquisition module 2034 performs a series of processes for managing the patient's medical information (first information) acquired from the medical institution's chart database 40. The patient's medical information includes information on the patient's name, information on the ID of the medical institution that holds the patient's medical information, information on the details of the previous medical treatment, and information on the details of the patient's medical treatment after the current treatment. The patient medical information acquisition module 2034 stores the acquired patient's medical information in the patient medical information management database 2022.

[0071] The doctor information acquisition module 2035 performs a series of processes for managing information about users who are 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 registration ID, information about the authentication ID, and password information. The doctor information acquisition module 2035 stores the acquired information about doctors in the doctor information management database 2023.

[0072] The medical institution information acquisition module 2036 performs a series of processes for managing information about medical institutions that hold medical information about patients. 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 medical institutions in the medical institution information management database 2024. The designated doctor ID does not necessarily have to include the first to third pieces of information, but may include four or more designated doctor IDs.

[0073] The approval history information acquisition module 2037 performs a series of processes to manage information related to the approval history of the medical information of a patient that reflects the medical treatment details by the medical institution. The information related to the approval history includes information related to the medical treatment ID, information related to the doctor user ID, information related to the patient ID, information related to the medical treatment date and time, information related to the approved medical record information, and information related to the approval date and time. The approval history information acquisition module 2037 stores the approval history information in the approval history information management database 2025.

[0074] The authentication information generation module 2038 performs a series of processes for generating authentication information for authenticating that a user is permitted to access the medical information of a patient obtained from the electronic medical record database. The authentication information generated by the authentication information generation module 2038 includes authentication information for authenticating that the user is a registered user in advance as a doctor who can provide medical care, temporary authentication information that is temporarily given to a user who is not registered as a doctor who can provide medical care, and the like.

[0075] The working conditions notice information generation module 2039 performs a series of processes for generating working conditions notice information to be presented to a doctor who is requested to treat a patient when the medical institution requests the medical treatment from a doctor other than the medical institution. The generated working conditions notice information includes information indicating the working conditions for performing medical treatment on a patient and information indicating that the medical institution temporarily belongs to the medical institution. The working conditions notice information generation module 2039 generates working conditions notice information based on information about the medical institution in charge of the patient who is the subject of the medical treatment and information about the doctor who is the subject of the request for medical treatment. The working conditions notice information generation module 2039 stores the generated working conditions notice information in the storage unit 202.

[0076] In addition, "temporarily belonging" means that a doctor user belongs to a specific medical institution during the employment institution (contract period), which is one of the working conditions included in the employment conditions notice information. For example, a doctor can access and view the medical information of patients held by a medical institution during the period of his / her affiliation to a specific medical institution, but cannot view the information after the period of his / her affiliation has expired.

[0077] The consent information acquisition module 2040 performs a series of processes for managing information regarding consent to the working conditions notice information from doctors. The information regarding consent to the working conditions notice information includes information regarding the doctor's user ID, information regarding the affiliated medical institution ID to which the user usually belongs, information regarding consent to the working conditions notice information, information regarding the date and time of consent to the medical treatment request, information regarding the affiliated institution ID of the switching destination when switching affiliation, etc. When the consent information acquisition module 2040 receives an operation to consent to the working conditions notice information from a doctor user, it stores the acquired information regarding consent to the medical treatment request in the consent information management database 2027.

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

[0079] 4 is a diagram showing the data structure of the scheduled medical treatment information management database 2021. Each record of the scheduled medical treatment information management database 2021 includes an item "scheduled medical treatment ID", an item "medical institution ID", an item "patient ID", an item "patient name", an item "patient age", an item "patient sex", an item "patient contact information", an item "scheduled medical treatment date and time", and an item "last medical treatment date and time". In the illustrated example, an example capable of accepting three medical treatment IDs is shown, but this is not limited to this.

[0080] The item "scheduled medical treatment ID" is information for identifying a scheduled medical treatment subject.

[0081] The item "medical institution ID" is information for identifying the medical institution in charge of the patient who is the subject of medical treatment.

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

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

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

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

[0086] 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.

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

[0088] The item "Last medical examination date and time" is information indicating the date and time of the last medical examination.

[0089] 5 is a diagram showing the data structure of the patient medical information management database 2022. Each record in the patient medical information management database 2022 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 regarding medical treatment content at the time of medical treatment". In the illustrated example, three examples of medical treatment history are shown, but the present invention is not limited to this.

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

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

[0092] The item "medical institution ID" is information for identifying each medical institution that holds the patient's medical information.

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

[0094] 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.

[0095] 6 is a diagram showing the data structure of the doctor information management database 2023. Each record of the doctor information management database 2023 includes an item "user ID", an item "user name", an item "affiliated medical institution ID", an item "user contact information", an item "registration ID", an item "authentication ID", and an item "password information". In the illustrated example, three doctors are shown, but the present invention is not limited to this.

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

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

[0098] The item "affiliated medical institution ID" is information for identifying the medical institution to which the user normally belongs. The medical institution to which the user belongs may be the same as the medical institution in charge of the patient.

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

[0100] The item “Registration ID” is identification information indicating that the user is registered as a user who can use the electronic medical record system 1.

[0101] The item "authentication ID" is information for authenticating that the user is a user who can access the medical information of the patient acquired from the medical record database 40, and is information for identifying the user.

[0102] The item "password information" is information for authenticating that the user is a user who can access the patient's medical information obtained from the electronic medical record database, and is password information that is required during authentication processing.

[0103] 7 is a diagram showing the data structure of the medical institution information management database 2024. Each record of the medical institution information management database 2024 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.

[0104] The item "medical institution ID" is information that identifies each medical institution that holds medical information of a patient.

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

[0106] 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.

[0107] 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 available for medical treatment when medical information requests treatment from a doctor other than the medical institution. 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."

[0108] 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 available for medical treatment when medical information requests treatment from a doctor other than the medical institution. 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."

[0109] 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 available for medical treatment when medical information requests treatment from a doctor other than the medical institution. 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."

[0110] 8 is a diagram showing the data structure of the approval history information management database 2025. Each record in the approval history information management database 2025 includes an item "clinical practice ID", an item "user (doctor) ID", an item "user (patient) ID", an item "approval / non-approval", an item "approved medical record information", and an item "approval date and time". In the illustrated example, three management examples are shown, but the present invention is not limited to these.

[0111] The item "Treatment ID" is information for identifying a subject of treatment.

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

[0113] The item "patient ID" is information for identifying a patient.

[0114] The item "approval" is information indicating whether the medical institution in charge of the patient approves the medical information of the patient that reflects the medical treatment details.

[0115] The item "approved medical information" is medical information of a patient that reflects the contents of medical treatment, and is information that has been approved by the medical institution in charge of the patient.

[0116] The item "approval date and time" is information indicating the date and time when the medical institution in charge of the patient approved the patient's medical information reflecting the medical treatment details.

[0117] 9 is a diagram showing the data structure of the consent information management database 2027. Each record in the consent information management database 2027 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.

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

[0119] The item "user name" is information that indicates the name of a user who is a doctor.

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

[0121] 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.

[0122] 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.

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

[0124] <3.1 Example of operation> 10 is a diagram showing the flow of processing the patient's medical information stored in the medical record database via the server 20. In the following example, a case will be described in which the patient's past medical information is presented to a user who is a doctor who is treating the patient, medical record information regarding the contents of the treatment is received from the doctor after the treatment is completed, and the patient's medical information is updated based on the medical record information.

[0125] In step S651, the server 20 acquires the patient's medical information (first information) from the medical record system of the medical institution. The timing of acquiring the patient's medical information can be set arbitrarily, for example, a certain period of time before the medical examination date and time, or a regular date and time such as 9:00 a.m. every Monday. In addition, the patient's medical information can be acquired under any rule, such as acquiring it for each patient, or acquiring it all at once (in a batch) for all patients managed by the electronic medical record system 1.

[0126] In step S652, the server 20 presents the patient's medical information to the user at a timing based on the date and time of the patient's medical treatment. The user who has received the medical information can check the patient's medical information on the display 132 of the doctor's terminal device 10. Any condition can be set as the timing for presenting the patient's medical information. For example, the server 20 presents the medical information within six hours before the start of medical treatment.

[0127] In step S601, the doctor's terminal device 10 accepts from the user, after the end of medical treatment of the patient, chart information on the medical treatment of the patient created by the user. The user inputs the chart information using the doctor's terminal device 10 and transmits it to the server 20. The chart information to be transmitted includes information on the patient's symptoms based on diagnosis, information on the interview with the patient, information on prescribed medicines, etc.

[0128] In step S653, the server 20 updates the patient's medical information based on the received chart information. Specifically, for example, the server 20 extracts text information or the like that is necessary as the patient's medical information from the received chart information, and updates the patient's medical information by adding the extracted information to the patient's medical information up to the previous medical examination.

[0129] In step S654, the server 20 stores the updated medical information of the patient. In this case, the server 20 updates the patient medical information management database 2022 and stores the medical information of the patient.

[0130] In step S655, the server 20 requests the medical institution that holds the patient's medical information to approve the updated medical information of the patient. This process is executed to reflect the updated medical information of the patient stored in the server 20 in the medical institution's chart database 40. When requesting approval, the server 20 presents the updated medical information of the patient to the medical institution.

[0131] In step S701, an operation to approve the updated medical information of the patient is accepted from the medical institution side terminal device 30. Specifically, if the medical institution in charge of the patient judges that there is no problem with the updated medical information of the patient, the medical institution performs an operation to approve in response to the operation from the medical institution. On the other hand, if the medical institution judges that there is a problem with the updated medical information of the patient, the medical institution performs an operation to not approve in response to the operation from the medical institution.

[0132] In step S656, the server 20 updates the patient's medical information stored in the medical institution's chart database 40 in response to the approval operation by the medical institution.

[0133] <3.2 Operation example 2> FIG. 11 is a diagram showing another example of processing of chart information received via the server 20 from a user who is a doctor providing medical care.

[0134] In step S601, the doctor's terminal device 10 receives, from the doctor user after the completion of medical treatment for the patient, chart information on the medical treatment details of the patient created by the user. The user inputs the chart information using the doctor's terminal device 10 and transmits it to the server 20. The chart information to be transmitted includes information on the patient's symptoms based on diagnosis, information on the interview with the patient, information on prescribed medicines, and the like.

[0135] In step S6531, the server 20 judges whether the received medical record information is appropriate. In this process, the appropriateness is judged based on whether the information included in the received medical record information includes information necessary for updating the patient's medical information. For example, if the information included in the received medical record information is unclear as information necessary for updating the patient's medical information, or if the information does not include the necessary information, the server 20 judges the received medical record information to be inappropriate.

[0136] In step S6532, when the server 20 determines that the received chart information is inappropriate, it transmits a notification to the doctor's terminal device 10 to prompt the doctor to correct the chart information. The notification to prompt the doctor to correct the chart includes, for example, information on the reason why the chart information is inappropriate, information on the part that is inappropriate, etc.

[0137] The user who has received the notification uses the doctor's terminal device 10 to input the corrected chart information and resend it to the server 20. If the server 20 determines that the information contained in the re-received chart information is appropriate, it executes the process from step S654 onward in FIG.

[0138] <3.3 Operation example 3> FIG. 12 is a diagram showing another example of a process for presenting medical information of a patient to a user who is a doctor via the server 20. In the process shown in FIG.

[0139] In step S6001, the doctor's terminal device 10 receives a request from a doctor user to present medical information of a patient whom the user is planning to treat. The user inputs information related to the presentation request using the doctor's terminal device 10 and transmits it to the server 20. The request to present medical information is made at a timing based on the date and time of the patient's treatment. Specifically, the request is made within a certain period before the start of treatment, such as on the day of treatment or six hours before the start of treatment.

[0140] In step S6520, the server 20 presents the patient's medical information in response to a presentation request from the doctor. The doctor who has received the medical information can check the patient's medical information on the display 132 of the doctor's terminal device 10. When presenting the patient's medical information, conditions for presenting the information can be set. For example, the server 20 presents the medical information only if a presentation request is made within six hours before the start of medical treatment, and if a presentation request is made before that time, the server 20 can reject the request and notify the doctor's terminal device 10 to urge the doctor to make another presentation request within the target period.

[0141] <3.4 Operation example 4> FIG. 13 is a diagram showing an example of authentication processing for presenting medical information of a patient to a user who is a doctor providing medical care via the server 20. In FIG.

[0142] In step S6002, the doctor's terminal device 10 accepts input of authentication information from a doctor user. The user inputs, using the doctor's terminal device 10, information on an authentication ID and password information for authenticating that the user is allowed to access the medical information of the patient acquired from the medical record database 40, as authentication information, and transmits the information to the server 20. The authentication information in this step is not limited to information on an authentication ID and password information, and other information for authentication may also be applied.

[0143] In step S6501, the server 20 compares the received authentication information with registered authentication information and authenticates the received authentication information.

[0144] In step S6502, after authentication, the server 20 presents the patient's medical information to the user.

[0145] <3.5 Operation example 5> FIG. 14 is a diagram showing an example of authentication processing for accepting, via the server 20, chart information on medical treatment contents created by a user who is a doctor providing medical treatment.

[0146] In step S6002, the doctor's terminal device 10 accepts input of authentication information from a doctor user. The user inputs, using the doctor's terminal device 10, information on an authentication ID and password information for authenticating that the user is allowed to access the medical information of the patient acquired from the medical record database 40, as authentication information, and transmits the information to the server 20.

[0147] In step S6501, the server 20 compares the received authentication information with registered authentication information and authenticates the received authentication information.

[0148] In step S6010, after authentication, the doctor's terminal device 10 accepts chart information on the contents of medical treatment of the patient from the user who has performed medical treatment.

[0149] <4 Screen example> FIG. 15 is a diagram showing an example of a screen of the medical information of a patient presented to the doctor's terminal device.

[0150] 15 is a screen example displayed on the doctor side terminal device 10 of a doctor user from the server 20. This corresponds to the processing of step S652 in FIG. 8 and step S6520 in FIG.

[0151] As shown in FIG. 15, the doctor's terminal device 10 displays an area 801A for displaying information regarding the viewing expiration date of the presented information, an area 801B for displaying information regarding the patient being treated, an area 801C for displaying information regarding scheduled medical treatment, and an area 801D for displaying information regarding the contents of medical treatment during the previous medical treatment.

[0152] In the area 801A, information on the viewing expiration date, which clearly indicates the period during which the presented medical information of the patient can be viewed, can be displayed. Specifically, information on the date and time during which the medical information of the patient can be viewed is displayed.

[0153] Area 801B can display information about the patient who is the subject of medical treatment and that the doctor needs to confirm before the medical treatment. Specifically, information about the patient's name, the patient's sex, the patient's date of birth and age, the patient's address, and the name of the medical institution in charge of the patient is displayed.

[0154] Area 801C can display information about the scheduled medical treatment that the doctor is planning to handle and that the doctor needs to confirm before the medical treatment. Specifically, information about contact information for contacting the patient during the medical treatment, such as the patient's name, the scheduled date and time of the medical treatment, the location of the medical treatment, the address of the medical treatment, and the patient's phone number, is displayed.

[0155] Area 801D can display information on the contents of the patient's previous medical examination, which is medical information that the doctor needs to confirm before the examination. Specifically, information on the interview at the previous medical examination, information on the condition after the diagnosis at the previous medical examination, information on the medicine prescribed at the previous medical examination, etc. are displayed.

[0156] The user checks the information about the patient displayed in area 801B, the information about the scheduled medical treatment displayed in area 801C, and the information about the previous medical treatment displayed in area 801D before attending the medical treatment.

[0157] FIG. 16 is a diagram showing an example of a screen showing chart information regarding the medical treatment of a patient, which is created after the medical treatment by a user who is a doctor who performed the medical treatment.

[0158] 16 is a screen example that is displayed on the doctor side terminal device 10 in response to a user operation. This corresponds to the processing in step S601 in FIG. 10 and FIG. 11 and step S6010 in FIG.

[0159] As shown in FIG. 16, the doctor's terminal device 10 displays an area 901A for displaying information about the doctor who created the medical record information, an area 901B for displaying information about the patient who was the subject of medical treatment, an area 901C for displaying information about the date, time and location of the treatment, an area 901D for displaying information about the contents of the patient's medical treatment, and an area 901E for displaying information for confirming whether or not the medical record information can be sent.

[0160] In the area 901A, information about the doctor who prepared the chart information on the medical treatment can be displayed after the medical treatment. Specifically, the name of the preparer (the name of the doctor who prepared the chart information), the name of the medical institution to which the doctor belongs, and information about the doctor's contact information are displayed.

[0161] Area 901B can display information about the patient who was the subject of medical treatment. Specifically, information about the patient's name, the patient's sex, the patient's date of birth and age, the patient's address, and the name of the medical institution treating the patient is displayed.

[0162] In the area 901C, information on the date, time and place of the medical treatment can be displayed. Specifically, information on the date and time (record) of the medical treatment, the medical place and the medical address of the medical treatment can be displayed.

[0163] In the area 901D, information about the contents of the medical treatment of the patient can be displayed. Specifically, information about the contents of the medical treatment, the prescribed medicine, and other matters to be noted as notes is displayed.

[0164] In the area 901E, information for confirming whether or not to transmit the medical chart information to the server 20 can be displayed. Specifically, link information (9011E) for performing a process for transmitting the medical chart information and link information (9012E) for performing a process for not transmitting the medical chart information are displayed.

[0165] The user checks information about the creator (doctor) of the medical record information displayed in area 901A, information about the patient displayed in area 901B, information about the date, time and place of the treatment displayed in area 901C, and information about the details of the patient's medical treatment displayed in area 901D, and then clicks on link information 9011E labeled "Send" if the user wishes to send the medical record information to server 20. On the other hand, if the user does not wish to send the medical record information, he or she clicks on link information 9012E labeled "Do not send."

[0166] FIG. 17 is a diagram showing an example of a screen for requesting approval from a medical institution for the medical information of a patient updated in the server 20. In FIG.

[0167] 17 is a screen example displayed on the medical institution side terminal device 30. This corresponds to the processing of steps S656 and S701 in FIG.

[0168] As shown in FIG. 17, the medical institution side terminal device 30 displays an area 1001A for displaying information about the doctor providing the medical treatment, an area 1001B for displaying information about the patient's medical treatment, and an area 1001C for displaying information for confirming whether the presented medical information can be approved.

[0169] Information about the doctor who treated the patient can be displayed in area 1001A. Specifically, the name of the creator (the name of the doctor who created the chart information), the name of the medical institution to which the doctor belongs, and information about the doctor's contact information are displayed.

[0170] In the area 1001B, information about the medical treatment of the patient can be displayed. Specifically, the patient's name, the patient's ID managed by the medical institution, the date and time of the medical treatment (record), the medical treatment content of this medical treatment, and other information to be written as notes are displayed.

[0171] Area 1001C can display information for confirming whether or not to approve the presented medical information. Specifically, link information (10011C) for performing a process to approve the content displayed as medical information and link information (10012C) for performing a process to not approve the content displayed as medical information are displayed.

[0172] The medical institution checks the information on the doctor providing the medical treatment displayed in area 1001A and the information on the patient's medical treatment displayed in area 1001B, and if the medical institution approves the content displayed as medical information, the medical institution clicks on link information 10011C labeled "Approve." On the other hand, if the medical institution does not approve the content displayed as medical information, the medical institution clicks on link information 10012C labeled "Do not approve."

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

[0174] (1) Processing when the user is not registered as a doctor who can provide medical care If a doctor requested by a medical institution or the like to treat a patient is not registered as a doctor who can treat the patient, i.e., is not registered as a user who can use the electronic medical record system 1, a process may be executed to grant temporary authentication information to the doctor to authenticate that the doctor is a user who can temporarily access the patient's medical information obtained from the medical record database 40 of the medical institution. Since this process grants temporary access authority to the doctor who is the user, it is possible to impose restrictions such as, for example, allowing the user to access only the medical information of the patient related to the treatment requested.

[0175] When the temporary authentication information is granted to a user, the user may request presentation of the patient's medical information based on the granted temporary authentication information, and in response to the request for presentation, a process may be executed to present the patient's medical information to the user.

[0176] In addition, when the temporary authentication information is granted to the user, the user may execute a process of transmitting medical record information to the server 20 based on the granted temporary authentication information.

[0177] (2) Processing when presenting patient medical information to a doctor who is not affiliated with a medical institution The server 20 may execute a process of presenting a user who is a doctor not affiliated with a medical institution, at a timing based on the date and time of the patient's medical treatment, with working conditions notice information, which is first information indicating working conditions for performing medical treatment on a patient and includes temporary affiliation to the medical institution, and by receiving an operation from the user to agree to the working conditions notice information.

[0178] In this case, the server 20 may execute a process of presenting the working conditions notice information, which indicates the working conditions for performing medical treatment on the patient and includes temporary affiliation to the medical institution, to the user who is a doctor designated in advance by the medical institution, at a timing based on the date and time of the patient's medical treatment. The doctor designated by the medical institution is determined, for example, based on the medical institution information stored in the medical institution information management database 2024.

[0179] As described above, according to the electronic medical record system 1 of the present disclosure, the medical information of the patient obtained from the medical record database of the medical institution is presented to the user, who is the doctor who treats the patient, at a timing based on the date and time of the patient's medical treatment, and after the treatment is completed, the medical record information related to the medical treatment is received from the user, the medical information of the patient is updated based on the received medical record information, and the updated medical information of the patient is stored. Therefore, the latest medical contents can be reliably reflected in the medical information of the patient.

[0180] Furthermore, according to the electronic medical record system 1 of the present disclosure, a process is performed to present the medical information of a patient to a user who is a doctor in response to a request from the user. This allows the doctor to receive the medical information of the patient at an appropriate time and provide smooth medical treatment.

[0181] Furthermore, according to the electronic medical record system 1 of the present disclosure, a request is made to the medical institution for approval of the patient's medical information updated in the server 20, and a process is performed to update the patient's medical information stored in the medical institution's medical record database in response to the approval operation by the medical institution. This ensures that the latest medical details are reflected in the medical institution's medical record database.

[0182] Furthermore, according to the electronic medical record system 1 disclosed herein, the suitability of the medical record information received from the user who is a doctor is judged, and if the received medical record information is judged to be inappropriate, a notification is sent to the user to prompt him / her to correct the medical record information. Therefore, even if there is an error in the medical record information created by the doctor, an opportunity to correct it is given, so that the latest medical content can be reliably reflected in the patient's medical information.

[0183] Furthermore, according to the electronic medical record system 1 of the present disclosure, a user is registered as a doctor who can treat patients, together with authentication information for authenticating that the user has access to the patient's medical information obtained from the medical record database. Therefore, only users who are authenticated doctors can access the electronic medical record system 1, ensuring the security of the medical information.

[0184] Furthermore, according to the electronic medical record system 1 of the present disclosure, the input of authentication information is accepted from a user who is a doctor, and the accepted authentication information is compared with registered authentication information to present the patient's medical information to the user. Therefore, only authenticated users who are doctors are presented with the patient's medical information, ensuring the security of the medical information.

[0185] Furthermore, according to the electronic medical record system 1 of the present disclosure, the input of authentication information is accepted from a doctor user, and the accepted authentication information is compared with registered authentication information to accept the transmission of medical record information from the doctor. Therefore, only authenticated users who are doctors can transmit medical record information to update the medical information of patients, ensuring the security of the medical information.

[0186] Furthermore, according to the electronic medical record system 1 of the present disclosure, when a user is not registered as a doctor who can treat a patient, temporary authentication information is provided to the user to authenticate that the user has temporary access to the patient's medical information, and the patient's medical information is presented to the user based on the provided temporary authentication information. Therefore, even if the doctor is not registered, the patient's medical information can be presented promptly without going through the process related to the formal registration procedure, and the doctor can smoothly treat the patient.

[0187] Furthermore, according to the electronic medical record system 1 of the present disclosure, when a user is not registered as a doctor who can treat patients, temporary authentication information is provided to the user to authenticate that the user has temporary access to the patient's medical information, and a process is performed to receive medical record information from the user based on the provided temporary authentication information. Therefore, even if a doctor is not registered, the doctor can quickly send medical record information without going through the process related to the formal registration procedure, so that the patient's medical information can be updated smoothly.

[0188] Furthermore, according to the electronic medical record system 1 of the present disclosure, a process is performed to periodically obtain the medical information of a patient from the medical record database of a medical institution. This eliminates the need to manage the timing of obtaining the medical information of a patient, such as obtaining the information each time the date and time of treatment approaches.

[0189] According to the electronic medical record system 1 of the present disclosure, the user is a doctor not belonging to a medical institution, and the working conditions notice information is presented to the user at a timing based on the date and time of the patient's medical treatment, the working conditions notice information including information indicating working conditions for performing medical treatment on the patient and including temporary affiliation to the medical institution of the patient, and an operation to consent to the working conditions notice information is received from the user, and by receiving the consent operation, the medical information of the patient is presented to the user. Therefore, even if the doctor does not belong to a medical institution, the doctor can receive the medical information of the patient by consenting to the presented working conditions notice information, and thus the medical treatment can be handled smoothly.

[0190] 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.

[0191] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) A program for processing medical information of a patient stored in a medical record database of a medical institution when executed by a computer having a processor (29) and a memory (25), the program executing the following steps: acquiring first information, which is medical information of the patient stored in the medical record database, from the medical institution's medical record database (40); presenting the first information to a first user, who is a doctor treating the patient, at a timing based on the date and time of the patient's medical treatment (S652); receiving medical record information regarding the medical treatment details of the patient from the first user after the medical treatment for the patient is completed (S653); updating the first information based on the received medical record information; and storing the updated first information as second information, which is medical information reflecting the medical treatment details of the patient (S655).

[0192] (Appendix 2) The program according to claim 1, wherein in the step of presenting medical information of the first user, the first information is presented to the first user in response to a presentation request from the first user (S6520).

[0193] (Appendix 3) A program described in Appendix 1 or 2, which executes a step (S656) of requesting approval from the medical institution for the second information stored in the storing step, a step (S701) of accepting an approval operation from the medical institution, and a step (S657) of updating the first information stored in the medical institution's medical record database to the approved second information in accordance with the approval operation by the medical institution.

[0194] (Appendix 4) A program described in any one of Appendices 1 to 3, which executes a step (S6531) of determining whether the received medical record information is appropriate, and a step (S6532) of sending a notification to the first user urging them to correct the medical record information if the received medical record information is determined to be inappropriate in the step of determining whether it is appropriate.

[0195] (Appendix 5) A program described in any one of Appendices 1 to 4, in which the first user is registered together with authentication information for authenticating that the first user is a doctor who is available to provide treatment and is a user who can access the first information obtained from the medical record database.

[0196] (Appendix 6) The program described in Appendix 5, in a step of presenting a patient's medical information, receives input of authentication information from a first user, and presents the first information to the first user by comparing the received authentication information with registered authentication information.

[0197] (Appendix 7) A program as described in Appendix 5 or 6, in which, in a step of accepting medical record information, input of authentication information is accepted from a first user, and the accepted authentication information is compared with registered authentication information to accept transmission of medical record information from a second user.

[0198] (Appendix 8) A program described in any one of Appendices 1 to 4, which, when the second user is not registered as a doctor who can provide medical treatment, grants the first user temporary authentication information to authenticate that the first user is a user who can temporarily access the first information, and presents the first information to the first user based on the granted temporary authentication information.

[0199] (Appendix 9) A program described in any one of Appendices 1 to 4, which, when the first user is not registered as a doctor who can provide medical treatment, grants the second user temporary authentication information to authenticate that the second user is a user who can temporarily access the first information, and accepts the transmission of medical record information from the first user based on the granted temporary authentication information.

[0200] (Appendix 10) 10. The program of claim 1, wherein in the step of acquiring the first information, the first information is acquired periodically from a medical institution's medical record database.

[0201] (Appendix 11) 11. The program of any one of appendices 1 to 10, wherein the program executes the steps of: presenting to the first user, the first user being a doctor not affiliated with a medical institution, third information indicating working conditions for performing medical treatment on a patient at a timing based on the patient's consultation date and time, the third information including the fact that the doctor temporarily belongs to the patient's medical institution; accepting an operation from the first user to agree to the third information; and presenting the first information to the first user by accepting the agreement operation.

[0202] (Appendix 12) A method for processing patient medical information stored in a medical institution's medical record database, the method being executed by a computer having a processor (29) and a memory (25), the method comprising the steps of: acquiring first information, which is the patient's medical information stored in the medical record database, from the medical institution's medical record database; presenting the first information to a first user, who is a doctor treating the patient, at a timing based on the date and time of the patient's medical treatment (S652); receiving medical record information regarding the patient's medical treatment from the first user after the patient's medical treatment is completed (S653); updating the first information based on the received medical record information; and storing the updated first information as second information, which is medical information reflecting the patient's medical treatment (S655).

[0203] (Appendix 13) An information processing device comprising a control unit (203) and a memory unit (202), the information processing device for processing medical information of a patient stored in a medical institution's medical record database, in which the control unit (203) executes the following steps: a step (S651) of acquiring first information, which is medical information of the patient stored in the medical record database, from the medical institution's medical record database; a step (S652) of presenting the first information to a first user, who is a doctor treating the patient, at a timing based on the date and time of the patient's medical treatment; a step (S653) of receiving medical record information regarding the patient's medical treatment from the first user after the patient's medical treatment is completed; a step (S654) of updating the first information based on the received medical record information; and a step (S655) of storing the updated first information as second information, which is medical information reflecting the patient's medical treatment. [Explanation of symbols]

[0204] 1: Electronic medical record system, 10: Doctor's terminal device, 12: Communication IF, 13: Input device, 14: Output device, 17: Memory, 18: Storage unit, 19: Processor, 20: Server, 22: Communication IF, 23: Input / output IF, 25: Memory, 26: Storage, 29: Processor, 30: Medical institution's terminal device, 32: Communication IF, 33: Input device, 34: Output device, 35: Memory, 36: Storage unit, 39: Processor, 40: Medical record data database, 80: network, 111: antenna, 112: antenna, 121: first wireless communication unit, 122: second wireless communication unit, 130: operation reception unit, 131: touch-sensitive device, 132: display, 140: audio processing unit, 141: microphone, 142: speaker, 150: position information sensor, 160: camera, 170: memory unit, 171: user information, 172: authentication information, 173: medical record information, 181 : Input operation reception unit, 182: Transmitting and receiving unit, 183: Notification control unit, 184: Data processing unit, 201: Communication unit, 202: Memory unit, 203: Control unit, 2021: Scheduled medical treatment information management database, 2022: Patient medical information management database, 2023: Doctor information management database, 2024: Medical institution information management database, 2025: Approval history information management database, 2026: Working conditions notice information, 2027: Consent information management database, 2031: Reception control module, 2032: Transmission control module, 2033: Scheduled medical treatment information acquisition module, 2034: Patient medical information acquisition module, 2035: Doctor information acquisition module, 2036: Medical institution information acquisition module, 2037: Approval history information acquisition module, 2038: Authentication information generation module, 2039: Working conditions notice information generation module, 2040: Consent information acquisition module

Claims

1. A program for processing patient medical information stored in a medical record database of a medical institution, the program being executed by a computer having a processor and a storage unit, The storage unit stores information on the dates and times when the medical institution provides medical care to patients of the medical institution, acquiring, from a medical record database of the medical institution, first information which is medical information of a patient stored in the medical record database; presenting the first information to a first user who is a doctor who treats the patient at a timing based on the medical treatment date and time of the patient; receiving, from the first user, chart information relating to the medical treatment of the patient after the medical treatment of the patient is completed; updating the first information based on the received medical record information; storing the updated first information as second information, which is medical information of the patient that reflects the medical treatment content; A program that executes the following.

2. receiving a presentation request from the first user for requesting presentation of the first information; presenting the first information to the first user in response to the received presentation request; The program according to claim 1,

3. requesting the medical institution to approve the stored second information; receiving an approval operation from the medical institution; updating the first information stored in a medical record database of the medical institution to the approved second information in response to an approval operation from the medical institution; The program according to claim 1 or 2, which causes the program to execute the following:

4. A step of determining whether the received medical record information is appropriate; a step of sending a notification to the first user to prompt the first user to correct the medical record information when the accepted medical record information is determined to be unsuitable in the step of determining suitability; The program according to any one of claims 1 to 3, which causes the program to execute the steps of:

5. The first user is registered as a doctor available for medical treatment together with authentication information for authenticating that the first user is a user who can access the first information acquired from the medical record database. The program according to any one of claims 1 to 4.

6. accepting the authentication information from the first user; authenticating the first user by matching the received authentication information with registered authentication information; presenting the first information to the first user after authentication; The program according to claim 5, which causes the program to execute the steps of:

7. accepting the authentication information from the first user; authenticating the first user by matching the received authentication information with registered authentication information; receiving, after authentication, transmission of the medical record information from the first user; 7. The program according to claim 5 or 6, which causes the program to execute the steps of:

8. When the first user is not registered as a doctor who can provide medical treatment, providing temporary authentication information to the first user for authenticating that the first user is a user who can temporarily access the first information; presenting the first information to the first user based on the assigned temporary authentication information; The program according to any one of claims 1 to 4, which causes the program to execute the steps of:

9. When the first user is not registered as a doctor who can provide medical treatment, providing temporary authentication information to the first user for authenticating that the first user is a user who can temporarily access the first information; receiving the medical record information from the first user based on the temporary authentication information provided; The program according to any one of claims 1 to 4, which causes the program to execute the steps of:

10. In the step of acquiring the first information, the first information is periodically acquired from a medical record database of the medical institution. The program according to any one of claims 1 to 9.

11. The first user is a doctor who does not belong to the medical institution, presenting to the first user, at a timing based on the medical date and time of the patient, third information indicating working conditions for performing a medical procedure on the patient, the third information including that the first user is temporarily affiliated with the medical institution of the patient; receiving an operation of consenting to the third information from the first user; presenting the first information to the first user by accepting the consent operation; The program according to any one of claims 1 to 10, which causes the program to execute the steps of:

12. A method for processing patient medical information stored in a medical record database of a medical institution, the method being executed by a computer having a processor and a storage unit, the method comprising: The storage unit stores information on the dates and times when the medical institution provides medical care to patients of the medical institution, The processor, acquiring, from a medical record database of the medical institution, first information which is medical information of a patient stored in the medical record database; presenting the first information to a first user who is a doctor who treats the patient at a timing based on the medical treatment date and time of the patient; receiving, from the first user, chart information relating to the medical treatment of the patient after the medical treatment of the patient is completed; updating the first information based on the received medical record information; storing the updated first information as second information, which is medical information of the patient that reflects the medical treatment content; How to do it.

13. An information processing device including a control unit and a storage unit, the information processing device being configured to process medical information of a patient stored in a medical record database of a medical institution; The storage unit stores information on the dates and times when the medical institution provides medical care to patients of the medical institution, The control unit: acquiring, from a medical record database of the medical institution, first information which is medical information of a patient stored in the medical record database; presenting the first information to a first user who is a doctor who treats the patient at a timing based on the medical treatment date and time of the patient; receiving, from the first user, chart information relating to the medical treatment of the patient after the medical treatment of the patient is completed; updating the first information based on the received medical record information; storing the updated first information as second information, which is medical information of the patient that reflects the medical treatment content; An information processing device that executes the above.

Images