JP7828579B2 - Healthcare systems and medical programs - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies Publication: Precision Medicine 2020 Vol. 3 No. 9 (Volume 26) August issue p. 34-p. 38 Hokuryukan Co., Ltd. Publication date: August 25, 2020

This invention relates to a medical system and a medical program.

Conventionally, support devices that store medical information and assist medical professionals in their medical procedures (see Patent Document 1) have been known.

Japanese Patent Publication No. 2014-211828

Incidentally, there were cases where it became necessary to store information stored in electronic medical record systems in support devices that store medical information.

However, for example, the database structure of the electronic medical record system was complex, making it time-consuming to locate the information stored in the system, and potentially making it difficult to quickly store that information in the support device.

This invention was made in view of the above problems, and aims to enable the efficient storage of medical information.

To solve the above-mentioned problems and achieve the objective, the medical system described in claim 1 is a second medical information storage means for storing medical information relating to a patient, comprising: the second medical information storage means for storing the medical information in a plurality of predetermined second storage locations in the second medical information storage means; an association information storage means for storing association information relating to an information input field associated with any of the plurality of second storage locations in the second medical information storage means and an information indicating a first storage location in the first medical information storage means; and a processing means for performing a process of storing the medical information entered in the information input field in the second storage location specified by the association information corresponding to the information input field, based on the association information stored in the association information storage means.

According to the medical system described in claim 1, for example, it becomes possible to efficiently store medical information.

This is a block diagram showing the medical-related system according to this embodiment. This is a block diagram of a terminal device. This diagram illustrates a patient information table in the medical record system. This diagram illustrates an example of a medical record-side examination information table. This diagram illustrates a table of detailed prescription history information in the medical record. This diagram illustrates various tables stored as medical information for the support side. This is a diagram illustrating a patient information table. This is a diagram illustrating an episode information table. This is a diagram illustrating a treatment information table. This diagram illustrates an example of an effectiveness evaluation information table. This is a diagram illustrating an example of an adverse event information table. This is a diagram illustrating an example of an inspection information table. This diagram illustrates information related to the input screen. This diagram illustrates each input screen. This diagram illustrates information that identifies the storage location. This is a flowchart for the process of storing information that identifies the storage location. This is an example of the display screen for the storage location. This is a flowchart for the medical information storage process on the support side. This is an example of the display screen for the medical information candidate for transcription. This is an example of the display screen for the medical information candidate for transcription. This is a flowchart for the medical information storage process on the other support side.

The following describes in detail embodiments of the medical system and medical program according to the present invention, based on the drawings. However, this embodiment does not limit the present invention.

[Basic Concepts of the Embodiments]
First, let's explain the basic concepts of the embodiment. The embodiment, in general terms, relates to a medical system and a medical program.

Here, "medical system" refers to a system related to medical care, and is a concept that includes systems for supporting the work of medical professionals (e.g., doctors, nurses, CRCs (Clinical Research Coordinators), laboratory technicians, pharmacists, or medical office staff, etc.) or other persons engaged in medical practice. For example, it may include a second medical information storage means, a related information storage means, and a processing means. Furthermore, this "medical system" is a concept that includes, for example, a system configured as a dedicated medical system, or a system configured by implementing medical functions on a general-purpose system (e.g., a personal computer or server computer, etc.). Also, this "medical system" is a concept that includes systems implemented by a single computer, or systems implemented by multiple distributed computers (i.e., cloud computing).

The "second medical information storage means" is a means for storing medical information relating to a patient that is stored in a predetermined first storage location in the first medical information storage means. The "first medical information storage means" is a concept that includes databases (hereinafter, databases are also referred to as "DB") located in a different device from the device on which the second medical information storage means is installed.

The "association information storage means" is a means for storing association information. "Association information" is information that mutually associates information indicating an information input field with information indicating a first storage location in the first medical information storage means. The "information input field" is a field for inputting information, specifically an information input field associated with one of the second storage locations in the second medical information storage means, where medical information stored in the associated second storage location of the second medical information storage means is entered, and which is an information input field displayed on the display means.

"Processing means" refers to means that perform processing related to storing medical information in the second medical information storage means based on the association information stored in the association information storage means. "Processing related to storing medical information in the second medical information storage means" is a concept that includes, for example, processing to support the storage of medical information in the second medical information storage means (such as processing to display candidate medical information to be stored in the second medical information storage means), or processing to actually store medical information in the second medical information storage means.

The "processing means" performs, for example, a first process and a second process. The "first process" is a concept that includes, for example, when multiple information input fields are displayed on the display means, and at least one of the multiple information input fields is selected by the user, a process that identifies a first storage location associated with the selected at least one information input field based on the association information stored in the association information storage means. The "second process" is a concept that includes, for example, a process that displays the medical information stored in the first storage location identified in the first process. In the second process, for example, the "processing means" filters or sorts the medical information stored in the first storage location identified in the first process and displays it based on predetermined criteria.

The "processing means," for example, when medical information is newly stored in the first storage location of the first medical information storage means, identifies a second storage location associated with the first storage location based on at least the association information stored in the association information storage means, and stores the newly stored medical information in the first storage location in the identified second storage location.

Furthermore, in the embodiments described below, we will explain the case where the "processing related to storing medical information in the second medical information storage means" is processing that supports the storage of medical information in the second medical information storage means. Other concepts will be explained in the modified examples.

(composition)
First, the configuration of the medical system according to this embodiment will be described. Figure 1 is a block diagram of the medical system according to this embodiment. In reality, the number of electronic medical record information storage devices 2 in the medical system 100 is arbitrary, but we will focus on the ones shown in the diagram for this explanation.

The medical system 100 shown in Figure 1 includes, for example, a terminal device 1, an electronic medical record information storage device 2, and a medical support device 3.

(Configuration - Terminal device)
Figure 2 is a block diagram of a terminal device. The terminal device 1 in Figure 1 is a computer used by a user, and can be configured as, for example, a tablet terminal or a personal computer, but in this embodiment, the case of a tablet terminal will be described. As shown in Figure 2, the terminal device 1 includes, for example, a communication unit 11, a touchpad 12, a display 13, a recording unit 14, and a control unit 15.

(Configuration - Terminal equipment - Communication unit)
The communication unit 11 in Figure 2 is a communication means for communicating with an external device (for example, a medical support device 3), and can be configured using, for example, a known communication circuit.

(Configuration - Terminal device - Touchpad)
The touchpad 12 in Figure 2 is an operating means that receives various operation inputs from the user when pressed by the user's finger or the like. The specific configuration of this touchpad 12 is arbitrary, but for example, a known one equipped with an operation position detection means such as a resistive type or a capacitive type can be used.

(Configuration - Terminal device - Display)
The display 13 in Figure 2 is a display means that displays various images based on the control of the control unit 15. The specific configuration of this display 13 is arbitrary, but for example, a known liquid crystal display or an organic EL display or other flat panel display can be used. In addition, the touch pad 12 and the display 13 may be superimposed on each other to form an integrated touch panel.

(Configuration - Terminal device - Recording unit)
The recording unit 14 in Figure 2 is a recording means for recording programs and various data necessary for the operation of the terminal device 1, and is configured using, for example, a known recording device. This known recording device can be, for example, a flash memory.

(Configuration - Terminal device - Control unit)
The control unit 15 in Figure 1 is a control means for controlling the terminal device 1, and specifically, it is a computer configured with a CPU, various programs interpreted and executed on the CPU (including basic control programs such as an OS, and application programs launched on the OS to realize specific functions), and internal memory such as RAM for storing programs and various data (the control units of other devices are similar). In particular, the program according to this embodiment is installed on the terminal device 1 via any recording medium or network, and substantially constitutes each part of the control unit 15 (the control units of other devices are similar). The processing performed by this control unit 15 will be described later.

(Configuration - Electronic medical record information storage device)
The electronic medical record information storage device 2 shown in Figure 1 is a device that stores various medical information. For example, we will describe a case where it is configured as a so-called DWH (Data Warehouse) that stores the same information as that stored in a known electronic medical record device (not shown). The electronic medical record information storage device 2 includes, for example, a communication unit 21, a recording unit 22, and a control unit 23.

(Configuration - Electronic medical record information storage device - Communication unit)
The communication unit 21 in Figure 1 is a communication means for communicating with an external device (for example, a medical support device 3), and can be configured in the same way as the communication unit 11 of the terminal device 1.

(Configuration - Electronic medical record information storage device - Recording unit)
The recording unit 22 in Figure 1 is a recording means for recording programs and various data necessary for the operation of the electronic medical record information storage device 2, and is configured using, for example, a known recording device. As this known recording device, for example, a hard disk as an external recording device, a magnetic recording medium such as a magnetic disk, an optical recording medium such as a DVD or Blu-ray disc, an electrical recording medium such as a Flash, ROM, USB memory, or SD card, or any other arbitrary recording medium can be used (the same applies to the medical support device 3 described later).

This recording unit 22 includes, for example, a medical record-side medical information database 221.

(Configuration - Electronic medical record information storage device - Recording unit - Medical record-side medical information DB)
The medical record-side medical information DB 221 in Figure 1 is the aforementioned first medical information storage means, specifically a medical record-side medical information storage means for storing medical record-side medical information. "Medical record-side medical information" refers to medical information related to medical treatment, and in this embodiment, we will describe the case where various information related to the disease cancer is medical information. Figure 3 is an example of a medical record-side patient information table, Figure 4 is an example of a medical record-side examination information table, and Figure 5 is an example of a medical record-side prescription history details table. The "medical record-side medical information" in the medical record-side medical information DB 221 in Figure 1 includes, for example, the medical record-side patient information table T91 in Figure 3, the medical record-side examination information table T92 in Figure 4, and the medical record-side prescription history details table T93 in Figure 5. In reality, "medical record-side medical information" actually includes many tables other than those shown (for example, tens to hundreds or more), but in this embodiment, the shown tables will be described as representative. Furthermore, "table" can be interpreted as a concept that shows multiple types of information that are related to each other.

(Configuration - Electronic medical record information storage device - Recording unit - Medical record-side medical information DB - Medical record-side patient information table)
The patient information table T91 on the medical record side in Figure 3 is a table that shows information about the patient. In the patient information table T91 on the medical record side, as shown in Figure 3, for example, information corresponding to the item "Patient ID", information corresponding to the item "Patient Name", information corresponding to the item "Gender", information corresponding to the item "Date of Birth", and information corresponding to the item "Update Date" are interconnected.

The information corresponding to the "Patient ID" field is the patient ID used to uniquely identify the patient (e.g., "IDp1" in Figure 3). The information corresponding to the "Patient Name" field is the patient's name (e.g., "AA" in Figure 3). The information corresponding to the "Gender" field is the patient's gender (e.g., "Male" in Figure 3). The information corresponding to the "Date of Birth" field is the patient's date of birth (e.g., "1960/1/1" in Figure 3, indicating January 1, 1960). The information corresponding to the "Update Date" field is the date on which each of the above pieces of information was stored or updated (e.g., "2020/6/20" in Figure 3, indicating June 20, 2020).

Please note that the specific information illustrated in each table is provided for explanatory purposes only (the same applies to the specific information illustrated in each figure other than the tables).

Furthermore, in the patient information table T91 on the medical record side, for example, the information at the top (the combination of "IDp1", "AA", "Male", "1960/1/1", and "2020/6/20") indicates, for example, that the patient ID of a patient whose name is "AA" is "IDp1", that the patient's gender and date of birth are indicated by "Male" and "1960/1/1", and that the date on which each piece of information was stored or updated is indicated by "2020/6/20".

The specific storage method for the patient information table T91 on the medical record side is arbitrary. However, for example, if a medical professional or other person responsible for information input uses any method (e.g., inputting information via their own computer, or using input means of an electronic medical record device known but not illustrated (keyboard or mouse, etc.)) to input information into an electronic medical record device known but not illustrated, the electronic medical record device will record the information itself, transmit this recorded information to the electronic medical record information storage device 2, and the control unit 23 of the electronic medical record information storage device 2 will store the information based on this transmitted information (the same applies to the medical record-side examination information table T92 and the medical record-side prescription history details table T93, which will be described later).

(Configuration - Electronic medical record information storage device - Recording unit - Medical record-side medical information DB - Medical record-side examination information table)
The medical record-side examination information table T92 in Figure 4 is a table that shows information about examinations performed on a patient. In the medical record-side examination information table T92, as shown in Figure 4, for example, information corresponding to the item "Examination Result ID", information corresponding to the item "Patient ID", information corresponding to the item "Examination Code", information corresponding to the item "Examination Item Name", information corresponding to the item "Examination Value", information corresponding to the item "Examination Date", and information corresponding to the item "Update Date" are interconnected. Note that the information corresponding to the item "Patient ID" and the information corresponding to the item "Update Date" are the same as the information with the same name in Figure 3 (the same applies to the information with the same name in Figure 5, which will be described later).

The information corresponding to the item "Test Result ID" is a unique test result ID that identifies information regarding the results of tests performed on the patient (e.g., "IDct1" in Figure 4). The information corresponding to the item "Test Code" indicates various codes related to tests performed or to be performed on the patient. These codes are arbitrary; for example, JLAC10 code, analyte code, identification code, material code, measurement code, result identification code, or test item source code can be used. In Figure 4, for ease of explanation, "CODt1" is stored as the information corresponding to the item "Test Code". The information corresponding to the item "Test Item Name" indicates the name of the test item performed or to be performed on the patient (e.g., "KRAS" in Figure 4). The information corresponding to the item "Test Value" indicates the test value, which is the result of the test performed on the patient (e.g., "D1" in Figure 4). The information corresponding to the item "Test Date" indicates the date the test was performed on the patient (e.g., "2020/6/20" in Figure 4).

Furthermore, in the medical record-side examination information table T92, for example, the information at the top (the combination of "IDct1", "IDp1", "CODt1", "KRAS", "D1", "2020/6/20", and "2020/6/20") indicates that, for example, the code, name of the examination item, examination value, and examination date related to the examination performed on the patient identified by "IDp1" are the dates indicated by "CODt1", "KRAS", "D1", and "2020/6/20". It also indicates that the examination result ID is "IDct1", and that the date each piece of information was stored or updated is the date indicated by "2020/6/20".

(Configuration - Electronic medical record information storage device - Recording unit - Medical record-side medical information DB - Medical record-side prescription history detailed information table)
The medical record prescription history details table T93 in Figure 5 is a table that shows information about medications prescribed to a patient for treatment. In the medical record prescription history details table T93, as shown in Figure 5, for example, information corresponding to the item "Prescription History ID", information corresponding to the item "Patient ID", information corresponding to the item "Medication Code", information corresponding to the item "Medication Name", information corresponding to the item "Dosage", information corresponding to the item "Unit", information corresponding to the item "Number of Days", information corresponding to the item "Prescription Date", and information corresponding to the item "Update Date" are all interconnected.

The information corresponding to the item "Prescription History ID" is a prescription history ID used to uniquely identify information about medications prescribed to a patient for treatment (e.g., "IDcp1" in Figure 5). The information corresponding to the item "Medication Code" is information indicating various codes related to the medication. Note that the various codes here are arbitrary, and HOT codes or drug source codes can be used. In Figure 5, for the sake of explanation, "CODm1" is stored as the information corresponding to the item "Medication Code". The information corresponding to the item "Medication Name" is information indicating the name of the medication used to treat the patient's illness (e.g., "A1 medication" in Figure 5). The information corresponding to the item "Dosage" is information indicating the dosage of the medication (e.g., "28" indicating 28 tablets in Figure 5). The information corresponding to the item "Unit" is information indicating the amount of medication to be administered orally at one time (e.g., "1" indicating 1 tablet in Figure 5). The information corresponding to the item "Days" is information indicating the number of days for which the prescribed medication should be administered (e.g., "14" indicating 14 days in Figure 5). The information corresponding to the "Prescription Date" field indicates the date the medication was prescribed to the patient (e.g., "2020/7/1" in Figure 5).

Furthermore, in the medical record prescription history details table T93, for example, the information at the top (the combination of "IDcp1", "IDp1", "CODm1", "A1 drug", "28", "1", "14", "2020/7/1", and "2020/7/1") indicates that, for example, the code, drug name, dosage, unit, duration, and prescription date for the drug prescribed for treatment to the patient identified by "IDp1" are the date indicated by "CODm1", "A1 drug", "28", "1", "14", and "2020/7/1". It also indicates that the prescription history ID is "IDcp1", and that the date each piece of information was stored or updated is the date indicated by "2020/7/1".

Furthermore, for example, each table and each item within each table in Figures 3 to 5 above may be interpreted as corresponding to the predetermined "first storage location" of the medical information in the medical record-side medical information DB 221.

(Configuration - Electronic medical record information storage device - Control unit)
The control unit 23 in Figure 1 is a control means for controlling the electronic medical record information storage device 2. The processing performed by this control unit 23 will be described later.

(Configuration - Medical support device)
The medical support device 3 in Figure 1 is the aforementioned medical system, and includes, for example, a communication unit 31, a recording unit 32, and a control unit 33.

(Configuration - Medical support device - Communications unit)
The communication unit 31 in Figure 1 is a communication means for communicating with external devices (for example, terminal device 1 and electronic medical record information storage device 2), and can be configured in the same way as the communication unit 11 of terminal device 1.

(Configuration - Medical support device - Recording unit)
The recording unit 32 in Figure 1 is a recording means for recording programs and various data necessary for the operation of the medical support device 3, and is configured, for example, using a known recording device.

This recording unit 32 includes, for example, a support-side medical information DB 321, an input screen-related information DB 322, and a storage location identification information DB 323.

(Configuration - Medical support device - Recording unit - Support-side medical information database)
The support-side medical information DB 321 in Figure 1 is the second medical information storage means described above, and specifically, it is a support-side medical information storage means for storing support-side medical information. "Support-side medical information" refers to medical information related to medical care, and in this embodiment, we will explain the case where various information related to the disease cancer is medical information. Figure 6 is a diagram illustrating various tables stored as support-side medical information. The support-side medical information DB 321 in Figure 1 stores, for example, a patient information table T1, an episode information table T2, a treatment information table T3, an effectiveness evaluation information table T4, a side effect information table T5, and an examination information table T6 as support-side medical information, as shown in Figure 6.

(Configuration - Medical support device - Recording unit - Support-side medical information database - Patient information table)
The patient information table T1 in Figure 6 is a table that shows information about a patient. Figure 7 is an example of a patient information table. In the patient information table T1, as shown in Figure 7, for example, the same information as in the medical record-side patient information table T91 in Figure 3 is interconnected.

The specific storage method for this patient information table T1 is arbitrary. For example, when each piece of information in the medical record-side patient information table T91 is stored in the electronic medical record information storage device 2, communication may be performed between the medical support device 3 and the electronic medical record information storage device 2 to store the same information as in the medical record-side patient information table T91. Alternatively, when a user (medical professional, etc.) inputs the same information as in the medical record-side patient information table T91 into the medical support device 3 using any method (for example, inputting information via their own terminal device 1, or using the input means of the medical support device 3 (keyboard or mouse, etc.)), the control unit 33 of the medical support device 3 may store the information based on the input. The specific storage methods for the other tables will be described later.

(Configuration - Medical support device - Recording unit - Support-side medical information DB - Episode information table)
The episode information table T2 in Figure 6 is a table that shows information about the patient's disease status (cancer in this embodiment). Figure 8 is an example of the episode information table. In the episode information table T2, as shown in Figure 8, for example, information corresponding to the item "Episode ID", information corresponding to the item "Patient ID", information corresponding to the item "Cancer Type Classification", information corresponding to the item "Cancer Tissue", information corresponding to the item "Cancer Differentiation Level", information corresponding to the item "Cancer Site", information corresponding to the item "TNM Classification", information corresponding to the item "Stage", and information corresponding to the item "Update Date" are all interconnected. Note that the information corresponding to the item "Patient ID" and the information corresponding to the item "Update Date" are the same as the information with the same name in Figure 7.

The information corresponding to the item "Episode ID" is an episode ID that uniquely identifies the episode (e.g., "IDse1" in Figure 8). This information corresponding to "Episode ID" is used to identify the progression of disease treatment. In this embodiment, it is used to identify the progression of treatment for cancer, a disease whose condition can change over time through progression or recovery. For example, it is also information that uniquely identifies the state of cancer. In other words, in this embodiment, "Episode" may be interpreted as corresponding to "Cancer State."

The information corresponding to the item "Cancer Type Classification" indicates the classification of cancer types (in Figure 8, the classification is based on the site where the cancer is located, such as "Gastric Cancer" and, although not shown, "Lung Cancer," etc.). The information corresponding to the item "Cancer Tissue" indicates the histological type of cancer (in Figure 8, such as "Tubular Adenocarcinoma," etc.). The information corresponding to the item "Cancer Differentiation Level" indicates the degree of differentiation of the cancer (in Figure 8, such as "Poorly Differentiated Type," etc.). The information corresponding to the item "Cancer Site" indicates the site where the cancer is located (in Figure 8, such as "Stomach/Cardia," etc.). The information corresponding to the item "TNM classification" is information indicating indicators related to cancer for determining the degree of cancer progression. This information can be determined according to arbitrary criteria, including, for example, the UICC (Unio Internationalis Contra Cancrum) criteria or other criteria. For example, it includes information on cancer size and invasion as the T factor, information on lymph node metastasis as the N factor, and information on distant metastasis as the M factor (in Figure 8, for gastric cancer, it specifies that the T factor is "1", the N factor is "1", and the M factor is "0" as "T=1, N=1, M=0"). The information corresponding to the item "stage" indicates the stage of cancer progression. This information can be determined according to arbitrary criteria, including, for example, the UICC criteria or other criteria (in Figure 8, it indicates stage 1A as "1A").

Furthermore, in such episode information table T3, for example, the information at the top (the combination of "IDse1", "IDp1", "gastric cancer", "tubular adenocarcinoma", "poorly differentiated", "stomach/cardia", "T=1, N=1, M=0", "1A", and "2020/7/1") indicates that, for example, the cancer type, cancer tissue, cancer differentiation level, location of the cancer, TNM classification, and stage identified by "IDp1" are "gastric cancer", "tubular adenocarcinoma", "poorly differentiated", "stomach/cardia", "T=1, N=1, M=0", and "1A". It also indicates that the episode ID is "IDse1", and that the date each piece of information was stored or updated is the date indicated by "2020/7/1".

Furthermore, since the episode information table T2 contains information corresponding to the "Patient ID" item, it becomes possible to associate multiple episode information tables T2 with a single patient's patient information table T1, as shown in Figure 6.

(Configuration - Medical support device - Recording unit - Support-side medical information DB - Treatment information table)
The treatment information table T3 in Figure 6 is a table that shows information about the treatment of a patient's illness. Figure 9 is an example of a treatment information table. In the treatment information table T3, as shown in Figure 9, for example, the information corresponding to the item "treatment information ID", the information corresponding to the item "episode ID", the information corresponding to the item "patient ID", the information corresponding to the item "drug name", the information corresponding to the item "prescription date", and the information corresponding to the item "update date" are interrelated. Note that the information corresponding to the item "episode ID", the information corresponding to the item "patient ID", and the information corresponding to the item "update date" are the same as the information with the same name in Figure 8 (the same applies to the information with the same name in Figure 12, which will be described later).

The information corresponding to the "Treatment Information ID" field is a treatment information ID used to uniquely identify information related to the treatment of the patient's illness (e.g., "IDsm1" in Figure 9). The information corresponding to the "Drug Name" field indicates the name of the drug used to treat the patient's illness (e.g., "A1 Drug" in Figure 9). The information corresponding to the "Prescription Date" field indicates the date the drug was prescribed to the patient (e.g., "2020/7/1" in Figure 9).

Furthermore, in such treatment information table T4, for example, the information at the top (the combination of "IDsm1", "IDse1", "IDp1", "A1 drug", "2020/7/1", and "2020/7/1") indicates that, for example, the patient identified by "IDse1" (the patient identified by "IDp1") was prescribed "A1 drug" on the date indicated by "2020/7/1", the treatment information ID is "IDsm1", and the date each piece of information was stored or updated is indicated by the date indicated by "2020/7/1".

Furthermore, since the treatment information table T3 contains information corresponding to the "Episode ID" and "Patient ID" fields, as shown in Figure 6, it is possible to associate multiple treatment information tables T3 with the episode information table T2, which represents one episode for one patient (the same applies to the examination information table T6 described later).

(Configuration - Medical support device - Recording unit - Support-side medical information DB - Effectiveness evaluation information table)
The effectiveness evaluation information table T4 in Figure 6 is a table that shows information about the effectiveness of treatments given to patients. Figure 10 is an example of the effectiveness evaluation information table. In the effectiveness evaluation information table T4, as shown in Figure 10, for example, the information corresponding to the item "Effectiveness Evaluation Information ID", the information corresponding to the item "Episode ID", the information corresponding to the item "Patient ID", the information corresponding to the item "Treatment Information ID", the information corresponding to the item "Effectiveness Evaluation Result", the information corresponding to the item "Effectiveness Evaluation Date", and the information corresponding to the item "Update Date" are interrelated. Note that the information corresponding to the item "Episode ID", the information corresponding to the item "Patient ID", the information corresponding to the item "Treatment Information ID", and the information corresponding to the item "Update Date" are the same as the information with the same name in Figure 9 (the same applies to the information with the same name in Figure 11, which will be described later).

The information corresponding to the item "Effect Assessment Information ID" is an effect assessment information ID that uniquely identifies information regarding the effectiveness of the treatment given to the patient (e.g., "IDsj1" in Figure 10). The information corresponding to the item "Effect Assessment Result" indicates the assessment result regarding the effectiveness of the treatment given to the patient (e.g., "Progression" in Figure 10, indicating a relatively small effect and cancer progression, and "Success" in indicating a relatively large effect and cessation of cancer progression or reduction in cancer size). The information corresponding to the item "Effect Assessment Date" indicates the date on which the assessment of the treatment given to the patient was made (e.g., "2020/8/15" in Figure 9).

Furthermore, in such an effectiveness evaluation information table T5, for example, the information at the top (the combination of "IDsj1", "IDse1", "IDp1", "IDsm1", "Progression", "2020/8/15", and "2020/8/15") indicates that, for example, the effect judged for the treatment indicated by "IDsm1" performed on the patient identified by "IDse1" (the patient identified by "IDp1") is "Progression". It also indicates that the date this judgment was made is the date indicated by "2020/8/15", the effectiveness evaluation information ID is "IDsj1", and the date each piece of information was stored or updated is the date indicated by "2020/8/15".

Furthermore, since the efficacy evaluation information table T4 contains information corresponding to the items "Episode ID," "Patient ID," and "Treatment Information ID," as shown in Figure 6, it is possible to associate multiple efficacy evaluation information tables T4 with the treatment information table T3 for a single patient and one episode of treatment (the same applies to the side effect information table T5, which will be discussed later).

(Configuration - Medical support device - Recording unit - Support-side medical information DB - Side effect information table)
The adverse event information table T5 in Figure 6 is a table that shows information about adverse events of treatments given to a patient. Figure 11 is an example of an adverse event information table. In the adverse event information table T5, as shown in Figure 11, for example, information corresponding to the item "Adverse Event Information ID", information corresponding to the item "Episode ID", information corresponding to the item "Patient ID", information corresponding to the item "Treatment Information ID", information corresponding to the item "Adverse Event Name", information corresponding to the item "Grade", information corresponding to the item "Date of Adverse Event Onset", information corresponding to the item "Date of Adverse Event Resolution", and information corresponding to the item "Update Date" are all interconnected.

The information corresponding to the item "Adverse Event Information ID" is an adverse event information ID that uniquely identifies information regarding adverse events of the treatment administered to the patient (e.g., "IDss1" in Figure 11). The information corresponding to the item "Adverse Event Name" indicates the name of the adverse event that occurred (e.g., "Vomiting" in Figure 11). The information corresponding to the item "Grade" indicates the severity of the adverse event that occurred (in Figure 11, the severity of adverse events is divided into a predetermined number of stages, and the stage to which it falls is indicated numerically, e.g., "2"). The information corresponding to the item "Adverse Event Onset Date" indicates the date the adverse event occurred (e.g., "2020/7/12" in Figure 11). The information corresponding to the item "Adverse Event Resolution Date" indicates the date the adverse event resolved (e.g., "2020/7/15" in Figure 11).

Furthermore, in such adverse event information table T6, for example, the information at the top (the combination of "IDss1", "IDse1", "IDp1", "IDsm1", "vomiting", "2", "2020/7/12", "2020/7/15", and "2020/7/20") indicates that, for example, the adverse event name, grade, date of onset, and date of resolution for the treatment indicated by "IDsm1" performed on the patient identified by "IDse1" (the patient identified by "IDp1") corresponds to the dates indicated by "vomiting", "2", "2020/7/12", and "2020/7/15". It also indicates that the adverse event information ID is "IDss1", and that the date each piece of information was stored or updated is the date indicated by "2020/7/20".

(Configuration - Medical support device - Recording unit - Support-side medical information DB - Examination information table)
The examination information table T6 in Figure 6 is a table that shows information about examinations performed on a patient. Figure 12 is an example of an examination information table. In the examination information table T6, as shown in Figure 12, for example, information corresponding to the item "Examination Information ID", information corresponding to the item "Episode ID", information corresponding to the item "Patient ID", information corresponding to the item "Examination Item Name", information corresponding to the item "Examination Value", information corresponding to the item "Examination Date", and information corresponding to the item "Update Date" are interconnected.

The information corresponding to the item "Test Information ID" is a unique test information ID that identifies information about the test performed on the patient (e.g., "IDst1" in Figure 12). The information corresponding to the item "Test Item Name" indicates the name of the test item performed or to be performed on the patient (e.g., "KRAS" in Figure 12). The information corresponding to the item "Test Value" indicates the test value, which is the result of the test performed on the patient (e.g., "D1" in Figure 12). The information corresponding to the item "Test Date" indicates the date the test was performed on the patient (e.g., "2020/6/20" in Figure 11).

Furthermore, in such a test information table T6, for example, the information at the top (the combination of "IDst1", "IDse1", "IDp1", "KRAS", "D1", "2020/6/20", and "2020/6/20") indicates that, for example, the name of the test item, the test value, and the test date performed on the patient identified by "IDse1" (the patient identified by "IDp1") are the same as the date indicated by "KRAS", "D1", and "2020/6/20". It also indicates that the test information ID is "IDst1", and that the date each piece of information was stored or updated is the date indicated by "2020/6/20".

Furthermore, for example, each table in Figures 7 to 12 and each item within each table may be interpreted as corresponding to a predetermined "second storage location" for medical information in the support-side medical information DB 321.

(Configuration - Medical support device - Recording unit - Input screen related information DB)
The input screen-related information DB322 in Figure 1 is an input screen-related information storage means for storing input screen-related information. "Input screen-related information" refers to information related to various input screens for users to input medical information into the medical support device 3. Figure 13 is an example of input screen-related information, and Figure 14 is an example of each input screen. In Figure 14, elements other than the characteristic parts of the present invention have been appropriately omitted from each input screen.

===Input Screen===
First, let's explain the input screen. The "input screen" is a screen for storing medical information in the support-side medical information DB 321, and is a screen displayed on the display 13 of the terminal device 1 based on input screen information (information for displaying the input screen) generated on the medical support device 3. The "input screen" includes, for example, a patient information input screen, an episode information input screen, a treatment information input screen, an effectiveness evaluation information input screen, a side effect information input screen, and an examination information input screen, as shown in Figure 14. Note that each of these input screens may be configured so that each screen can be switched by performing a predetermined operation on the terminal device 1 side, by applying any technology (for example, a technology that switches screens using tabs).

=Patient Information Input Screen=
The "Patient Information Input Screen" is a screen for inputting information from the patient information table T1 in Figure 7, and displays input fields P11 to P12, for example. Each input field is a field for inputting and storing information corresponding to the name of the information displayed to the left of each input field on the input screen (that is, information corresponding to each item in each table in Figures 7 to 12), and it is also possible to display each piece of information as appropriate (the same applies to input fields on other screens). Input fields P11 to P12, for example, are fields for inputting information corresponding to the items "Patient Name" and "Gender" in Figure 7, and are fields to which "ID11" to "ID12," for example, are associated as input field IDs to uniquely identify each field.

=Episode Information Input Screen=
The "Episode Information Input Screen" is a screen for inputting information from the Episode Information Table T2 in Figure 8, and displays input fields such as P21 to P22. Input fields P21 to P22 are fields for inputting information corresponding to the items "Cancer Type Classification" and "Cancer Tissue" in Figure 8, and are fields to which input field IDs such as "ID21" to "ID22" are associated to uniquely identify each field.

=Treatment Information Input Screen=
The "treatment information input screen" is a screen for inputting information from the treatment information table T3 in Figure 9, and is the screen that displays input fields P31 to P32. Input fields P31 to P32 are fields for inputting information corresponding to the items "drug name" and "prescription date" in Figure 9, and are fields to which "ID31" to "ID32" are associated as input field IDs to uniquely identify each field.

=Effect Evaluation Information Input Screen=
The "Effect Evaluation Information Input Screen" is a screen for inputting information from the effect evaluation information table T4 in Figure 10, and displays input fields such as P41 to P42. Input fields P41 to P42 are fields for inputting information such as the items "Effect Evaluation Result" and "Effect Evaluation Date" in Figure 10, and are fields to which "ID41" to "ID42" are associated as input field IDs to uniquely identify each field.

=Side effect information input screen=
The "adverse event information input screen" is a screen for inputting information from the adverse event information table T5 in Figure 11, and displays input fields such as P51 to P52. Input fields P51 to P52 are fields for inputting information such as the "adverse event name" and "grade" items in Figure 11, and are fields to which input field IDs such as "ID51" to "ID52" are associated to uniquely identify each field.

=Inspection Information Input Screen=
The "examination information input screen" is a screen for inputting information from the examination information table T6 in Figure 12. In this embodiment, candidate examination items such as "KRAS" and "NRAS" are predetermined for the patient, and the explanation will be based on an example of when an examination is performed on any of these candidate examination items. The "examination information input screen" in Figure 14 is a screen that displays input fields such as P61 to P64. Input fields P61 to P62 are fields for inputting information corresponding to the item "examination value" and the item "examination date" associated with the item "examination item name" = "KRAS" in Figure 12. For example, these fields are associated with input field IDs "ID61" to "ID62". Input fields P63 to P64 are for entering information corresponding to the item "Test Value" and the item "Test Date" associated with the item "Test Item Name" = "NRAS" in Figure 12. For example, these fields are associated with input field IDs "ID63" to "ID64".

===Input Screen Related Information===
Next, we will explain the information related to the input screen. In the input screen related information in Figure 13, for example, the information corresponding to the item "Input Screen", the information corresponding to the item "Input Field ID", the information corresponding to the item "Table" of the item "Medical Information", and the information corresponding to the item "Information" of the item "Medical Information" are all interconnected.

The information corresponding to the item "Input Screen" is the information indicating each of the aforementioned input screens (in Figure 13, "Patient Information," etc., indicating the patient information input screen). The information corresponding to the item "Input Field ID" is the input field ID mentioned above. The information corresponding to the item "Table" in the item "Medical Information" is the information indicating each of the tables shown in Figures 7 to 12. Any information can be used as the information indicating each table, but for example, we will explain the case where table name information indicating the table name is used. In Figure 13, the information corresponding to the item "Table" in the item "Medical Information" is exemplified by the table name information of the patient information table T1 in Figure 7, "Patient Information," etc.

The information corresponding to the item "Information" is information that indicates the specific type of information contained in each table (i.e., information that indicates each item contained in each table). Any information can be used as the information that indicates each item, but for example, the case in which item name information indicating the name of the item is used will be explained. In Figure 13, as an example of the information corresponding to the item "Information" of the item "Medical Information", "Patient Name", which is the item name information of the item "Patient Name" in Figure 7, is shown. Note that the item "Information" = "Laboratory Value (KRAS)" in Figure 13 is assumed to indicate the item "Laboratory Value" associated with the item "Laboratory Item Name" = "KRAS" in Figure 12 (i.e., the item name information "Laboratory Value" associated with the item "Laboratory Item Name" = "KRAS" in Figure 12), and similarly, the item "Information" = "Laboratory Date (KRAS)" in Figure 13 is assumed to indicate the item "Laboratory Date" associated with the item "Laboratory Item Name" = "KRAS" in Figure 12. Similarly, the items "Information" = "Test Value (NRAS)" and "Test Date (NRAS)" in Figure 13 also represent the items "Test Value" and "Test Date" associated with the item "Test Item Name" = "NRAS" in Figure 12.

Furthermore, regarding the information related to such input screens, for example, the top-level information (the combination of "Patient Information," "ID 11," "Patient Information," and "Patient Name"), it is shown that, for example, the patient information input screen indicated by "Patient Information" (Figure 14) displays the input field P11 (Figure 14) identified by "ID 11," and that this input field P11 identified by "ID 11" is associated with the item "Patient Name" in Figure 7, indicated by "Patient Name," in the patient information table T1 (Figure 7) indicated by "Patient Information." Note that for the sake of clarity, some input field IDs in Figure 13 are represented as "..." and specific information is omitted.

While the specific method for storing such input screen-related information is arbitrary, for example, if information related to the input screen is input to the medical support device 3 using any method (for example, by an administrator accessing the medical support device 3 using their own terminal device, or by inputting it using an input means (keyboard or mouse, etc.) of the medical support device 3 not shown), the control unit 33 may store the information based on that input.

(Configuration - Medical support device - Recording unit - Storage location identification information DB)
The storage location identification information DB 323 in Figure 1 is the aforementioned association information storage means, and more specifically, it is a storage location identification information storage means for storing storage location identification information. "Storage location identification information" is the aforementioned association information, and more specifically, it is information in which information indicating at least one or more input fields in each input screen and information indicating a predetermined storage location (i.e., the first storage location) of medical information in the medical record side medical information DB 221 are mutually associated. Figure 15 is a diagram illustrating storage location identification information. In the storage location identification information of Figure 15, for example, information corresponding to the item "input field ID" and information corresponding to the item "medical record side storage location information" are mutually associated. Note that the information corresponding to the item "input field ID" is the same as the information with the same name in Figure 13.

The information corresponding to the item "Medical Record Storage Location Information" is information indicating the predetermined storage location of medical information in the medical record side medical information DB221. Note that any information can be used for this item "Medical Record Storage Location Information," for example, so-called schema information can be used. In this embodiment, an example is given of using information similar to that shown in the "Table" and "Information" items of the "Medical Information" item in Figure 13. Specifically, the information for the item "Medical Record Storage Location Information" will be described in the following example: a combination of information indicating each table in the medical record side medical information DB221 shown in Figures 3 to 5 (for example, table name information indicating the name of the table) and information indicating the specific type of information contained in each table (i.e., information indicating each item contained in each table (for example, item name information indicating the name of the item)). Figure 15 illustrates the combination of "Medical Record Prescription Details - Drug Name," which is the table name information for the medical record prescription details table T93 in Figure 5, and the item name information for the "Drug Name" field in that table, "Drug Name." Figure 15 also illustrates the combination of "Medical Record Laboratory Information - Laboratory Value (KRAS)," which is the table name information for the medical record laboratory information table T92 in Figure 4, and the item name information for the "Laboratory Value (KRAS)," which is the item name information for the "Laboratory Value" field associated with the "Laboratory Item Name" = "KRAS" field in that table, "Medical Record Laboratory Information - Laboratory Value (KRAS)."

Furthermore, regarding the top-level information in this storage location identification information (for example, the combination of "ID 31" and "Medical Record Prescription History Details - Drug Name"), it is shown that, for example, the input field P31 identified by "ID 11" (Figure 14) and the storage location indicated by "Medical Record Prescription History Details - Drug Name" (i.e., the "Drug Name" item in the Medical Record Prescription History Details Table T93 in Figure 5) are mutually associated. While the specific method for storing such storage location identification information is arbitrary, it can be stored, for example, by executing the storage location identification information storage process described later.

(Configuration - Medical support device - Control unit)
The control unit 33 in Figure 1 is a control means for controlling the medical support device 3, and functionally, it includes, for example, a processing unit 331. The processing unit 331 is a processing means that performs processing related to storing medical information in the support-side medical information DB 321 based on the storage location identification information stored in the storage location identification information DB 323. The processing performed by each part of this control unit 33 will be described later.

(process)
Next, we will describe the storage location identification information storage process and the support-side medical information storage process performed by the medical-related system 100 configured in this manner.

Here, we will explain using an example where, as mentioned above, the patient information table T1 already contains the information illustrated in Figure 7.

(Processing - Storage location identification information storage process)
First, let's explain the storage location identification information storage process. Figure 16 is a flowchart of the storage location identification information storage process (in the following explanations of each process, steps will be abbreviated as "S"). The "storage location identification information storage process" is, in general terms, a process performed by the medical support device 3, and specifically, it is a process for storing storage location identification information.

The timing of executing this storage location identification information storage process is arbitrary, but for example, it will be initiated when the user performs a predetermined operation (an operation to start the storage location identification information storage process) via the touchpad 12 of their terminal device 1 at any time, such as during initial setup. The explanation will begin from the point where the process is initiated.

===SA1===
In SA1 of Figure 16, the processing unit 331 of the medical support device 3 displays each input screen. Specifically, although it is arbitrary, for example, it generates input screen information for displaying an input screen and transmits the generated input screen information to the terminal device 1, thereby displaying each input screen on the display 13 of the terminal device 1. More specifically, referring to the input screen related information in Figure 13, it generates input screen information for displaying an input screen that is indicated by the information of the item "Input Screen" and includes an input field identified by the information of the item "Input Field ID" associated with the information of the item "Input Screen", and transmits it to the terminal device 1. On the other hand, the control unit 15 of the terminal device 1 receives the input screen information transmitted from the medical support device 3 and displays the input screen on the display 13 based on the received input screen information.

Here, for example, by referring to the input screen-related information in Figure 13, input screen information is generated for displaying each input screen in Figure 14, such as the patient information input screen indicated by the item "Input Screen" = "Patient Information" (the patient information input screen including input fields P11 and P12, etc., identified by the item "Input Field ID" = "ID11" and "ID12," etc.), and transmitted to the terminal device 1. Meanwhile, the control unit 15 of the terminal device 1 receives the input screen information transmitted from the medical support device 3 and displays each input screen in Figure 14 on the display 13 based on the received input screen information.

===SA2===
In SA2 of Figure 16, the processing unit 331 of the medical support device 3 acquires table name information and item name information related to the medical record-side medical information DB 221 of the electronic medical record information storage device 2. Specifically, although arbitrary, for example, the processing unit 331 of the medical support device 3 transmits a table name request signal (a signal to request table name information and item name information) to the electronic medical record information storage device 2. On the other hand, when the control unit 23 of the electronic medical record information storage device 2 receives the table name request signal, it acquires the table name information of the tables stored in its own medical record-side medical information DB 221 and item name information indicating the items contained in those tables, and transmits the acquired table name information and item name information to the medical support device 3. For example, it is decided to transmit table name information and item name information for all tables contained in the medical record-side medical information DB 221, and transmit the information in an arbitrary format that makes it possible to understand which items are contained in each table so that the data structure of each table can be grasped. Meanwhile, the processing unit 331 of the medical support device 3 receives and acquires table name information and item name information transmitted from the electronic medical record information storage device 2.

Here, for example, when the processing unit 331 of the medical support device 3 transmits a table name request signal, the control unit 23 of the electronic medical record information storage device 2 receives the table name request signal and then acquires and transmits table name information and item name information for each table and the items contained in each table shown in Figures 3 to 5.

As an example, regarding the medical record prescription history details table T93 in Figure 5, the "table name information" = "medical record prescription history details" and the "item name information" = "prescription history ID", "patient ID", "drug code", "drug name", "dosage", "unit", "days", "prescription date", and "update date" are retrieved, and this retrieved information is transmitted. The same procedure applies to the medical record patient information table T91 in Figure 3.

Furthermore, regarding the medical record-side examination information table T92 in Figure 4, the "table name information" = "medical record-side examination information" is obtained, and for the item name information, the items "examination code," "examination item name," "examination value," "examination date," and "update date" in Figure 4 are obtained as information associated with the item "examination item name" (i.e., "KRAS" and "NRAS," etc.). Note that the item "examination item name" itself is associated with other items as specific information as described above, so it is not obtained here. Specifically, regarding the medical record-side examination information table T92 in Figure 4, the following information is obtained: "Table name information" = "Medical record-side examination information" (as described above), and "Item name information" = "Examination result ID", "Patient ID", "Examination code (KRAS)", "Examination code (NRAS)", ..., "Examination value (KRAS)", "Examination value (NRAS)", ..., "Examination date (KRAS)", "Examination date (NRAS)", ..., and "Update date (KRAS)", "Update date (NRAS)", etc. This obtained information is then transmitted. Note that "Examination value (KRAS)" here refers to the item "Examination value" associated with the item "Examination item name" = "KRAS" in Figure 4, as explained in Figure 15. The same applies to other items such as "Examination value (NRAS)". Meanwhile, the processing unit 331 of the medical support device 3 receives and obtains this transmitted table name information and item name information.

===SA3===
In SA3 of Figure 16, the processing unit 331 of the medical support device 3 displays a storage location display screen. Figure 17 shows an example of the storage location display screen. The "storage location display screen" is a screen for displaying table name information and item name information acquired in SA2. For example, it is a screen for displaying the information in a table format, and as shown in Figure 17, it includes a table name information display area R1 (the uppermost area in the table) which is the area for displaying table name information, and an item name information display area R2 (the area from the second row onwards in the table) which is the area for displaying item name information. The processing of SA3 is specific and arbitrary, but for example, screen information for displaying the storage location display screen that displays the table name information and item name information acquired in SA2 is generated, and the generated screen information is transmitted to the terminal device 1, thereby displaying the storage location display screen on the display 13 of the terminal device 1.

Here, for example, based on the table name information and item name information related to each table and the items contained in each table, acquired by SA2, screen information for displaying the storage location display screen in Figure 17 is generated and transmitted, thereby displaying the storage location display screen in Figure 17 on the display 13 of the terminal device 1.

===SA4===
In SA4 of Figure 16, the processing unit 331 of the medical support device 3 acquires information on the combination of mutually related input field IDs, table name information, and item name information. Specifically, although arbitrary, for example, each item in each table of the support-side medical information DB 321 (Figures 7 to 12) contains items (hereinafter referred to as "transfer items") that should be transferred and stored with the same information as each item in each table of the medical record-side medical information DB 221 (Figures 3 to 5) (in this embodiment, for example, "drug name" and "prescription date" in the treatment information table T3 in Figure 9, and the items "test value" and "test date" in the test information table T6 in Figure 12). The processing unit 331 acquires information on the combination of an input field ID that identifies the input field for inputting information for these items, and table name information and item name information that indicate the table and items of the information to be transferred on the medical record-side medical information DB 221.

In detail, when a user taps and selects an input field for entering "transfer item" information on each input screen displayed in SA1 via the touchpad 12, and also taps and selects table name information and item name information indicating the table and item where the information to be transferred to each item in each table of the support-side medical information DB 321 corresponding to the selected input field is stored, on the storage location display screen displayed in SA3, via the touchpad 12, the control unit 15 of the terminal device 1 transmits information combining the input field ID of the selected input field and the selected table name information and item name information to the medical support device 3, and the processing unit 331 of the medical support device 3 receives and acquires the transmitted information combining the input field ID and the table name information and item name information.

Here, for example, if a user taps and selects input field P31 in Figure 14, and then taps and selects "Medical Record Prescription History Details" and "Drug Name" in Figure 17, the control unit 15 of the terminal device 1 transmits information combining the selected input field ID = ID31 of the input field P31 and the selected table name information = "Medical Record Prescription History Details" and item name information = "Drug Name" to the medical support device 3. The processing unit 331 of the medical support device 3 receives and acquires the transmitted information combining the input field ID = ID31 and the table name information = "Medical Record Prescription History Details" and item name information = "Drug Name". Furthermore, if, after tapping and selecting input field P32 in Figure 14, the user then taps and selects "Medical Record Prescription History Details" and "Prescription Date" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information combining "Input Field ID" = "ID32," "Table Name Information" = "Medical Record Prescription History Details," and "Item Name Information" = "Prescription Date."

Furthermore, if, after tapping and selecting input field P61 in Figure 14, the user then taps and selects "Medical Record-Side Examination Information" and "Examination Value (KRAS)" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information combining "Input Field ID" = "ID61", "Table Name Information" = "Medical Record-Side Examination Information", and "Item Name Information" = "Examination Value (KRAS)". Furthermore, if, after tapping and selecting input field P62 in Figure 14, the user then taps and selects "Medical Record-Side Examination Information" and "Examination Date (KRAS)" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information combining "ID62", "Medical Record-Side Examination Information", and "Examination Date (KRAS)". Furthermore, if, after tapping and selecting input field P63 in Figure 14, the user then taps and selects "Medical Record-Side Examination Information" and "Examination Value (NRAS)" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information combining "ID63" and "Medical Record-Side Examination Information" and "Examination Value (NRAS)". Similarly, if, after tapping and selecting input field P64 in Figure 14, the user then taps and selects "Medical Record-Side Examination Information" and "Examination Date (NRAS)" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information combining "ID64" and "Medical Record-Side Examination Information" and "Examination Date (NRAS)".

===SA5===
In SA5 of Figure 16, the processing unit 331 of the medical support device 3 stores storage location identification information. Specifically, although it is arbitrary, for example, in the storage location identification information of Figure 15, the input field ID from the combination information acquired in SA4 is stored as information for the item "Input ID", and the table name information and item name information from the said combination information are stored as information for the item "Medical record side storage location information".

Here, for example, based on the "Input Field ID" = "ID31", "Table Name Information" = "Medical Record Prescription History Details", and "Item Name Information" = "Drug Name" obtained in SA4, the information at the top of Figure 15 (i.e., the item "Input Field ID" = "ID31" and the item "Medical Record Storage Location Information" = "Medical Record Prescription History Details - Drug Name") is stored. Similarly, other information specifically illustrated in Figure 15 is stored based on other combinations of information obtained in SA4. This concludes the explanation of the storage location identification information storage process.

(Processing - Support-side medical information storage processing)
Next, we will explain the support-side medical information storage process. Figure 18 is a flowchart of the support-side medical information storage process. The "support-side medical information storage process" is, in general terms, a process performed by the electronic medical record information storage device 2 and the medical support device 3, and specifically, it is a process for storing support-side medical information.

The timing of executing this support-side medical information storage process is arbitrary. However, for example, when a user enters the name of the patient whose information is to be stored via the touchpad 12 of their terminal device 1 and performs a predetermined operation (an operation to activate the support-side medical information storage process), the control unit 15 of the terminal device 1 transmits patient name information indicating the entered patient name to the medical support device 3. When the control unit 33 of the medical support device 3 receives the patient name information transmitted from the terminal device 1, the support-side medical information storage process is activated. The explanation will begin from the point where this support-side medical information storage process is activated.

Here, for example, if a user inputs "AA," the name of the patient whose information is to be stored, via the touchpad 12 of their terminal device 1, and then performs a predetermined operation (an operation to activate the support-side medical information storage process), the control unit 15 of terminal device 1 transmits "patient name information" = "AA" to the medical support device 3. When the control unit 33 of the medical support device 3 receives "patient name information" = "AA" transmitted from terminal device 1, the support-side medical information storage process is activated.

Furthermore, in this embodiment, for example, since each table of support-side medical information has the relationship shown in Figure 6, we will explain the case where information is appropriately stored from the table on the left side of the figure according to medical practice.

===SB1===
In SB1 of Figure 18, the processing unit 331 of the medical support device 3 identifies the patient ID of the patient whose information is to be stored. Specifically, although it is arbitrary, for example, when the support-side medical information storage process is started, the patient name information received is obtained, and by referring to the patient information table T1 in Figure 7, the information of the item "Patient ID" associated with the item "Patient Name" which stores the same information as the patient name information obtained above is identified as the patient ID of the patient whose information is to be stored.

Here, for example, the "Patient Name Information" = "AA" received when the support-side medical information storage process is started is obtained. Referring to the patient information table T1 in Figure 7, the "IDp1," which is the information of the "Patient ID" item associated with the "Patient Name" item (which contains the same information as the obtained "Patient Name Information" = "AA"), is identified as the patient ID of the patient whose information is to be stored.

===SB2===
In SB2 of Figure 18, the processing unit 331 of the medical support device 3 displays each input screen. Specifically, it performs the same processing as SA1 in Figure 16 and displays each input screen on the display 17 of the terminal device 1.

Here, for example, each input screen in Figure 14 is displayed on the display 13. Note that for input fields P11 to P12, etc., of the patient information input screen, for the convenience of confirmation when entering various information, the system may be configured to display information already stored in the support-side medical information DB 321. In this case, for example, the processing unit 331 may refer to the patient information table T1 in Figure 7 to obtain information such as the "Patient Name" item and the "Gender" item, which are associated with the "Patient ID" item containing the same information as the patient ID identified in SB1, and generate input screen information so that each of the obtained pieces of information is displayed in the corresponding input fields P11 to P12, etc.

===SB3===
In SB3 of Figure 18, the processing unit 331 of the medical support device 3 determines whether or not to display medical information that is a candidate for transfer among the medical information stored on the medical record side medical information DB 221 (hereinafter referred to as "transfer candidate medical information"). Specifically, although it is optional, for example, when storing support-side medical information, the device focuses on the fact that the user taps and selects each input field in Figure 14 via the touchpad 12 and inputs the medical information to be stored into the selected input field, and makes a determination based on whether or not an input field corresponding to the "transfer item" (described above) has been selected.

In detail, when a user taps and selects any input field, the control unit 15 of the terminal device 1 transmits the input field ID of the selected input field to the medical support device 3. The processing unit 331 of the medical support device 3, upon receiving the input field ID transmitted from the terminal device 1, refers to the storage location identification information in Figure 15 and determines whether the same information as the received input field ID is stored as the "input field ID" information. If the same information is not stored, it determines that the input field corresponding to the "transfer item" was not selected, and decides not to display the "transfer candidate medical information" (SB3 NO), proceeding to SB7. If the same information is stored, it determines that the input field corresponding to the "transfer item" was selected, and decides to display the "transfer candidate medical information" (SB4 YES), proceeding to SB4.

Here, for example, to input information into input fields P21-P22 on the episode information input screen in Figure 14, if the user first taps and selects input field P21, the control unit 15 of terminal device 1 transmits the "input field ID" = "ID21" of the selected input field P21 to the medical support device 3. The processing unit 331 of medical support device 3 then receives the "input field ID" = "ID21" transmitted from terminal device 1, refers to the storage location identification information in Figure 15, and determines that the same information as the received "input field ID" = "ID21" is not stored as information for the item "input field ID," and therefore does not display the "transfer candidate medical information" (NO in SB3), and proceeds to SB7.

===SB7===
In SB7 of Figure 18, the processing unit 331 of the medical support device 3 determines whether or not to store the medical information entered in each input screen. Specifically, although optional, for example, when a user performs a predetermined operation to store information via the touchpad 12 (for example, tapping a record button not shown), the control unit 15 of the terminal device 1 transmits information of a combination of the medical information entered in the input field and the input field ID that identifies the input field in which the medical information was entered to the medical support device 3. If the processing unit 331 of the medical support device 3 has not received the information of this combination from the terminal device 1, it determines that the medical information will not be stored (NO in SB7) and proceeds to SB3. If the information of this combination has been received from the terminal device 1, it determines that the medical information will be stored (YES in SB7) and proceeds to SB8.

Here, for example, if a user enters "gastric cancer" and "tubular adenocarcinoma" in input fields P21-P22 of the episode information input screen shown in Figure 14 via the touchpad 12 and taps the record button (not shown), the control unit 15 of the terminal device 1 transmits information for each combination, such as "gastric cancer" and "ID21," and "tubular adenocarcinoma" and "ID22," to the medical support device 3. Upon receiving this information for each combination, the processing unit 331 of the medical support device 3 determines that it should store medical information (YES in SB7) and proceeds to SB8.

===SB8===
In SB8 of Figure 18, the processing unit 331 of the medical support device 3 stores medical information. Specifically, although it is arbitrary, for example, based on the information of each combination received from the terminal device 1 (information of the combination of medical information entered in the input field and the input field ID), the medical information entered in the input field is stored in the support-side medical information DB 321.

In general terms, for example, by referring to the input screen-related information in Figure 13, the system identifies the table and items within that table to store the medical information received from terminal device 1 (i.e., the medical information contained in each combination of information received from terminal device 1), and stores the information based on the identification result. More specifically, for example, "SB8's first processing" to "SB8's second processing" are executed for each combination of information received by SB7.

=SB8's first process=
In the "first processing of SB8," the system refers to the input screen related information in Figure 13 to identify the information of the item "Table" and the item "Information" associated with the item "Input Field ID" which contains the same information as the input field ID among the medical information and input field IDs received from the terminal device 1. The system identifies the table indicated by the identified item "Table" as the table to be used to store the medical information received from the terminal device 1, and also identifies the item indicated by the identified item "Information" as the item to be used to store the medical information received from the terminal device 1.

Here, for example, regarding "gastric cancer" and "ID21" received from terminal device 1, in the input screen related information of Figure 13, the item "Input Field ID" = "ID21" is associated with the items "Table" = "Episode Information" and "Information" = "Carcinoma Classification". Therefore, "Episode Information Table T2" is identified as the table to store "gastric cancer," which is medical information received from terminal device 1, and the item "Carcinoma Classification" is identified as the item to store "gastric cancer." Similarly, regarding "tubular adenocarcinoma" and "ID22" received from terminal device 1, "Episode Information Table T2" is identified as the table to store "tubular adenocarcinoma," and the item "Cancer Tissue" is identified as the item to store "tubular adenocarcinoma."

=SB8's second process=
In the "second processing of SB8," medical information received from terminal device 1 is stored according to the identification result of the "first processing of SB8."

Here, for example, the medical information entered in each input field of the episode information input screen in Figure 14 will be newly stored in the episode information table T2 in Figures 6 and 8. Therefore, a unique episode ID is generated, and the current date is identified using an arbitrary method (for example, by referring to the timing result of the timing means (timer, etc.) of the medical support device 3). Then, in the episode information table T2 in Figure 8, the information for the items "Episode ID," "Patient ID," and "Update Date" are stored, representing the generated episode ID, the patient ID identified by SB1, and the identified date. The medical information received from the terminal device 1 is then stored in association with each of these stored pieces of information.

As an example, an "Episode ID" = "IDse1" is generated, and the current date "2020/7/1" is identified using any method. Then, as shown in the top row of Figure 8, the items "Episode ID" = "Dse1", "Patient ID" = "IDp1" (the patient ID identified in SB1), and "Update Date" = "2020/7/1" are stored. Additionally, items such as "Cancer Type Classification" = "Gastric Cancer" and "Cancer Tissue" = "Tubular Adenocarcinoma" are also stored.

===Example of YES in SB3===

Furthermore, in SB3 of Figure 18, for example, in order to input information into input fields P31 to P32 of the treatment information input screen in Figure 14, if the user first taps and selects input field P31, the control unit 15 of the terminal device 1 transmits the "input field ID" = "ID31" of the selected input field P31 to the medical support device 3. The processing unit 331 of the medical support device 3 then receives the "input field ID" = "ID31" transmitted from the terminal device 1, refers to the storage location identification information in Figure 15, and determines that the same information as the received "input field ID" = "ID31" is stored as the information for the item "input field ID," and therefore determines to display the "transfer candidate medical information" (YES in SB3), and proceeds to SB4.

===SB4===
In SB4 of Figure 18, the processing unit 331 of the medical support device 3 transmits a transcription candidate medical information request signal (at least a signal to request "transcription candidate medical information") to the electronic medical record information storage device 2. Specifically, although it is arbitrary, for example, it obtains the input field ID received in SB3 (i.e., the input field ID of the input field selected by the user by tapping), refers to the storage location identification information in Figure 15, obtains the item "Medical Record Side Storage Location Information" which is associated with the item "Input Field ID" where the same information as the obtained input field ID is stored, and identifies the table and items indicated by the information of the obtained item "Medical Record Side Storage Location Information" as the storage location associated with the input field selected by the user. Then, it generates a transcription candidate medical information request signal including the information indicating the identified storage location (i.e., the information of the item "Medical Record Side Storage Location Information" obtained above) and the patient ID identified in SB1, and transmits it to the electronic medical record information storage device 2.

Here, for example, the "Input Field ID" = "ID31" received by SB3 is acquired, and by referring to the storage location identification information in Figure 15, the item "Medical Record Side Storage Location Information" = "Medical Record Side Prescription History Details - Drug Name," which is associated with the item "Input Field ID" = "ID31" where the same information as the acquired "Input Field ID" = "ID31" is stored, is acquired. The medical record side prescription history details T93 and the item "Drug Name" shown in Figure 5, indicated by the acquired item "Medical Record Side Storage Location Information" = "Medical Record Side Prescription History Details - Drug Name," are identified as the storage location associated with the input field selected by the user. Then, a transcription candidate medical information request signal is generated, including the information indicating the identified storage location, "Medical Record Side Prescription History Details - Drug Name," and the "Patient ID" = "IDp1" identified by SB1, and transmitted to the electronic medical record information storage device 2.

===SC1===
Meanwhile, in SC1 of Figure 18, the control unit 23 of the electronic medical record information storage device 2 receives the transcription candidate medical information request signal transmitted in SB4. Here, for example, it receives the transcription candidate medical information request signal which includes "Medical record side prescription history details - drug name" and "IDp1".

===SC2===
In SC2 of Figure 18, the control unit 23 of the electronic medical record information storage device 2 acquires "medical information to be transcribed." Specifically, although it is arbitrary, for example, it acquires information indicating the storage location and the patient ID included in the medical information request signal for medical information to be transcribed received by SC1, refers to the medical record-side medical information DB 221 to identify the medical information of the table and item indicated by the information indicating the storage location, and then acquires the medical information associated with the item "Patient ID" that stores the same information as the aforementioned acquired patient ID among the identified medical information as "medical information to be transcribed."

<Reference information>
Furthermore, the system may be configured to acquire any information other than the "medical information candidates for transcription." For example, if there are multiple "medical information candidates for transcription," the system may be configured to acquire other information predetermined for each table (hereinafter referred to as "reference information") so that the user can visually select the appropriate information. In this embodiment, the case in which "reference information" is also acquired will be described.

For example, in the medical record-side prescription history details table T93 in Figure 5, if the information for the item "Drug Name" is "Candidate Medical Information for Transfer," then the information for the items "Prescription Date" and "Update Date" are set as "Reference Information." Similarly, if the information for the item "Prescription Date" is "Candidate Medical Information for Transfer," then the information for the items "Drug Name" and "Update Date" are set as "Reference Information." Furthermore, for example, in the medical record-side laboratory information table T92 in Figure 4, if the item "Laboratory Value" is "Candidate Medical Information for Transfer," then the information for the items "Laboratory Date" and "Update Date" are set as "Reference Information." Similarly, if the item "Laboratory Date" is "Candidate Medical Information for Transfer," then the information for the items "Laboratory Value" and "Update Date" are set as "Reference Information." Note that the reference information described here is illustrative; if multiple "Candidate Medical Information for Transfer" exists, other arbitrary information may be set as reference information, as long as the user can visually select the appropriate information from these multiple pieces of information.

<Specific examples>
Here, for example, in Figure 5, the items "Drug Name" = "A1 Drug" and "B1 Drug" are specifically illustrated. However, at the time of processing in SC2, "B1 Drug" has not yet been stored. In addition to the information at the top of Figure 5, the items "Drug Name" = "A2 Drug" (corresponding items "Prescription Date" and "Update Date" = "2020/6/22") and "Drug Name" = "A3 Drug" (corresponding items "Prescription Date" and "Update Date" = "2020/6/25") are stored as information associated with the item "Patient ID" = "IDp1", which is not illustrated.

In this case, the "storage location information" = "Medical record prescription history details - drug name" and "Patient ID" = "IDp1" included in the transcription candidate medical information request signal received by SC1 are obtained. By referring to the medical record medical information DB221, the medical information "A1 drug," "A2 drug" (not shown), and "A3 drug" (not shown), which are the medical information for the "drug name" item in the medical record prescription history details table T93 in Figure 5, are identified. Since these identified "A1 drug," "A2 drug," and "A3 drug" are all associated with the item "Patient ID" = "IDp1," they are obtained as "transfer candidate medical information." Furthermore, in this case, the "reference information" for "A1 drug," "A2 drug," and "A3 drug" includes the items "prescription date" and "update date" = "2020/7/1," "2020/6/22" (not shown), and "2020/6/25" (not shown), respectively.

===SC3===
In SC3 of Figure 18, the control unit 23 of the electronic medical record information storage device 2 transmits a transcription candidate medical information response signal (a signal for transmitting at least "transcription candidate medical information") to the medical support device 3. Specifically, although it is optional, for example, it generates a transcription candidate medical information response signal that includes the "transcription candidate medical information" and "reference information" acquired in SC2 and transmits it to the medical support device 3.

Here, for example, a response signal containing "Transfer Candidate Medical Information" (e.g., "A1 Drug") and "Reference Information" (e.g., "2020/7/1" - in this case, the prescription date and update date are the same) acquired by SC2 is generated and transmitted to the medical support device 3.

===SB5===
Meanwhile, in SB5 of Figure 18, the processing unit 331 of the medical support device 3 receives the transcription candidate medical information response signal transmitted by SC3. Here, it receives a transcription candidate medical information response signal that includes, for example, "Transcription candidate medical information" = "A1 drug" and "Reference information" = "2020/7/1" (in this case, the prescription date and update date are the same).

===SB6===
In SB6 of Figure 18, the processing unit 331 of the medical support device 3 displays a screen for displaying candidate medical information for transcription. Figure 19 shows an example of the display screen for displaying candidate medical information for transcription. The "screen for displaying candidate medical information for transcription" is a screen for displaying at least "candidate medical information for transcription," and optionally also displays "reference information." The processing of SB6 is specific and optional, but for example, the "candidate medical information for transcription" and "reference information" contained in the candidate medical information for transcription response signal received in SB5 are acquired, screen information for displaying the candidate medical information for transcription is generated based on the acquired "candidate medical information for transcription" and "reference information," and the generated screen information is transmitted to the terminal device 1, whereupon it is displayed on the display 13 of the terminal device 1.

Here, for example, the "medical information to be transcribed" = "A1 drug" etc. and "reference information" = "2020/7/1" etc. included in the medical information response signal for transcribed received by SB5 are acquired, and screen information for displaying the medical information to be transcribed shown in Figure 19 is generated based on the acquired information. Specifically, the text "A1 drug" is displayed based on the "medical information to be transcribed" = "A1 drug" etc., and the text "(prescription date: 2020/7/1 update date: 2020/7/1)" etc. is displayed following the text "A1 drug" etc. based on the "reference information" = "2020/7/1" etc. Furthermore, screen information is generated so that each piece of information is displayed sorted (i.e., rearranged) according to a predetermined sorting criterion (a predetermined criterion; in this embodiment, the "medical information to be transcribed" whose prescription date (or update date, as an example) is closer to the current date is displayed higher on the screen). Furthermore, although not shown in Figure 19, screen information may be generated by filtering (i.e., narrowing down each piece of information) according to a predetermined filtering criterion (a predetermined criterion; for example, one criterion is to narrow down the display to only two pairs of "candidate medical information for transcription" and "reference information" whose prescription date (or, in a modified example, update date) is close to the current date, and only these two narrowed-down pairs of "candidate medical information for transcription" and "reference information" are displayed on the screen information). Then, this generated screen information is transmitted to display, for example, the candidate medical information for transcription display screen in Figure 19 on the display 13 of the terminal device 1.

With this configuration, for example, a user who taps and selects input field P31 in Figure 14 can check the "Transfer Candidate Medical Information" displayed on the Transfer Candidate Medical Information Display Screen, select one "Transfer Candidate Medical Information" from among them using any method, and input the same medical information as the selected "Transfer Candidate Medical Information" into input field P31 via the touchpad 12. In other words, it becomes possible to store the same medical information stored on the electronic medical record information storage device 2 in Figure 1 on the medical support device 3.

===Repeated Processing===
Then, after performing SB7 and the aforementioned SB3-SB4, SC1-SC3, SB5-SB6 etc. as appropriate, and entering "A1 drug" and "2020/7/1" into input fields P31-P32 of the treatment information input screen in Figure 14 and tapping the unshown record button, the control unit 15 of the terminal device 1 transmits information for each combination of "A1 drug" and "ID31", and "2020/7/1" and "ID32" to the medical support device 3. When the processing unit 331 of the medical support device 3 receives the information for each combination, it determines that medical information should be stored (YES for SB7) and proceeds to SB8.

Here, for example, in the "First Processing of SB8" in Figure 18, in the input screen-related information in Figure 13, the "Treatment Information Table T3" is identified as the table to store "A1 Drug" and "2020/7/1," similar to the case described above. Furthermore, the items "Drug Name" and "Prescription Date" are identified as the items to store "A1 Drug" and "2020/7/1."

Next, in the "SB8 second processing," the medical information entered in each input field of the treatment information input screen in Figure 14 will be newly stored in the treatment information table T3 in Figures 6 and 9. Therefore, a unique treatment information ID is generated, the episode ID is identified using a method described later, and the current date is identified using an arbitrary method. Then, in the treatment information table T3 in Figure 9, the information for the items "Treatment Information ID," "Episode ID," "Patient ID," and "Update Date" are stored, representing the generated treatment information ID, the identified episode ID, the patient ID identified in SB1, and the identified date. The medical information received from terminal device 1 is then stored in association with each of these stored pieces of information.

The method for identifying the episode ID is arbitrary, but for example, one may refer to the episode information table T2 in Figure 6 and identify the "episode ID" associated with the "patient ID" item that stores the same information as the patient ID identified in SB1. In this case, it is conceivable that, for example, if the patient's cancer progresses, if the patient is currently suffering from a different cancer than the one previously suffered from, or if the patient is suffering from multiple types of cancer, there may be multiple episode IDs associated with the patient ID identified in SB1 (i.e., the patient ID that identifies the patient whose information is to be stored) in the episode information table T2 in Figure 8. In this case, one episode ID may be identified using either the "first method" or the "second method" described below.

The "first method" focuses on the "Update Date" item in the episode information table T2 shown in Figure 8. In this method, for example, if there are multiple entries for the "Episode ID" item associated with the patient ID identified in SB1 in the episode information table T2, the method identifies the single "Episode ID" entry that contains the "Update Date" information closest to the current date.

The "second method" is a method that allows the user to make a selection. In this method, for example, if there are multiple pieces of information for the item "Episode ID" associated with the patient ID identified in SB1 in the episode information table T2, the information for each of these multiple items "Episode ID" (i.e., the information for each item illustrated in Figure 8) is transmitted to the terminal device 1 and displayed on the display 13. When the user taps and selects one piece of information for "Episode ID" via the touchpad 12, the terminal device 1 transmits the information for the tapped item "Episode ID" to the medical support device 3, and identifies the transmitted item "Episode ID".

As an example, a "Treatment Information ID" = "IDsm1" is generated, and by referring to the episode information table T2 in Figure 8, the item "Episode ID" = "IDse1" associated with the item "Patient ID" which stores the same information as the "Patient ID" = "IDp1" identified in SB1 is identified. Furthermore, "2020/7/1" is identified as the current date using any method. Then, as shown in the top row of Figure 9, the items "Treatment Information ID" = "IDsm1", "Episode ID" = "Dse1", "Patient ID" = "IDp1" (the patient ID identified in SB1), and "Update Date" = "2020/7/1" are stored. Additionally, the items "Drug Name" = "A1 Drug" and "Prescription Date" = "2020/7/1" are stored.

===Storage in other tables (effect judgment information table)===
Furthermore, for example, if "Progress" and "2020/8/15" are entered in input fields P41 to P42 of the effect evaluation information input screen in Figure 14 and the record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information for each combination of "Progress" and "ID41", and "2020/8/15" and "ID42" to the medical support device 3. The processing unit 331 of the medical support device 3 receives the information for each combination and performs "SB8's first processing" and "SB8's second processing" based on the received information for each combination, and stores the information in the uppermost row of Figure 10.

In particular, in the "second processing of SB8," the information in the effect evaluation information table T4 of Figures 6 and 10 will be newly stored. Therefore, a unique effect evaluation information ID is generated, the episode ID is identified in the same manner as described above, the treatment information ID is identified using a method described later, and the current date is identified using an arbitrary method. Then, in the effect evaluation information table T4 of Figure 10, the information for the items "Effect Evaluation Information ID," "Episode ID," "Patient ID," "Treatment Information ID," and "Update Date" are stored, representing the generated effect evaluation information ID, the identified episode ID, the patient ID identified in SB1, the identified treatment information ID, and the identified date. Medical information received from terminal device 1 is then stored in association with each of these stored pieces of information.

The method for identifying the treatment information ID is arbitrary. For example, one may refer to the treatment information table T3 in Figure 9 to identify the "Patient ID" item, which stores the same information as the patient ID identified in SB1, and the "Treatment Information ID" item, which is associated with the previously identified episode ID. In this case, for example, in various cases such as when multiple drugs are administered for treatment, it is conceivable that there may be multiple patient IDs (i.e., patient IDs that identify the patient for whom the information is to be stored) and treatment information IDs associated with the previously identified episode ID in the treatment information table T3 in Figure 9. In this case, similar to the "first method" and "second method" described above for the episode ID, one treatment information ID may be identified by focusing on the "Update Date" item in the treatment information table T3 in Figure 9, or by allowing the user to select a method.

===Storage in other tables (adverse event information table)===
Furthermore, for example, if "vomiting" and "2" are entered in input fields P51 to P52 of the side effect information input screen in Figure 14 and the record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information on each combination of "vomiting" and "ID 51", and "2" and "ID 52" to the medical support device 3. The processing unit 331 of the medical support device 3 receives the information on each combination and performs the "first processing of SB8" and the "second processing of SB8" based on the received information on each combination, and stores the information in the uppermost row of Figure 11. In this case, as shown in Figure 6, the side effect information table T5 is associated with the treatment information table T3 in the same way as the effect judgment information table T4 described above, and is therefore stored in the same way as the effect judgment information table T4.

===Storage in other tables (inspection information tables)===
Figure 20 shows an example of the display screen for the medical information to be transcribed. Also, for example, in order to input information into input fields P61 to P64 on the examination information input screen in Figure 14, if the user first taps and selects input field P61, then, in the same manner as described above, after SB3 YES, SB4, SC1 to SC3, and SB5 in Figure 18, at SB6, for example, the medical information to be transcribed screen in Figure 20 will be displayed on the display 13.

Then, after checking this transfer candidate medical information display screen, or other transfer candidate medical information display screens that appear when other input fields are selected, if "D3" and "2020/7/1" are entered into input fields P61 to P62 of the examination information input screen in Figure 14 and the record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information such as "D3" and "ID61" and "2020/7/1" and "ID62" for each combination to the medical support device 3. The processing unit 331 of the medical support device 3 receives the information for each combination and performs "SB8's first processing" and "SB8's second processing" based on the received information for each combination, and stores the information in the third row of Figure 12. In particular, as information for the item "Examination Item Name", "KRAS" as the examination item for "D3", which is medical information of the examination value, is stored. Furthermore, in this case, as shown in Figure 6, the examination information table T6 is associated with the episode information table T2 in the same way as the treatment information table T3 described above, and is therefore stored in the same manner as the treatment information table T3. This concludes the explanation of the support-side medical information storage process.

(Effects of the embodiment)
As described above, according to this embodiment, by performing processing related to storing medical information based on storage location identification information (association information), for example, it is possible to process the input fields associated with a predetermined storage location (second storage location) of medical information in the support-side medical information DB 321 and the predetermined storage location (first storage location) of medical information in the medical record-side medical information DB 221 in relation to each other, thereby enabling efficient storage of medical information.

Furthermore, by displaying medical information stored in a predetermined storage location for medical information in the medical record-side medical information DB 221 associated with at least one input field selected by the user, it becomes possible to quickly and accurately transcribe medical information stored in a predetermined storage location for medical information in the medical record-side medical information DB 221, thereby enabling efficient storage of medical information.

Furthermore, by filtering or sorting medical information for display, for example, the visibility of medical information can be improved, making it possible to store medical information efficiently.

[Modifications of the embodiment]
While embodiments of the present invention have been described above, the specific configurations and means of the present invention can be arbitrarily modified and improved within the scope of the technical idea of each invention described in the claims. Such modifications will be described below.

(Regarding the problems to be solved and the effects of the invention)
First, the problems that the invention aims to solve and the effects of the invention are not limited to those described above, and may vary depending on the implementation environment and details of the invention's configuration. In some cases, only a portion of the problems described above may be solved, or only a portion of the effects described above may be achieved.

(Regarding decentralization and integration)
Furthermore, the above-described configuration is a functional concept and does not necessarily require that the system be physically configured as shown in the illustration. In other words, the specific forms of distribution and integration of each part are not limited to those shown in the illustration, and all or part of them can be functionally or physically distributed or integrated in any unit. In this application, "system" is not limited to those composed of multiple devices, but also includes those composed of a single device. Similarly, in this application, "device" is not limited to those composed of a single device, but also includes those composed of multiple devices.

(Regarding filtering and sorting)
Furthermore, the filtering and sorting described in the above embodiment may be configured to perform both, or to perform only one of them.

(Regarding the automatic storage of medical information)
Furthermore, while the above embodiment describes a case where the user inputs and stores the information for the "transfer items," it is not limited to this. For example, the system may be configured to automatically store the information for the "transfer items." The specific implementation method for such a configuration is arbitrary, but for example, it may be configured to execute other support-side medical information storage processes.

(Regarding the automatic storage of medical information - Medical information storage processing by other support systems)
Figure 21 is a flowchart of the other support-side medical information storage process. The "other support-side medical information storage process" is, in general terms, a process executed by the electronic medical record information storage device 2 and the medical support device 3, and specifically, it is a process that automatically stores the information of the "transfer items". The timing of executing this other support-side medical information storage process is arbitrary, but for example, it will be started repeatedly at predetermined intervals (for example, every 24 hours), and the explanation will begin from the point when the other support-side medical information storage process has been started.

===SD1===
In SD1 of Figure 21, the processing unit 331 of the medical support device 3 transmits a medical information request signal to the electronic medical record information storage device 2. The "medical information request signal" is a signal that requests the transmission of medical information when medical information corresponding to the information of the "transfer item" is newly stored in the medical record medical information DB 221. The medical information on the medical record medical information DB 221 side that corresponds to the information of the "transfer item" is also called "medical information to be transferred from the medical record side". Specifically, although it is arbitrary, for example, the item "medical record side storage location information" in the storage location identification information of Figure 15 stores information on a combination of table name information and item name information of the medical record side medical information DB 221 that will be transferred as information of the "transfer item". Focusing on the fact that the "medical information to be transferred from the medical record side" can be identified based on each piece of information, the following processing is performed.

In detail, the information for the item "Medical Record Storage Location Information" in Figure 15 (hereinafter also simply referred to as "Medical Record Storage Location Information") is acquired, and a medical information request signal containing the acquired Medical Record Storage Location Information is generated and transmitted to the electronic medical record information storage device 2.

Here, for example, a medical information request signal is generated and transmitted to the electronic medical record information storage device 2, including "Medical record prescription history details - drug name," "Medical record prescription history details - prescription date," and "Medical record test information - test value (KRAS)," as shown in Figure 15.

===SE1===
Meanwhile, in SE1 of Figure 21, the control unit 23 of the electronic medical record information storage device 2 receives the medical information request signal transmitted by SD1. Here, for example, it receives a medical information request signal that includes "medical record storage location information" = "medical record prescription history details - drug name", "medical record prescription history details - prescription date", and "medical record test information - test value (KRAS)", etc.

===SE2===
In SE2 of Figure 21, the control unit 23 of the electronic medical record information storage device 2 acquires newly stored "medical information to be transferred to the medical record side". Specifically, although this is arbitrary, for example, we will explain the case where the "other support-side medical information storage process" is configured to be executed at the end of the day, and the "update date" information associated with the "medical information to be transferred to the medical record side" in each table of the medical record-side medical information DB 221 is stored as information indicating the current date, and the "medical information to be transferred to the medical record side" is considered to have been newly stored.

In detail, the system acquires the "medical record storage location information" contained in the medical information request signal received by SE1, refers to each table in the medical record-side medical information DB221 to identify the information corresponding to the table and item indicated by the "medical record-side storage location information" as "medical information to be transferred to the medical record side," acquires the "update date" information of the item associated with the identified "medical information to be transferred to the medical record side" within the table, and identifies the current date by any method. If the acquired "update date" information does not contain the same information as the information indicating the current date identified above, it is determined that the identified "medical information to be transferred to the medical record side" was already stored on the previous day and was already stored on the support-side medical information DB321 side as "transfer item" information in processing on the previous day or earlier, and therefore the identified "medical information to be transferred to the medical record side" has not been newly stored in the medical record-side medical information DB221. On the other hand, if the information stored in the "Update Date" field, as mentioned above, is the same as the information indicating the current date identified earlier, then the identified "Medical Information to be Transmitted to the Medical Record" is determined to have been newly stored in the Medical Record-side Medical Information DB 221. This is because the "Transmitted Item" information has not yet been stored in the support-side Medical Information DB 321. After these determinations, the "Medical Information to be Transmitted to the Medical Record" that has been determined to be newly stored is retrieved.

Here, we will explain in detail, for example, the "Medical Record Storage Location Information" = "Medical Record Prescription History Details - Drug Name" included in the medical information request signal received by SE1. Furthermore, as explained in "SC2" in Figure 18, for example, in Figure 5, the items "Drug Name" = "A1 Drug" and "B1 Drug" are specifically illustrated. However, "B1 Drug" has not yet been stored. In addition to the information at the top of Figure 5, we will illustrate and explain the case where the items "Drug Name" = "A2 Drug" (corresponding items "Prescription Date" and "Update Date" = "2020/6/22") and "Drug Name" = "A3 Drug" (corresponding items "Prescription Date" and "Update Date" = "2020/6/25") are stored as information associated with the unillustrated item "Patient ID" = "IDp1".

In this case, the "Medical Record Storage Location Information" = "Medical Record Prescription History Details - Drug Name" included in the medical information request signal is obtained, and by referring to each table in the Medical Record Medical Information DB221, the Medical Record Prescription History Details Table T93 and the items "Drug Name" = "A1 Drug", "A2 Drug" (not shown), and "A3 Drug" (not shown) shown in Figure 5, which are indicated by the "Medical Record Storage Location Information" = "Medical Record Prescription History Details - Drug Name", are identified as "Medical Information to be Transmitted from the Medical Record". The items "Update Date" = "2020/7/1", "2020/6/22 (not shown)", and "2020/6/25" (not shown) associated with the identified "A1 Drug", "A2 Drug", and "A3 Drug" in the Medical Record Prescription History Details Table T93 are obtained, and "Current Date" = "2020/7/1" is identified. Then, only the "Update Date" item associated with "A1 Drug" = "2020/7/1" has the same information as "Current Date" = "2020/7/1". Therefore, "A1 Drug" is determined to be newly stored, while "A2 Drug" and "A3 Drug" are not determined to be newly stored. The item "Drug Name" = "A1 Drug" is then retrieved.

Furthermore, the same processing is performed on other "medical record storage location information" included in the medical information request signal received by SE1 (for example, the information illustrated in the item "Medical Record Storage Location Information" in Figure 15) to obtain the item "Prescription Date" = "2020/7/1" in Figure 5, and the item "Test Value" = "D3" and the item "Test Date" = "2020/7/1" associated with the test item name = "KRAS" in Figure 4.

===SE3===
In SE3 of Figure 21, the control unit 23 of the electronic medical record information storage device 2 transmits a medical information response signal to the medical support device 3. The "medical information response signal" is a signal for transmitting information that combines the aforementioned "medical information to be transcribed from the medical record side,""related information from the medical record side," and "storage location information from the medical record side." The "related information from the medical record side" is information associated with the "medical information to be transcribed from the medical record side" in each table of the medical record side medical information DB 221, and specifically, it is information that is necessary when storing the "medical information to be transcribed from the medical record side" on the medical support device 3 side in the processing described later. In this embodiment, "Medical record-related information" refers to the information in the "Medical record-related information" fields. For example, if the "Medical record-related medical information to be transcribed" is the information in the medical record-side examination information table T92 shown in Figure 4, then the "Medical record-related information" will be the information in the fields "Patient ID" and "Examination Item Name". If the "Medical record-related medical information to be transcribed" is the information in the medical record-side prescription history details table T93 shown in Figure 5, then the "Medical record-related information" will be the information in the field "Patient ID". It should be noted that the Medical Record-related information is not limited to this example, and any other information may be used based on the applicable data structure, etc.

The specific processing of SE3 is optional, but for example, it refers to each table in the medical record-side medical information DB221 to obtain "related medical record information" associated with the "medical record-side information to be transcribed" obtained in SE2. It also identifies the "medical record-side storage location information" that indicates the storage location of the "medical record-side information to be transcribed" obtained in SE2, from the "medical record-side storage location information" included in the medical information request signal received in SE1. Finally, it generates and transmits a medical information response signal containing information on the combination of the "medical record-side information to be transcribed" obtained in SE2, the aforementioned obtained "related medical record information," and the aforementioned identified "medical record-side storage location information."

Here, for example, for the item "Drug Name" = "A1 Drug," which is "Medical Information to be Transcribed to the Medical Record" acquired by SE2, the item "Patient ID" = "IDp1" is acquired as "Medical Record Related Information." In addition, "Medical Record Prescription History Details - Drug Name" is identified from the "Medical Record Storage Location Information" included in the medical information request signal received by SE1, and "A1 Drug," "IDp1," and "Medical Record Prescription History Details - Drug Name" are associated as a combination of information. Similarly, for other information, "2020/7/1," "IDp1," and "Medical Record Prescription History Details - Prescription Date" are associated as a combination of information, "D3," "IDp1," "KRAS," and "Medical Record Test Information - Test Value (KRAS)" are associated as a combination of information, and "2020/7/1," "IDp1," "KRAS," and "Medical Record Test Information - Test Date (KRAS)" are associated as a combination of information. Then, a medical information response signal containing this combination of information is generated and transmitted.

===SD2===
Meanwhile, in SD2 of Figure 21, the processing unit 331 of the medical support device 3 receives the medical information response signal transmitted by SE3. Here, it receives a medical information response signal that includes, for example, information such as the combination of "A1 drug", "IDp1", and "medical record prescription history details - drug name".

===SD3===
In SD3 of Figure 21, the processing unit 331 of the medical support device 3 stores medical information from the support-side medical information DB 321 based on the medical information response signal received in SD2. Specifically, this is arbitrary, but in general terms, for example, the processing unit identifies the storage location of the "medical information to be transcribed to the medical record" and "related information to the medical record" included in the medical information response signal, and stores the "medical information to be transcribed to the medical record" and "related information to the medical record" in the identified storage location. In detail, for example, the processing unit executes "the first processing of SD3" to "the second processing of SBD3".

=SD3's first processing=
In the "first processing of SD3," first, the "medical record side storage location information" included in the medical information response signal received by SD2 is acquired, the storage location identification information in Figure 15 is referenced to identify the "input field ID" item associated with the same information as the acquired "medical record side storage location information," and the input screen related information in Figure 13 is referenced to identify the table and items indicated by the "medical information" item associated with the same information as the identified "input field ID" item as the storage location of the "medical information to be transcribed from the medical record side" included in the "medical record side storage location information" included in the medical information response signal. Furthermore, the item corresponding to the type of "medical record side related information" in the same table identified as the storage location of the "medical information to be transcribed from the medical record side" is identified as the storage location of the "medical record side related information."

Here, we will explain in detail, as a representative example, the information combining "A1 drug," "IDp1," and "Medical record prescription history details - drug name" included in the medical information response signal received by SD2. In this case, in the "first processing of SD3," first, the "Medical record storage location information" = "Medical record prescription history details - drug name" included in the medical information response signal received by SD2 is obtained, the storage location identification information in Figure 15 is referred to to identify the item "Input field ID" = "ID31" which is associated with the same information as the obtained "Medical record storage location information" = "Medical record prescription history details - drug name," and the input screen related information in Figure 13 is referred to to associate the identified item "Input field ID" = "ID31" with the same information. The information in the item "Medical Information" (item "Table" = "Treatment Information" and item "Information" = "Drug Name") in Figure 9, specifically the Treatment Information Table T3 and the item "Drug Name," are identified as the storage location for "Medical Information to be Transcribed from the Medical Record Side" = "A1 Drug" included in the "Medical Record Side Storage Location Information" contained in the Medical Information Response Signal. Furthermore, the item "Patient ID," corresponding to the type of "Medical Record Side Related Information" = "IDp1" in Treatment Information Table T3 in Figure 9, is identified as the storage location for "Medical Record Side Related Information" = "IDp1."

Furthermore, similar processing is performed on other combinations of information contained in the medical information response signal received by SD2. For example, the storage location for "Medical information to be transcribed to the medical record" = "2020/7/1" is identified as the treatment information table T3 and the item "Prescription Date" in Figure 9, and the storage location for "Medical record related information" = "IDp1" is identified as the treatment information table T3 and the item "Patient ID" in Figure 9. Also, for example, the storage location for "Medical information to be transcribed to the medical record" = "D3" is identified as the examination information table T6 in Figure 12 and the item "Examination Value" associated with "Item" = "KRAS," and the storage locations for "Medical record related information" = "IDp1" and "KRAS" are identified as the examination information table T6 in Figure 12 and the items "Patient ID" and "Examination Date" associated with "Item" = "KRAS." Furthermore, for example, the storage location for "Medical Information to be Transcribed from the Medical Record" = "2020/7/1" is identified as the "Examination Date" item associated with the "Item" = "KRAS" in the examination information table T6 of Figure 12. Similarly, the storage locations for "Medical Record Related Information" = "IDp1" and "KRAS" are identified as the "Patient ID" and "Examination Date" items associated with the "Item" = "KRAS" in the examination information table T6 of Figure 12.

=SD3's second processing=
In the "second processing of SD3," the "medical information to be transcribed to the medical record" and "related information to the medical record" included in the medical information response signal received by SD2 are stored according to the identification result of the "first processing of SD3."

Here, for example, regarding the information identified as the storage location of treatment information table T3 in Figure 9 during the "first processing of SD3," the information from treatment information table T3 in Figures 6 and 9 will be newly stored. Therefore, a unique treatment information ID is generated, the episode ID is identified using the method described in the embodiment, and the current date is identified using an arbitrary method. Then, in treatment information table T3 in Figure 9, the information for the items "treatment information ID," "episode ID," "patient ID," and "update date" are stored, specifically the generated treatment information ID, the identified episode ID, the patient ID included as "medical record-related information" in the medical information response signal received by SD2, and the identified date. The "medical information to be transcribed from the medical record" is then stored in association with each of the stored pieces of information.

For example, a "treatment information ID" = "IDsm1" is generated, and by referring to the episode information table T2 in Figure 8, the item "Episode ID" = "IDse1" is identified, which is associated with the item "Patient ID" that contains the same information as the "Patient ID" = "IDp1" included as "Medical Record Related Information" in the medical information response signal received by SD2. Furthermore, the current date "2020/7/1" is identified using an arbitrary method. Then, as shown in the top row of Figure 9, the following fields are stored: "Treatment Information ID" = "IDsm1", "Episode ID" = "Dse1", "Patient ID" = "IDp1", and "Update Date" = "2020/7/1". Additionally, the following fields are stored: "Drug Name" = "A1 Drug" (corresponding to "Medical Information to be Transcribed to the Chart" = "A1 Drug"), and "Prescription Date" = "2020/7/1" (corresponding to "Medical Information to be Transcribed to the Chart" = "2020/7/1").

Here, for example, regarding the information identified as the storage location in the examination information table T6 in Figure 12 during the "first processing of SD3," the information from the examination information table T6 in Figures 6 and 12 will be newly stored. Therefore, a unique examination information ID is generated, the episode ID is identified using the method described in the embodiment, and the current date is identified using an arbitrary method. Then, in the examination information table T6 in Figure 12, the information for the items "Examination Information ID," "Episode ID," "Patient ID," and "Update Date" are stored as follows: the generated examination information ID, the identified episode ID, the patient ID included as "Medical Record Related Information" in the medical information response signal received by SD2, and the identified date. The "Medical Record Transcribable Medical Information" is then stored in association with each of the stored pieces of information.

As an example, generate "Examination Information ID" = "IDst3," identify "Episode ID" = "IDse1," and then, using any method, identify the current date as "2020/7/1." Then, as shown in the third row of Figure 12, store the items "Examination Information ID" = "IDst3," "Episode ID" = "Dse1," "Patient ID" = "IDp1," and "Update Date" = "2020/7/1." Additionally, store the items "Examination Item Name" = "KRAS" (corresponding to "Medical Record Related Information" = "KRAS"), "Examination Value" = "D3" (corresponding to "Medical Record Transcribed Medical Information" = "D3"), and "Examination Date" = "2020/7/1" (corresponding to "Medical Record Transcribed Medical Information" = "2020/7/1"). This concludes the explanation of other support-side medical information storage processes.

By configuring the system in this way, newly stored medical information in the predetermined storage locations of medical information in the medical record-side medical information DB 221 is stored in the predetermined storage locations of medical information in the support-side medical information DB 321. This automates the process of storing medical information, enabling efficient storage of medical information.

(Regarding the features)
Furthermore, the features of the above embodiments and the features of the modified embodiments may be combined in any way.

(Note)
The medical system described in Appendix 1 is a second medical information storage means for storing medical information relating to a patient stored in a predetermined first storage location in a first medical information storage means, comprising: the second medical information storage means for storing the medical information in a predetermined second storage location in the second medical information storage means; an information input field associated with any of the second storage locations in the second medical information storage means, into which the medical information to be stored in the associated second storage location of the second medical information storage means is entered; an information input field for which information indicating the information input field displayed on a display means and information indicating the first storage location in the first medical information storage means are stored, and an information linkage information is stored therein; and a processing means for performing processing relating to storing medical information in the second medical information storage means based on the information linkage information stored in the information linkage storage means.

The medical system described in Appendix 2, in the medical system described in Appendix 1, wherein the processing means, when multiple information input fields are displayed on the display means, and at least one of the multiple information input fields is selected by the user, performs a first process of identifying the first storage location associated with the selected at least one information input field based on the association information stored in the association information storage means, and a second process of displaying the medical information stored in the first storage location identified in the first process.

The medical system described in Appendix 3, in the medical system described in Appendix 2, has the processing means, in the second processing, filter or sort the medical information stored in the first storage location identified in the first processing, based on predetermined criteria, and display it.

The medical system described in Appendix 4 is a medical system described in any one of Appendix 1 to 3, wherein, when medical information is newly stored in the first storage location of the first medical information storage means, the processing means identifies the second storage location associated with the first storage location based on the association information stored in the association information storage means, and stores the medical information newly stored in the first storage location in the identified second storage location.

The medical program described in Appendix 5 causes the computer to function as a second medical information storage means for storing medical information relating to a patient stored in a predetermined first storage location in the first medical information storage means, the second medical information storage means for storing the medical information in the predetermined second storage location in the second medical information storage means, an information input field associated with any of the second storage locations in the second medical information storage means, into which the medical information to be stored in the associated second storage location of the second medical information storage means is entered, and an information input field for storing the information input field is stored in an information input field, the information to be displayed on a display means for the information input field is stored in an information input field, and information to be displayed on a display means for the first storage location in the first medical information storage means is stored in an information input means for storing the medical information, and a processing means for performing processing related to storing medical information in the second medical information storage means based on the information input field stored in the information input means.

(Effects of the supplement)
According to the medical system described in Appendix 1 and the medical program described in Claim 5, by performing processing related to storing medical information based on association information, for example, it is possible to process the information input field associated with the second storage location and the first storage location in relation to each other, thereby enabling efficient storage of medical information.

According to the medical system described in Appendix 2, by displaying medical information stored in a first storage location associated with at least one information input field selected by the user, it becomes possible to quickly and accurately transcribe the medical information stored in the first storage location, thus enabling efficient storage of medical information.

According to the medical system described in Appendix 3, by filtering or sorting and displaying medical information, for example, the visibility of medical information can be improved, making it possible to store medical information efficiently.

According to the medical system described in Appendix 4, by storing newly stored medical information in the first storage location in the second storage location, for example, the medical information storage process can be automated, making it possible to store medical information efficiently.

1 Terminal device 2 Electronic medical record information storage device 3 Medical support device 11 Communication unit 12 Touchpad 13 Display 14 Recording unit 15 Control unit 21 Communication unit 22 Recording unit 23 Control unit 31 Communication unit 32 Recording unit 33 Control unit 100 Medical-related system 221 Medical record side medical information DB
321 Support-side medical information database
322 Input screen related information database
323 Storage Location Identification Information DB
331 Processing Unit T91 Medical Record Patient Information Table T92 Medical Record Examination Information Table T93 Medical Record Prescription History Details Table P11 Input Field P12 Input Field P21 Input Field P22 Input Field P31 Input Field P32 Input Field P41 Input Field P42 Input Field P51 Input Field P52 Input Field P61 Input Field P62 Input Field P63 Input Field P64 Input Field R1 Table Name Information Display Area R2 Item Name Information Display Area T1 Patient Information Table T2 Episode Information Table T3 Treatment Information Table T4 Effectiveness Evaluation Information Table T5 Side Effect Information Table T6 Examination Information Table

Claims (1)

A second medical information storage means for storing medical information relating to a patient, the second medical information storage means storing the medical information in a plurality of predetermined second storage locations in the second medical information storage means,
A relationship information storage means stores relationship information that correlates information indicating an information input field associated with one of the plurality of second storage locations in the second medical information storage means and information indicating a first storage location in the first medical information storage means,
Processing means that, based on the association information stored in the association information storage means, processes the medical information entered in the information input field to be stored in the second storage location specified by the association information corresponding to the information input field ,
A medical system equipped with these features.