Healthcare Systems and Programs

Abstract

A medical system and a medical program are provided that enable efficient storage of medical information. [Solution] In a medical-related system, a medical support device 3 comprises a second medical information storage means (support side medical information DB321) that stores medical information related to a patient in a second storage location that is predetermined for storing the medical information, a correlation information storage means (storage location identification information DB323) that stores correlation information that correlates information indicating an information input field associated with any second storage location in the second medical information storage means with information indicating a first storage location in the first medical information storage means (medical record side medical information DB221) possessed by the electronic medical record information storage device 2, and a processing means (processing unit 331) that performs processing related to storing medical information in the second medical information storage means based on the correlation information stored in the correlation information storage means.

Description

[Technical Field]

[0001] The present invention relates to medical systems and medical programs. [Background technology]

[0002] BACKGROUND ART Conventionally, a support device (see Patent Document 1) has been known that stores medical information and supports medical practices by medical personnel. [Prior art documents] [Patent documents]

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

[0004] However, there are cases where it becomes necessary to store information stored in an electronic medical record device in an assistance device that stores medical information.

[0005] However, for example, the database structure of the electronic medical record device is complicated, which can make it difficult to determine the storage location of the information stored in the electronic medical record device, making it difficult to quickly store the information in the support device.

[0006] The present invention has been made in view of the above problems, and has as its object to make it possible to store medical information efficiently. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the medical system according to claim 1 comprises a second medical information storage means for storing medical information relating to a patient, oh It is predetermined Multiplea second medical information storage means for storing the medical information in a second storage location; Any of the plurality of second storage locations and a first storage location in the first medical information storage means. The medical information entered in the information entry field is stored in the second storage location specified by the association information corresponding to the information entry field. and a processing means for performing the processing. [Effects of the Invention]

[0008] According to the medical system of claim 1, for example, it becomes possible to store medical information efficiently. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a medical-related system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing a terminal device. [Figure 3] FIG. 10 is a diagram illustrating an example of a medical record-side patient information table. [Figure 4] FIG. 10 is a diagram illustrating an example of a medical record examination information table. [Figure 5] 10 is a diagram illustrating an example of a medical record prescription history detailed information table. [Figure 6] 10A and 10B are diagrams illustrating various tables stored as support-side medical information. [Figure 7] FIG. 10 is a diagram illustrating a patient information table. [Figure 8] FIG. 10 is a diagram illustrating an example of an episode information table. [Figure 9] FIG. 10 is a diagram illustrating a treatment information table. [Figure 10] FIG. 10 is a diagram illustrating an example of an effect determination information table. [Figure 11] FIG. 10 is a diagram illustrating an example of a side effect information table. [Figure 12] FIG. 10 is a diagram illustrating an example of an examination information table. [Figure 13] FIG. 10 is a diagram illustrating an example of input screen related information. [Figure 14] 3A to 3C are diagrams illustrating examples of input screens. [Figure 15] FIG. 10 is a diagram illustrating an example of storage location specification information. [Figure 16] 10 is a flowchart of a storage location specifying information storage process. [Figure 17] 10 is a display example of a storage location display screen. [Figure 18] 10 is a flowchart of a support-side medical information storage process. [Figure 19] 10 is a display example of a transfer candidate medical information display screen. [Figure 20] 10 is a display example of a transfer candidate medical information display screen. [Figure 21] 10 is a flowchart of another support-side medical information storage process. DETAILED DESCRIPTION OF THE INVENTION

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A medical system and a medical program according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0011] [Basic Concept of the Embodiment] First, the basic concept of the embodiment will be described. The embodiment generally relates to a medical system and a medical program.

[0012] Here, the term "medical system" refers to a system related to medical care, and is a concept that includes, for example, a system for supporting the work of medical professionals (e.g., doctors, nurses, CRCs (Clinical Research Coordinators), laboratory technicians, pharmacists, or medical clerks) or other individuals engaged in medical procedures, and is equipped with, for example, a second medical information storage means, an association information storage means, and a processing means. Note that 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 in a general-purpose system (e.g., a personal computer or a server computer). Furthermore, this "medical system" is a concept that includes, for example, a system realized by only one computer, or a system realized by multiple computers (i.e., a cloud computer) that are distributed across multiple locations.

[0013] The "second medical information storage means" is a means for storing medical information about a patient stored in a predetermined first storage location in the first medical information storage means. Note that the "first medical information storage means" is a concept that includes a database (hereinafter, the database may also be referred to as "DB") provided in a different device from the device in which the second medical information storage means is provided.

[0014] The "associated information storage means" is a means for storing associated information. The "associated information" is information that correlates 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 any second storage location in the second medical information storage means, into which medical information stored in the second storage location of the associated second medical information storage means is input, and is an information input field displayed on the display means.

[0015] The "processing means" is a means for performing 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. The "processing related to storing medical information in the second medical information storage means" is a concept that includes, for example, processing to support storing medical information in the second medical information storage means (one example is processing to display medical information that is a candidate for storage in the second medical information storage means), or processing to actually store medical information in the second medical information storage means.

[0016] The "processing means" performs, for example, a first process and a second process. The "first process" is a concept that includes, for example, when a plurality of information input fields are displayed on the display means and at least one of the plurality of information input fields is selected by a user, a process of identifying 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 of displaying medical information stored in the first storage location identified in the first process. In the second process, the "processing means" filters or sorts the medical information stored in the first storage location identified in the first process based on a predetermined criterion and displays it.

[0017] For example, when medical information is newly stored in a first storage location of the first medical information storage means, the "processing means" identifies a second storage location associated with the first storage location based at least 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.

[0018] In the embodiment described below, the case where "processing related to storing medical information in a second medical information storage means" is processing that assists in storing medical information in a second medical information storage means will be explained, and other concepts will be explained in modified examples.

[0019] (composition) First, the configuration of the medical-related system according to this embodiment will be described. Fig. 1 is a block diagram showing the medical-related system according to this embodiment. In reality, the number of electronic medical record information storage devices 2 in the medical-related system 100 is arbitrary, but the following description will focus on those shown in the figure.

[0020] The medical-related system 100 shown in FIG. 1 includes, for example, a terminal device 1, an electronic medical record information storage device 2, and a medical support device 3.

[0021] (Configuration - Terminal Device) Fig. 2 is a block diagram showing a terminal device. The terminal device 1 in Fig. 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, a case where the terminal device is a tablet terminal will be described. As shown in Fig. 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.

[0022] (Configuration - Terminal Device - Communication Unit) The communication unit 11 in FIG. 2 is a communication means for communicating with an external device (for example, the medical support device 3), and can be configured using, for example, a known communication circuit or the like.

[0023] (Configuration - Terminal Device - Touchpad) 2 is an operation means that receives various operation inputs from the user when pressed with the user's finger, etc. The specific configuration of this touchpad 12 is arbitrary, but for example, a known touchpad equipped with an operation position detection means using a resistive film method, a capacitance method, or the like can be used.

[0024] (Configuration - Terminal Device - Display) 2 is a display means for displaying various images under the control of the control unit 15. The specific configuration of the display 13 is arbitrary, and for example, a known flat panel display such as a liquid crystal display or an organic EL display can be used. Note that the touch pad 12 and the display 13 may be superimposed on each other to form an integrated touch panel.

[0025] (Configuration - Terminal Device - Recording Unit) 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 configured using, for example, a flash memory or the like.

[0026] (Configuration - Terminal Device - Control Unit) 1 is a control means for controlling the terminal device 1, and is specifically a computer including a CPU, various programs interpreted and executed on the CPU (including basic control programs such as an OS and application programs that are started on the OS and realize specific functions), and an internal memory such as RAM for storing programs and various data (the same applies to control units of other devices). In particular, the program according to the embodiment is installed in the terminal device 1 via an arbitrary recording medium or a network, thereby substantially configuring each unit of the control unit 15 (the same applies to control units of other devices). The processing performed by the control unit 15 will be described later.

[0027] (Configuration - Electronic medical record information storage device) 1 is a device that stores various information related to medical care, and will be described as being configured as a so-called DWH (Data Ware House) 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.

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

[0029] (Configuration - Electronic medical record information storage device - Recording unit) 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. This known recording device may be, 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 a Blu-ray disc, an electrical recording medium such as Flash, ROM, USB memory, or an SD card, or any other recording medium (the same applies to the medical support device 3 described later).

[0030] The recording unit 22 includes, for example, a medical record-side medical information DB 221.

[0031] (Configuration - Electronic medical record information storage device - Recording unit - Medical record side medical information DB) The medical record medical information DB221 in FIG. 1 is the first medical information storage means described above, and specifically, is a medical record medical information storage means for storing medical record medical information. "Medical record medical information" refers to medical information related to medical care, and in this embodiment, a case will be described in which the medical information includes various information related to cancer, which is a disease. FIG. 3 is a diagram illustrating a medical record patient information table, FIG. 4 is a diagram illustrating a medical record test information table, and FIG. 5 is a diagram illustrating a medical record prescription history detailed information table. The "medical record medical information" in the medical record medical information DB221 in FIG. 1 includes, for example, the medical record patient information table T91 in FIG. 3, the medical record test information table T92 in FIG. 4, and the medical record prescription history detailed information table T93 in FIG. 5. Note that, in reality, the "medical record medical information" actually includes many tables (e.g., tens to hundreds or more) in addition to the tables shown in the figure, but in this embodiment, the tables shown in the figure will be used as a representative example. The term "table" may be interpreted as a concept indicating, for example, multiple types of information that are associated with each other.

[0032] (Configuration - Electronic medical record information storage device - Recording unit - Medical record side medical information DB - Medical record side patient information table) The medical record patient information table T91 in Fig. 3 is a table showing information about patients. In the medical record patient information table T91, as shown in Fig. 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 mutually associated.

[0033] Information corresponding to the item "Patient ID" is a patient ID for uniquely identifying a patient (e.g., "IDp1" in Figure 3). Information corresponding to the item "Patient Name" is information indicating the patient's name (e.g., "AA" in Figure 3). Information corresponding to the item "Gender" is information indicating the patient's gender (e.g., "Male" in Figure 3). Information corresponding to the item "Date of Birth" is information indicating the patient's date of birth (e.g., "1960 / 1 / 1" indicating January 1, 1960 in Figure 3). Information corresponding to the item "Update Date" is information indicating the date on which each of the above-mentioned information was stored or updated (e.g., "2020 / 6 / 20" indicating June 20, 2020 in Figure 3).

[0034] Note that the information specifically illustrated in each table is described for the convenience of explanation (the same applies to the information specifically illustrated in each figure other than each table).

[0035] For example, the information at the top of such a medical record-side patient information table T91 (information combining "IDp1," "AA," "male," "1 / 1 / 1960," and "6 / 2020") indicates that the patient ID of a patient whose name is "AA" is "IDp1," that the patient's gender and date of birth are "male" and the date indicated by "1 / 1 / 1960," and that the date on which each piece of information was stored or updated is the date indicated by "6 / 20 / 2020."

[0036] The specific storage method for this medical record side patient information table T91 is arbitrary, but for example, when a medical professional or other person in charge of information input uses any method (for example, a method of inputting information via their own computer, or an input means of an electronic medical record device (not shown, but known) (keyboard, mouse, etc.)) to input information into an electronic medical record device (not shown, but known), the electronic medical record device records the information itself, and this recorded information is sent to the electronic medical record information storage device 2, and the control unit 23 of the electronic medical record information storage device 2 stores the information based on this sent information (the same applies to the medical record side test information table T92 and the medical record side prescription history detailed information table T93 described below).

[0037] (Configuration - Electronic medical record information storage device - Recording unit - Medical record side medical information DB - Medical record side examination information table) The medical record test information table T92 in Fig. 4 is a table showing information about tests performed on patients. In the medical record test information table T92, as shown in Fig. 4, for example, information corresponding to the item "Test result ID," information corresponding to the item "Patient ID," information corresponding to the item "Test code," information corresponding to the item "Test item name," information corresponding to the item "Test value," information corresponding to the item "Test date," and information corresponding to the item "Update date" are mutually associated. 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 names in Fig. 3 (the same applies to the information with the same names in Fig. 5, which will be described later).

[0038] Information corresponding to the item "Test Result ID" is a test result ID that uniquely identifies information such as the results of a test performed on a patient (e.g., "IDct1" in FIG. 4). Information corresponding to the item "Test Code" is information indicating various codes related to a test performed or to be performed on a patient. Note that the various codes here are arbitrary, and for example, a JLAC10 code, analyte code, identification code, material code, measurement code, result identification code, or test item original code can be used. For convenience of explanation, in FIG. 4, "CODt1" is stored as information corresponding to the item "Test Code." Information corresponding to the item "Test Item Name" is information indicating the name of the test item performed or to be performed on a patient (e.g., "KRAS" in FIG. 4). Information corresponding to the item "Test Value" is information indicating the test value that is the result of a test performed on a patient (e.g., "D1" in FIG. 4). Information corresponding to the item "Test Date" is information indicating the date on which the test was performed on a patient (e.g., "2020 / 6 / 20" in FIG. 4).

[0039] For example, the information at the top of such a medical record side test information table T92 (information combining "IDct1", "IDp1", "CODt1", "KRAS", "D1", "2020 / 6 / 20", and "2020 / 6 / 20") indicates that the code, name of the test item, test value, and test date related to the test performed on the patient identified by "IDp1" are the dates indicated by "CODt1", "KRAS", "D1", and "2020 / 6 / 20", that the test result ID is "IDct1", and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 6 / 20".

[0040] (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 detailed information table T93 in Fig. 5 is a table showing information about drugs prescribed for treatment to patients. In the medical record prescription history detailed information table T93, as shown in Fig. 5, for example, information corresponding to the item "prescription history ID," information corresponding to the item "patient ID," information corresponding to the item "drug code," information corresponding to the item "drug name," information corresponding to the item "dose," 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 mutually associated.

[0041] The information corresponding to the item "Prescription History ID" is a prescription history ID for uniquely identifying information about drugs prescribed to a patient for treatment (e.g., "IDcp1" in FIG. 5). The information corresponding to the item "Drug Code" is information indicating various codes related to drugs. Note that the various codes here are arbitrary, and HOT codes, drug source codes, etc. can be used. In FIG. 5, for convenience of explanation, "CODm1" is stored as information corresponding to the item "Drug Code". The information corresponding to the item "Drug Name" is information indicating the name of the drug used to treat the patient's illness (e.g., "A1 Drug" in FIG. 5). The information corresponding to the item "Dose" is information indicating the drug dosage (e.g., "28" indicating 28 tablets in FIG. 5). The information corresponding to the item "Unit" is information indicating the amount of drug to be administered orally at one time (e.g., "1" indicating 1 tablet in FIG. 5). The information corresponding to the item "Number of Days" is information indicating the number of days for which the prescribed drug should be administered (e.g., "14" indicating 14 days in FIG. 5). The information corresponding to the item "prescription date" is information indicating the date on which the drug was prescribed to the patient (e.g., "2020 / 7 / 1" in FIG. 5).

[0042] For example, the information at the top of such a medical record side prescription history detailed information table T93 (information combining "IDcp1", "IDp1", "CODm1", "A1 drug", "28", "1", "14", "2020 / 7 / 1", and "2020 / 7 / 1") indicates that, for example, the code, drug name, dose, unit, number of days, and prescription date for the drug prescribed for treatment to the patient identified by "IDp1" are the dates indicated by "CODm1", "A1 drug", "28", "1", "14", and "2020 / 7 / 1", and also indicates that the prescription history ID is "IDcp1", and also indicates that the date on which each piece of information was stored or updated is the date indicated by "2020 / 7 / 1".

[0043] 3 to 5 and the items in each table may be interpreted as corresponding to a predetermined "first storage location" of medical information in the chart side medical information DB 221. In the example shown in FIG.

[0044] (Configuration - Electronic medical record information storage device - Control unit) 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.

[0045] (Configuration - Medical Support Device) The medical support device 3 in FIG. 1 is the above-mentioned medical system, and includes, for example, a communication unit 31, a recording unit 32, and a control unit 33.

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

[0047] (Configuration - Medical Support Device - Recording Unit) The recording unit 32 in FIG. 1 is a recording means for recording programs and various data required for the operation of the medical support device 3, and is configured using, for example, a known recording device.

[0048] The recording unit 32 includes, for example, a support side medical information DB 321, an input screen related information DB 322, and a storage location specifying information DB 323.

[0049] (Configuration - Medical support device - Recording unit - Support side medical information DB) The support-side medical information DB321 in FIG. 1 is the second medical information storage means described above, and more specifically, 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, a case will be described in which the medical information includes various information related to cancer, which is a disease. FIG. 6 is a diagram illustrating various tables stored as support-side medical information. For example, as shown in FIG. 6, the support-side medical information DB321 in FIG. 1 stores, as support-side medical information, a patient information table T1, an episode information table T2, a treatment information table T3, an effect assessment information table T4, a side effect information table T5, and an examination information table T6.

[0050] (Configuration - Medical support device - Recording unit - Support side medical information DB - Patient information table) The patient information table T1 in Fig. 6 is a table showing information about patients. Fig. 7 is a diagram showing an example of the patient information table. In the patient information table T1, as shown in Fig. 7, for example, the same information as that in the medical record-side patient information table T91 in Fig. 3 is mutually associated.

[0051] The specific method for storing this patient information table T1 is arbitrary, but for example, when each piece of information in the medical record 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, and the same information as the each piece of information in the medical record patient information table T91 may be stored, or when a user (such as a medical professional) uses any method (such as a method of inputting information via their own terminal device 1, or an input means of the medical support device 3 (such as a keyboard or mouse)), the same information as the each piece of information in the medical record patient information table T91 may be input into the medical support device 3, and the control unit 33 of the medical support device 3 may store the information based on the input information. Specific storage methods for each of the other tables will be described later.

[0052] (Configuration - Medical support device - Recording unit - Support side medical information DB - Episode information table) Episode information table T2 in FIG. 6 is a table showing information about the state of a patient's illness (cancer in this embodiment). FIG. 8 is a diagram showing an example of an episode information table. In episode information table T2, as shown in FIG. 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 mutually associated. 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 of the same names in FIG. 7.

[0053] The information corresponding to the item "episode ID" is an episode ID that uniquely identifies an episode (e.g., "IDse1" in FIG. 8). Note that the information corresponding to this "episode ID" is information used to identify the progress of treatment for a disease, and in this embodiment, it is information used to identify the progress of treatment for cancer, which is a disease whose condition can change over time as it progresses or recovers, and is also information that uniquely identifies, for example, the state of cancer. In other words, in this embodiment, "episode" may be interpreted as corresponding to "cancer state."

[0054] Information corresponding to the item "cancer type classification" is information indicating the classification of cancer type (in Figure 8, this is a classification of cancer type based on the location where the cancer is localized (present), such as "gastric cancer" and, although not shown, "lung cancer"). Information corresponding to the item "cancer tissue" is information indicating the histological type of cancer (in Figure 8, "tubular adenocarcinoma" etc.). Information corresponding to the item "cancer differentiation level" is information indicating the differentiation level of cancer (in Figure 8, "poorly differentiated" etc.). Information corresponding to the item "cancer location" is information indicating the location where the cancer is localized (present) (in Figure 8, "stomach / cardia" etc.). The information corresponding to the item "TNM classification" is information indicating a cancer-related index for determining the degree of cancer progression, and may be determined according to any standard including, for example, the UICC (Unio Internationalis Contra Cancrum) criteria or other standards, including, for example, information on the size and infiltration of the cancer as a T factor, information on lymph node metastasis of the cancer as an N factor, and information on distant metastasis of the cancer as an M factor (e.g., "T=1, N=1, M=0" for gastric cancer, specifying that the T factor is "1", the N factor is "1", and the M factor is "0"). The information corresponding to the item "stage" is information indicating the stage of the cancer as the degree of progression, and may be determined according to any standard including, for example, the UICC criteria or other standards (e.g., "1A" indicating stage 1A in FIG. 8).

[0055] For example, the information at the top of such an episode information table T3 (information combining "IDse1", "IDp1", "gastric cancer", "tubular adenocarcinoma", "poorly differentiated", "stomach / cardia", "T=1, N=1, M=0", "1A", and "2020 / 7 / 1") indicates that the cancer type classification, cancer tissue, cancer differentiation level, cancer localization site, TNM classification, and stage of the patient identified by "IDp1" are "gastric cancer", "tubular adenocarcinoma", "poorly differentiated", "stomach / cardia", "T=1, N=1, M=0", and "1A", and also indicates that the episode ID is "IDse1", and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 7 / 1".

[0056] Furthermore, since episode information table T2 includes information corresponding to the item "patient ID," it is possible to associate a large number of episode information tables T2 with patient information table T1 for one patient, as shown in FIG.

[0057] (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 showing information related to the treatment of a patient's illness. Figure 9 is a diagram showing an example of a treatment information table. In the treatment information table T3, as shown in Figure 9, for example, information corresponding to the item "treatment information ID", information corresponding to the item "episode ID", information corresponding to the item "patient ID", information corresponding to the item "drug name", information corresponding to the item "prescription date", and information corresponding to the item "update date" are mutually associated. Note that the information corresponding to the item "episode ID", information corresponding to the item "patient ID", and information corresponding to the item "update date" are the same as the information with the same names in Figure 8 (the same applies to the information with the same names in Figure 12, which will be described later).

[0058] Information corresponding to the item "Treatment Information ID" is a treatment information ID for uniquely identifying information regarding the treatment of the patient's illness (e.g., "IDsm1" in Figure 9). Information corresponding to the item "Drug Name" is information indicating the name of the drug used to treat the patient's illness (e.g., "A1 Drug" in Figure 9). Information corresponding to the item "Prescription Date" is information indicating the date the drug was prescribed to the patient (e.g., "2020 / 7 / 1" in Figure 9).

[0059] For example, the information in the top row of such a treatment information table T4 (information combining "IDsm1," "IDse1," "IDp1," "A1 drug," "2020 / 7 / 1," and "2020 / 7 / 1") indicates that, for example, "A1 drug" was prescribed on the date indicated by "2020 / 7 / 1" for the patient (patient identified by "IDp1") in the episode identified by "IDse1," that the treatment information ID is "IDsm1," and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 7 / 1."

[0060] Furthermore, since the treatment information table T3 contains information corresponding to the items "episode ID" and "patient ID," it is possible to associate multiple treatment information tables T3 with an episode information table T2 that indicates one episode for one patient, as shown in Figure 6 (the same applies to the examination information table T6 described below).

[0061] (Configuration - Medical support device - Recording unit - Support side medical information DB - Effect assessment information table) The effect assessment information table T4 in FIG. 6 is a table showing information about the effects of treatments administered to patients. FIG. 10 is a diagram illustrating an example of the effect assessment information table. In the effect assessment information table T4, as shown in FIG. 10, for example, information corresponding to the item "effect assessment 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 "effect assessment result," information corresponding to the item "effect assessment date," and information corresponding to the item "update date" are mutually associated. Note that the information corresponding to the item "episode ID," information corresponding to the item "patient ID," information corresponding to the item "treatment information ID," and information corresponding to the item "update date" is the same as the information with the same names in FIG. 9 (the same applies to the information with the same names in FIG. 11, which will be described later).

[0062] Information corresponding to the item "Effectiveness Assessment Information ID" is an effectiveness assessment information ID that uniquely identifies information regarding the effectiveness of the treatment administered to the patient (e.g., "IDsj1" in Figure 10). Information corresponding to the item "Effectiveness Assessment Result" is information indicating the assessment result of the effectiveness of the treatment administered to the patient (e.g., "Progression" in Figure 10, indicating that the treatment was relatively small and the cancer progressed, and "Success" indicating that the treatment was relatively large and the cancer progression was stopped or the cancer shrank). Information corresponding to the item "Effectiveness Assessment Date" is information indicating the date on which the assessment of the treatment administered to the patient was made (e.g., "2020 / 8 / 15" in Figure 9).

[0063] For example, the information in the top row of such an effectiveness assessment information table T5 (information combining "IDsj1," "IDse1," "IDp1," "IDsm1," "progression," "2020 / 8 / 15," and "2020 / 8 / 15") indicates that the effect assessed for the treatment indicated by "IDsm1" administered to the patient (patient identified by "IDp1") whose episode is identified by "IDse1" is "progression," that the date on which the assessment was made is the date indicated by "2020 / 8 / 15," that the effectiveness assessment information ID is "IDsj1," and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 8 / 15."

[0064] Furthermore, since the effectiveness assessment information table T4 contains information corresponding to the items "episode ID," "patient ID," and "treatment information ID," it is possible to associate multiple effectiveness assessment information tables T4 with a treatment information table T3 relating to the treatment of one episode of one patient, as shown in Figure 6 (the same applies to the side effect information table T5 described below).

[0065] (Configuration - Medical support device - Recording unit - Support side medical information DB - Side effect information table) The side effect information table T5 in Fig. 6 is a table showing information about side effects of treatments administered to patients. Fig. 11 is a diagram illustrating an example of the side effect information table. In the side effect information table T5, as shown in Fig. 11, for example, information corresponding to the item "side effect 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 "side effect name," information corresponding to the item "grade," information corresponding to the item "side effect onset date," information corresponding to the item "side effect resolution date," and information corresponding to the item "update date" are mutually associated.

[0066] Information corresponding to the item "Side effect information ID" is a side effect information ID that uniquely identifies information about the side effects of the treatment administered to the patient (e.g., "IDss1" in Figure 11). Information corresponding to the item "Side effect name" is information indicating the name of the side effect that occurred (e.g., "vomiting" in Figure 11). Information corresponding to the item "Grade" is information indicating the severity of the side effect that occurred (e.g., in Figure 11, the severity of the side effect is divided into a predetermined number of stages, and the stage that the side effect falls into is indicated numerically, e.g., "2"). Information corresponding to the item "Side effect onset date" is information indicating the date on which the side effect occurred (e.g., "2020 / 7 / 12" in Figure 11). Information corresponding to the item "Side effect resolution date" is information indicating the date on which the side effect resolved (e.g., "2020 / 7 / 15" in Figure 11).

[0067] For example, with regard to the information in the top row of such side effect information table T6 (information consisting of the combination of "IDss1", "IDse1", "IDp1", "IDsm1", "vomiting", "2", "2020 / 7 / 12", "2020 / 7 / 15", and "2020 / 7 / 20"), it is shown that the side effect name, grade, date of onset of side effect, and date of resolution of side effect for the treatment indicated by "IDsm1" performed on the patient (patient identified by "IDp1") who is the subject of the episode identified by "IDse1" are the dates indicated by "vomiting", "2", and "2020 / 7 / 12", and the date indicated by "2020 / 7 / 15", and it is also shown that the side effect information ID is "IDss1", and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 7 / 20".

[0068] (Configuration - Medical support device - Recording unit - Support side medical information DB - Examination information table) The test information table T6 in Fig. 6 is a table showing information about tests performed on patients. Fig. 12 is a diagram showing an example of the test information table. In the test information table T6, as shown in Fig. 12, for example, information corresponding to the item "test information ID," information corresponding to the item "episode ID," information corresponding to the item "patient ID," information corresponding to the item "test item name," information corresponding to the item "test value," information corresponding to the item "test date," and information corresponding to the item "update date" are mutually associated.

[0069] Information corresponding to the item "Test Information ID" is a test information ID that uniquely identifies information regarding a test performed on a patient (e.g., "IDst1" in Figure 12). Information corresponding to the item "Test Item Name" is information indicating the name of the test item that has been performed or will be performed on a patient (e.g., "KRAS" in Figure 12). Information corresponding to the item "Test Value" is information indicating the test value that is the result of a test performed on a patient (e.g., "D1" in Figure 12). Information corresponding to the item "Test Date" is information indicating the date on which the test was performed on a patient (e.g., "2020 / 6 / 20" in Figure 11).

[0070] For example, the information in the top row of such a test information table T6 (information combining "IDst1", "IDse1", "IDp1", "KRAS", "D1", "2020 / 6 / 20", and "2020 / 6 / 20") indicates that the names of the test items, test values, and test dates performed on the patient (patient identified by "IDp1") who is the subject of the episode identified by "IDse1" are the dates indicated by "KRAS", "D1", and "2020 / 6 / 20", and that the test information ID is "IDst1", and that the date on which each piece of information was stored or updated is the date indicated by "2020 / 6 / 20".

[0071] 7 to 12 and the items in each table may be interpreted as corresponding to a predetermined "second storage location" of medical information in the support-side medical information DB 321. In the example shown in FIG.

[0072] (Configuration - Medical support device - Recording unit - Input screen related information DB) The input screen related information DB 322 in FIG. 1 is an input screen related information storage means for storing input screen related information. "Input screen related information" is information related to various input screens for a user to input medical information into the medical support device 3. FIG. 13 is a diagram illustrating the input screen related information, and FIG. 14 is a diagram illustrating each input screen. Note that in each input screen in FIG. 14, elements other than the characteristic parts of the present application are omitted as appropriate.

[0073] ===Input screen=== First, the input screen will be described. The "input screen" is a screen for storing medical information in the support-side medical information DB 321, and is, for example, 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 side. The "input screen" includes, for example, a patient information input screen, an episode information input screen, a treatment information input screen, an efficacy assessment information input screen, a side effect information input screen, and an examination information input screen, as shown in FIG. 14. Note that each of these input screens may be configured to be switched by performing a predetermined operation on the terminal device 1 side using any technology (for example, a technology for switching screens using tabs).

[0074] =Patient information entry screen= The "patient information input screen" is a screen for inputting each piece of information in the patient information table T1 in Fig. 7, and is a screen on which input fields P11 to P12, for example, are displayed. Each input field is a field for inputting and storing information corresponding to the name of the information displayed to the left of the input field on the input screen (i.e., information corresponding to each item in each table in Figs. 7 to 12), and is also a field that can display each piece of information as appropriate (the same applies to the input fields on each of the other screens). The input fields P11 to P12, for example, are fields for inputting information corresponding to the items "patient name" and "gender" in Fig. 7, and are fields to which, for example, "ID11" to "ID12" and the like are associated as input field IDs for uniquely identifying each field.

[0075] =Episode information input screen= The "episode information input screen" is a screen for inputting each piece of information in episode information table T2 in Fig. 8, and is a screen that displays, for example, input fields P21 to P22, etc. Input fields P21 to P22, etc. are fields for inputting, for example, information corresponding to the item "cancer type classification" and the item "cancer tissue" in Fig. 8, and are fields to which, for example, "ID21" to "ID22" etc. are associated as input field IDs for uniquely identifying each field.

[0076] = Treatment information entry screen = The "treatment information input screen" is a screen for inputting each piece of information in the treatment information table T3 in Fig. 9, and is a screen that displays, for example, input fields P31 to P32. The input fields P31 to P32 are fields for inputting information corresponding to, for example, the item "drug name" and the item "prescription date" in Fig. 9, and are fields to which, for example, "ID31" to "ID32" are associated as input field IDs for uniquely identifying each field.

[0077] =Effect assessment information input screen= The "effectiveness assessment information input screen" is a screen for inputting each piece of information in the effectiveness assessment information table T4 in Fig. 10, and is a screen that displays, for example, input fields P41 to P42, etc. The input fields P41 to P42, etc. are fields for inputting information corresponding to, for example, the items "effectiveness assessment result" and "effectiveness assessment date" in Fig. 10, and are fields to which, for example, "ID41" to "ID42" are associated as input field IDs for uniquely identifying each field.

[0078] =Side effect information entry screen= The "side effect information input screen" is a screen for inputting each piece of information in the side effect information table T5 in Fig. 11, and is a screen that displays, for example, input fields P51 to P52, etc. The input fields P51 to P52, etc. are fields for inputting, for example, information corresponding to the item "side effect name" and the item "grade" in Fig. 11, and are fields to which, for example, "ID51" to "ID52", etc. are associated as input field IDs for uniquely identifying each field.

[0079] = Test information input screen = The "test information input screen" is a screen for inputting each piece of information in the test information table T6 of FIG. 12. In this embodiment, "KRAS" and "NRAS" are predefined as candidate test items to be performed on a patient, and a case will be described as an example in which an examination of any one of these candidate test items is performed. The "test information input screen" of FIG. 14 is a screen that displays, for example, input fields P61 to P64. The input fields P61 to P62 are fields for inputting information corresponding to the item "test value" associated with the item "test item name" = "KRAS" in FIG. 12 and information corresponding to the item "examination date," for example, and are associated with "ID61" to "ID62" as input field IDs. The input fields P63 to P64 are fields for inputting information corresponding to the item "test value" associated with the item "test item name" = "NRAS" in FIG. 12 and information corresponding to the item "examination date," for example, and are associated with "ID63" to "ID64" as input field IDs.

[0080] ===Input screen related information=== Next, the input screen related information will be described. In the input screen related information in Fig. 13, for example, information corresponding to the item "input screen", information corresponding to the item "input field ID", information corresponding to the item "table" of the item "medical information", and information corresponding to the item "information" of the item "medical information" are mutually associated.

[0081] Information corresponding to the item "input screen" is information indicating each of the input screens described above (e.g., "patient information" indicating the patient information input screen in FIG. 13). Information corresponding to the item "input field ID" is the input field ID described above. Information corresponding to the item "table" of the item "medical information" is information indicating each of the tables shown in FIGS. 7 to 12. Any information can be used as the information indicating each table, but an example will be described in which table name information indicating the name of the table is used. In FIG. 13, information corresponding to the item "table" of the item "medical information" is exemplified by "patient information," which is the table name information of the patient information table T1 in FIG. 7.

[0082] The information corresponding to the item "information" is information indicating the type of specific information included in each table (i.e., information indicating each item included in each table). Any information can be used as the information indicating each item, but for example, a case where item name information indicating the name of an item is used will be described. In FIG. 13, the information corresponding to the item "information" of the item "medical information" is exemplified by "patient name," which is the item name information of the item "patient name" in FIG. 7. Note that the item "information" = "lab value (KRAS)" in FIG. 13 indicates the item "lab value" associated with the item "lab item name" = "KRAS" in FIG. 12 (i.e., "lab value," which is the item name information associated with the item "lab item name" = "KRAS" in FIG. 12). Similarly, the item "information" = "examination date (KRAS)" in FIG. 13 indicates the item "examination date" associated with the item "lab item name" = "KRAS" in FIG. 12. Similarly, the items "Information" = "Test Value (NRAS)" and "Test Date (NRAS)" in Figure 13 indicate the items "Test Value" and "Test Date" associated with the item "Test Item Name" = "NRAS" in Figure 12.

[0083] For example, with regard to the information at the top of such input screen-related information (information combining "Patient Information," "ID11," "Patient Information," and "Patient Name"), for example, the patient information input screen (Fig. 14) indicated by "Patient Information" displays an input field P11 (Fig. 14) identified by "ID11," and it is shown that the input field P11 identified by "ID11" is associated with the item "Patient Name" in Fig. 7 indicated by "Patient Name" in the patient information table T1 (Fig. 7) indicated by "Patient Information." Note that for the sake of convenience, some input field IDs in Fig. 13 are shown as "..." and specific information is omitted.

[0084] The specific method for storing such input screen related information is arbitrary, but for example, when information regarding the input screen related information is input to the medical support device 3 by any method (for example, a method in which the administrator accesses the medical support device 3 using his / her own terminal device and inputs the information, or a method in which the administrator inputs the information using an input means (keyboard, mouse, etc.) of the medical support device 3 not shown), the control unit 33 may store the information based on the input information.

[0085] (Configuration - Medical support device - Recording unit - Storage location identification information DB) The storage location identification information DB323 in FIG. 1 is the aforementioned association information storage means, specifically, storage location identification information storage means that stores storage location identification information. "Storage location identification information" is the aforementioned association information, specifically, information that correlates information indicating at least one or more input fields on each input screen with information indicating a predetermined storage location (i.e., first storage location) of medical information in the medical record medical information DB221. FIG. 15 is a diagram illustrating an example of storage location identification information. In the storage location identification information in FIG. 15, for example, information corresponding to the item "input field ID" and information corresponding to the item "medical record storage location information" are correlated with each other. Note that the information corresponding to the item "input field ID" is the same as the information of the same name in FIG. 13.

[0086] The information corresponding to the item "medical record storage location information" is information indicating a predetermined storage location of medical information in the medical record medical information DB 221. Any information can be used as the information for this item "medical record storage location information," for example, so-called schema information can be used. In this embodiment, an example is given in which information similar to the information indicated in the items "table" and "information" of the item "medical information" in FIG. 13 is used. That is, a case is described in which the information for the item "medical record storage location information" is a combination of information indicating each table in the medical record medical information DB 221 shown in FIGS. 3 to 5 (for example, table name information indicating the name of the table) and information indicating the type of specific information included in each table (i.e., information indicating each item included in each table (for example, item name information indicating the name of the item)). Fig. 15 illustrates an example of "medical record prescription history detailed information-drug name" which indicates a combination of "medical record prescription history detailed information," which is the table name information of the medical record prescription history detailed information table T93 in Fig. 5, and "drug name," which is the item name information of the item "drug name" of the table. Fig. 15 also illustrates an example of "medical record test information-laboratory value (KRAS)," which indicates a combination of "medical record test information," which is the table name information of the medical record test information table T92 in Fig. 4, and "laboratory value (KRAS)," which is the item name information of the item "laboratory value" associated with the item "laboratory item name" = "KRAS" of the table.

[0087] For example, the information at the top of such storage location specifying information (information combining "ID31" and "medical record prescription history detailed information-drug name") indicates that, for example, the input field P31 (FIG. 14) identified by "ID11" and the storage location indicated by "medical record prescription history detailed information-drug name" (i.e., the item "drug name" in the medical record prescription history detailed information table T93 in FIG. 5) are mutually associated. Note that the specific method for storing such storage location specifying information is arbitrary, but it is stored, for example, by executing the storage location specifying information storage process described below.

[0088] (Configuration - Medical support device - Control unit) 1 is a control means for controlling the medical support device 3, and functionally includes, for example, a processing unit 331. The processing unit 331 is a processing means for performing 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 unit of the control unit 33 will be described later.

[0089] (process) Next, the storage location identification information storage process and the support side medical information storage process executed by the medical care-related system 100 configured as above will be described.

[0090] Here, as described above, an example will be explained in which the information shown in FIG. 7 has already been stored in the patient information table T1.

[0091] (Processing - Storage location specific information storage processing) First, the storage location identification information storage process will be described. Fig. 16 is a flowchart of the storage location identification information storage process (in the following description of each process, steps will be abbreviated as "S"). The "storage location identification information storage process" is generally a process executed by the medical support device 3, and specifically, a process of storing storage location identification information.

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

[0093] ===SA1=== 16, the processing unit 331 of the medical support device 3 displays each input screen. Specifically, although any method is possible, for example, the processing unit 331 generates input screen information for displaying the 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. In detail, with reference to the input screen-related information in FIG. 13, the processing unit 331 generates input screen information for displaying an input screen indicated by the information of the item "input screen" and including an input field identified by the information of the item "input field ID" associated with the information of the item "input screen", and transmits the generated input screen information 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 the input screen on the display 13 based on the received input screen information.

[0094] Here, for example, by referring to the input screen related information in Fig. 13, input screen information for displaying each input screen in Fig. 14 such as the patient information input screen indicated by the item "input screen" = "patient information" etc. (patient information input screen including input fields P11 and P12 etc. identified by the item "input field ID" = "ID11" and "ID12" etc.) is generated 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 Fig. 14 on the display 13 based on the received input screen information.

[0095] ===SA2=== 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. While specific details are arbitrary, for example, the processing unit 331 of the medical support device 3 transmits a table name etc. request signal (a signal for requesting table name information and item name information) to the electronic medical record information storage device 2. Meanwhile, when the control unit 23 of the electronic medical record information storage device 2 receives the table name etc. request signal, it acquires table name information of tables stored in its own medical record side medical information DB 221 and item name information indicating the items included in the tables, and transmits the acquired table name information and item name information to the medical support device 3. Note that, for example, table name information and item name information for all tables included in the medical record side medical information DB 221 are transmitted, and each piece of information is transmitted in an arbitrary format that enables it to understand which items are included in each table so that the data structure of each table can be understood. On the other hand, the processing unit 331 of the medical support device 3 receives and acquires the table name information and item name information transmitted from the electronic medical record information storage device 2.

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

[0097] As an example, for the medical record prescription history detailed information table T93 in Fig. 5, "table name information" = "medical record prescription history detailed information" and "item name information" = "prescription history ID", "patient ID", "drug code", "drug name", "dosage", "unit", "number of days", "prescription date", and "update date" are acquired, and this acquired information is transmitted. Note that the same applies to the medical record patient information table T91 in Fig. 3.

[0098] Furthermore, for the medical record side test information table T92 in Fig. 4, "table name information" = "medical record side test information" is acquired, and for the item name information, the items "test code", "test item name", "test value", "test date", and "update date" in Fig. 4 are acquired as information associated with the information in the item "test item name" (i.e., "KRAS", "NRAS", etc.). Note that the item "test item name" itself is associated with other items as the specific information mentioned above, so it will not be acquired here. That is, for the medical record test information table T92 in FIG. 4, the processing unit 331 acquires the "table name information" = "medical record test information" (described above) and the "item name information" = "test result ID," "patient ID," "test code (KRAS)," "test code (NRAS)," ..., "test value (KRAS)," "test value (NRAS)," ..., "test date (KRAS)," "test date (NRAS)," ..., and "update date (KRAS)," "update date (NRAS)," etc., and transmits this acquired information. Note that "test value (KRAS)" here indicates the item "test value" associated with the item "test item name" = "KRAS" in FIG. 4, as described in FIG. 15. The same applies to other "test value (NRAS)," etc. The processing unit 331 of the medical support device 3 receives and acquires this transmitted table name information and item name information.

[0099] ===SA3=== 16, the processing unit 331 of the medical support device 3 displays a storage location display screen. FIG. 17 is a display example of the storage location display screen. The "storage location display screen" is a screen for displaying the table name information and item name information acquired in SA2, for example, a screen for displaying the information in a table format, and as shown in FIG. 17, is a screen including a table name information display area R1 (the area at the top of the table) for displaying the table name information, and an item name information display area R2 (the area below the second row in the table) for displaying the item name information. The specific processing of SA3 is arbitrary, but for example, the storage location display screen may be displayed on the display 13 of the terminal device 1 by generating screen information for displaying the storage location display screen that displays the table name information and item name information acquired in SA2 and transmitting the generated screen information to the terminal device 1.

[0100] Here, for example, the storage location display screen of FIG. 17 is displayed on the display 13 of the terminal device 1 by generating and transmitting screen information for displaying the storage location display screen of FIG. 17 based on the table name information and item name information, etc., relating to each table of FIG. 3 to FIG. 5 and the items contained in each table, which are acquired by SA2.

[0101] ===SA4=== 16, the processing unit 331 of the medical support device 3 acquires information on a combination of an input field ID to be correlated with each other, table name information, and item name information. Specifically, although it is arbitrary, for example, each item (FIGS. 7 to 12) of each table of the support-side medical information DB 321 includes an item (hereinafter, "transcription item") to which the same information as the information of each item (FIGS. 3 to 5) of each table of the medical record-side medical information DB 221 should be transcribed and stored (for example, in this embodiment, "drug name" and "prescription date" of the treatment information table T3 of FIG. 9, and the item "lab value" and the item "examination date" of the examination information table T6 of FIG. 12) is to be transcribed and stored, and information on a combination of an input field ID identifying an input field for inputting information of this item and table name information and item name information indicating the table and item of information to be transcribed on the medical record-side medical information DB 221 is acquired.

[0102] In detail, when the user taps via the touchpad 12 to select an input field for inputting information for the "transcription item" in each input screen displayed by SA1, and also taps via the touchpad 12 to select table name information and item name information indicating the table and item in which the information to be transcribed into each item of each table in the support side medical information DB 321 corresponding to the selected input field is stored in the storage location display screen displayed by SA3, the control unit 15 of the terminal device 1 transmits information on the combination of 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 on the combination of the input field ID and the table name information and item name information.

[0103] Here, for example, if the user taps to select input field P31 in Figure 14 and then taps to select "Medical Record Prescription History Detailed Information" and "Drug Name" in Figure 17, the control unit 15 of the terminal device 1 transmits information of the combination of the "Input Field ID" = "ID31" of the selected input field P31 and the selected "Table Name Information" = "Medical Record Prescription History Detailed Information" and "Item Name Information" = "Drug Name" to the medical support device 3, and the processing unit 331 of the medical support device 3 receives and acquires the information of the combination of the transmitted "Input Field ID" = "ID31" and the "Table Name Information" = "Medical Record Prescription History Detailed Information" and "Item Name Information" = "Drug Name". Furthermore, if the user subsequently taps and selects input field P32 in Figure 14, and then taps and selects "Medical record prescription history details information" and "Prescription date" in Figure 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information that is a combination of "Input field ID" = "ID32", "Table name information" = "Medical record prescription history details information", and "Item name information" = "Prescription date".

[0104] 14, and then tap to select "medical record test information" and "test value (KRAS)" in FIG. 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information on the combination of "input field ID" = "ID61", "table name information" = "medical record test information", and "item name information" = "test value (KRAS)". Furthermore, if the input field P62 of FIG. 14 is subsequently tapped to select, and then tap to select "medical record test information" and "test date (KRAS)" in FIG. 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information on the combination of "ID62", "medical record test information", and "test date (KRAS)". 14, and then tap to select "Medical Record Test Information" and "Test Value (NRAS)" in FIG. 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information on the combination of "ID63", "Medical Record Test Information", and "Test Value (NRAS)". Furthermore, if you tap to select input field P64 of FIG. 14, and then tap to select "Medical Record Test Information" and "Test Date (NRAS)" in FIG. 17, the processing unit 331 of the medical support device 3 similarly receives and acquires information on the combination of "ID64", "Medical Record Test Information", and "Test Date (NRAS)".

[0105] ===SA5=== In SA5 of Fig. 16, the processing unit 331 of the medical support device 3 stores storage location identification information. Specifically, although this is optional, for example, in the storage location identification information of Fig. 15, the input field ID of the information combination acquired in SA4 is stored as information of the item "input ID," and the table name information and item name information of the information combination are stored as information of the item "medical record side storage location information."

[0106] Here, for example, based on the "input field ID" = "ID31", "table name information" = "medical record prescription history detailed information", and "item name information" = "drug name" obtained in SA4, the information in the top row of Figure 15 (i.e., item "input field ID" = "ID31" and item "medical record storage location information" = "medical record prescription history detailed information-drug name") is stored. Similarly, based on other combinations of information obtained in SA4, other information specifically shown in Figure 15 is stored. This concludes the explanation of the storage location identification information storage process.

[0107] (Processing - Supporting side medical information storage processing) Next, the support-side medical information storage process will be explained. Fig. 18 is a flowchart of the support-side medical information storage process. The "support-side medical information storage process" is generally a process executed by the electronic medical record information storage device 2 and the medical support device 3, and specifically, a process for storing support-side medical information.

[0108] The timing for executing this support-side medical information storage process is arbitrary, but for example, when a user inputs the name of the patient for whom information is to be stored via the touchpad 12 of their own terminal device 1 and then performs a specified operation (an operation to start the support-side medical information storage process), the control unit 15 of the terminal device 1 transmits patient name information indicating the inputted patient name to the medical support device 3, and 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 started, and the following description begins from the point at which the support-side medical information storage process is started.

[0109] Here, for example, when a user inputs "AA", which is the name of the patient whose information is to be stored, via the touchpad 12 of his / her own terminal device 1 and then performs a predetermined operation (an operation to start the support-side medical information storage process), the control unit 15 of the terminal device 1 sends "patient name information" = "AA" to the medical support device 3, and when the control unit 33 of the medical support device 3 receives "patient name information" = "AA" sent from the terminal device 1, the support-side medical information storage process is started.

[0110] In addition, in this embodiment, for example, since the tables of the support side medical information have the relationship shown in Figure 6, we will explain the case where the information in the table on the left side of the figure is stored appropriately in accordance with medical practice.

[0111] ===SB1=== 18, the processing unit 331 of the medical support device 3 identifies the patient ID of the patient for whom information is to be stored. Specifically, although this is optional, for example, the processing unit 331 acquires the patient name information received when the support-side medical information storage process is started, and refers to the patient information table T1 in Fig. 7 to identify the information in the item "patient ID" associated with the information in the item "patient name" that stores the same information as the acquired patient name information, as the patient ID of the patient for whom information is to be stored.

[0112] Here, for example, the "patient name information" = "AA" received when the support side medical information storage process is started is acquired, and by referring to the patient information table T1 in Figure 7, "IDp1", which is the information in the "patient ID" item associated with the information in the "patient name" item that stores the same information as the acquired "patient name information" = "AA", is identified as the patient ID of the patient whose information is to be stored.

[0113] ===SB2=== 18, the processing unit 331 of the medical support device 3 displays each input screen. Specifically, the processing unit 331 performs the same process as SA1 in FIG.

[0114] Here, for example, each input screen of Fig. 14 is displayed on the display 13. Note that, for the input fields P11 to P12 etc. of the patient information input screen, for the convenience of confirmation when inputting various information, it 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 of Fig. 7, acquire information of the item "patient name" and information of the item "gender" etc. associated with information of the item "patient ID" in which the same information as the patient ID identified in SB1 is stored, and generate input screen information so that each acquired piece of information is displayed in the input fields P11 to P12 etc. corresponding to each piece of information.

[0115] ===SB3=== 18, the processing unit 331 of the medical support device 3 determines whether to display medical information that is stored in the medical record side medical information DB 221 and is a candidate for transcription (hereinafter, "transcription candidate medical information"). Specifically, although this is optional, for example, when storing support side medical information, the user taps and selects each input field in FIG. 14 via the touchpad 12, and performs an operation of inputting medical information to be stored in the selected input field, and determines whether or not an input field corresponding to a "transcription item" (described above) has been selected.

[0116] Specifically, 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. Then, when the processing unit 331 of the medical support device 3 receives the input field ID transmitted from the terminal device 1, it refers to the storage location identification information of FIG. 15 and determines whether the same information as the received input field ID is stored as information for the item "input field ID." If the same information is not stored, it determines that the input field corresponding to the "transcription item" has not been selected, and determines that the "transcription candidate medical information" should not be displayed (NO in SB3), and proceeds to SB7. If the same information is stored, it determines that the input field corresponding to the "transcription item" has been selected, and determines that the "transcription candidate medical information" should be displayed (YES in SB4), and proceeds to SB4.

[0117] Here, for example, when the user taps to select input field P21 in order to input information into input fields P21-P22 on the episode information input screen in Fig. 14, the control unit 15 of the terminal device 1 transmits the "input field ID"="ID21" of the selected input field P21 to the medical support device 3. Then, the processing unit 331 of the medical support device 3 receives the "input field ID"="ID21" transmitted from the terminal device 1, and, with reference to the storage location identification information in Fig. 15, 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 determines not to display the "transfer candidate medical information" (NO in SB3), and proceeds to SB7.

[0118] ===SB7=== 18, the processing unit 331 of the medical support device 3 determines whether or not to store the medical information entered into each input screen. Specifically, although this is optional, for example, when the user performs a predetermined operation (e.g., tapping a record button, not shown) to store information via the touchpad 12, the control unit 15 of the terminal device 1 transmits information on the combination of the medical information entered into the input field and the input field ID identifying the input field into 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 on the combination from the terminal device 1, it determines not to store the medical information (NO in SB7) and proceeds to SB3. If the processing unit 331 has received the information on the combination from the terminal device 1, it determines to store the medical information (YES in SB7) and proceeds to SB8.

[0119] Here, for example, when the user inputs "gastric cancer" and "tubular adenocarcinoma" and the like into input fields P21 to P22 of the episode information input screen of Fig. 14 via the touchpad 12 and taps a record button (not shown), the control unit 15 of the terminal device 1 transmits information on each combination of "gastric cancer" and "ID21", and "tubular adenocarcinoma" and "ID22", and the like, to the medical support device 3. Then, when the processing unit 331 of the medical support device 3 receives the information on each combination, it determines that the medical information should be stored (YES in SB7) and proceeds to SB8.

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

[0121] 13, the table and items in the table to store the medical information received from the terminal device 1 (i.e., the medical information included in the information of each combination received from the terminal device 1) are identified, and the information is stored based on the identification results. In detail, for example, "first process of SB8" to "second process of SB8" are executed for the information of each combination received by SB7.

[0122] =SB8 first process= In "SB8 first processing", by referring to the input screen related information in Figure 13, the information of the item "table" and the information of the item "information" associated with the information of the item "input field ID" in which the same information as the input field ID among the medical information and input field IDs received from the terminal device 1 is stored are identified, and the table indicated by the information of the identified item "table" is identified as the table to be used to store the medical information received from the terminal device 1, and the item indicated by the information of the identified item "information" is identified as the item to be used to store the medical information received from the terminal device 1.

[0123] Here, for example, for "gastric cancer" and "ID21" received from terminal device 1, the item "input field ID" = "ID21" is associated with the item "table" = "episode information" and the item "information" = "carcinoma classification" in the input screen related information in Figure 13, so "episode information table T2" ​​is identified as the table to store the medical information "gastric cancer" received from terminal device 1, and the item "carcinoma classification" is identified as the item to store "gastric cancer". Similarly, for "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".

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

[0125] Here, for example, for medical information entered into each input field of the episode information input screen of FIG. 14, information in the episode information table T2 of FIG. 6 and FIG. 8 is newly stored, so a unique episode ID is generated, and the current date is identified using any method (for example, a method of referencing the timing results of the timing means (timer, etc.) of the medical support device 3), and then in the episode information table T2 of FIG. 8, the generated episode ID, the patient ID identified by SB1, and information indicating the identified date are stored as information in the item "episode ID," information in the item "patient ID," and information in the item "update date," and the medical information received from the terminal device 1 is stored in association with each of the stored information.

[0126] As an example, an "episode ID" = "IDse1" is generated, and then, using any method, "2020 / 7 / 1" is identified as the current date. As shown in the top row of Figure 8, the item "episode ID" = "Dse1", the item "patient ID" = "IDp1" (the patient ID identified by SB1), and the item "update date" = "2020 / 7 / 1" are stored, and the item "cancer type classification" = "gastric cancer", the item "cancer tissue" = "tubular adenocarcinoma", etc. are also stored.

[0127] ===SB3 YES Example===

[0128] 18, for example, in order to input information into input fields P31 to P32 of the treatment information input screen in FIG. 14 at SB3 in FIG. 18, if the user first taps to select 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. Then, the processing unit 331 of the medical support device 3 receives the "input field ID"="ID31" transmitted from the terminal device 1, and, referring to the storage location identification information in FIG. 15, determines that the same information as the received "input field ID"="ID31" is stored as information for the item "input field ID," and therefore determines that the "transfer candidate medical information" should be displayed (YES at SB3), and proceeds to SB4.

[0129] ===SB4=== At SB4 in FIG. 18, the processing unit 331 of the medical support device 3 transmits a transfer candidate medical information request signal (a signal for requesting at least the "transfer candidate medical information") to the electronic medical record information storage device 2. Specifically, although optional, for example, the processing unit 331 acquires the input field ID received at SB3 (i.e., the input field ID of the input field selected by the user by tapping), references the storage location identification information in FIG. 15, acquires information on the "medical record side storage location information" item associated with the information on the "input field ID" item in which the same information as the acquired input field ID is stored, and identifies the table and item indicated by the acquired information on the "medical record side storage location information" item as the storage location associated with the input field selected by the user. Then, the processing unit 331 generates a transfer candidate medical information request signal including information indicating the identified storage location (i.e., the information on the acquired "medical record side storage location information" item) and the patient ID identified at SB1, and transmits the signal to the electronic medical record information storage device 2.

[0130] Here, for example, the "input field ID" = "ID31" received by SB3 is acquired, and the storage location identification information in Figure 15 is referenced to acquire the item "medical record storage location information" = "medical record prescription history detailed information-drug name" associated with the item "input field ID" = "ID31" that stores the same information as the acquired "input field ID" = "ID31." The medical record prescription history detailed information T93 and the item "drug name" in Figure 5 indicated by the acquired item "medical record storage location information" = "medical record prescription history detailed information-drug name" are identified as the storage location associated with the input field selected by the user. Then, a transfer candidate medical information request signal is generated and transmitted to the electronic medical record information storage device 2, including the "medical record prescription history detailed information-drug name," which is information indicating the identified storage location, and the "patient ID" = "IDp1" identified by SB1.

[0131] ===SC1=== 18, the control unit 23 of the electronic medical record information storage device 2 receives the transfer candidate medical information request signal transmitted at SB4. Here, for example, the transfer candidate medical information request signal including "medical record side prescription history detailed information-drug name" and "IDp1" is received.

[0132] ===SC2=== 18, the control unit 23 of the electronic medical record information storage device 2 acquires "medical information candidate for transfer." Specifically, although this is optional, for example, the control unit 23 acquires the information indicating the storage location and the patient ID included in the transfer candidate medical information request signal received in SC1, and 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, as "medical information candidate for transfer," medical information associated with the item "patient ID" in which the same information as the acquired patient ID is stored among the identified medical information.

[0133] <Reference information> In addition, the system may be configured to acquire any information other than ``medical information candidates for transfer''; for example, when there is multiple ``medical information candidates for transfer,'' the system may be configured to also acquire other information (hereinafter ``reference information'') that is predetermined for each table so that the user can visually check and select the appropriate information; in this embodiment, we will explain the case where ``reference information'' is also acquired.

[0134] For example, in the medical record prescription history detailed information table T93 of FIG. 5, when the information in the item "Drug Name" is "Medical Information Candidate for Transfer," the information in the items "Prescription Date" and "Update Date" is set as "Reference Information." Also, when the information in the item "Prescription Date" is "Medical Information Candidate for Transfer," the information in the items "Drug Name" and "Update Date" is set as "Reference Information." Also, for example, in the medical record test information table T92 of FIG. 4, when the item "Test Value" is "Medical Information Candidate for Transfer," the information in the items "Test Date" and "Update Date" is set as "Reference Information." Also, when the item "Test Date" is "Medical Information Candidate for Transfer," the information in the items "Test Value" and "Update Date" is set as "Reference Information." Note that the reference information described here is merely an example. When multiple pieces of "Medical Information Candidate for Transfer" exist, any other information may be set as reference information as long as the user can visually identify and select appropriate information from these multiple pieces of information.

[0135] <Example> Here, for example, Figure 5 specifically illustrates the items "drug name" = "A1 drug" and "B1 drug", but at the time of processing SC2, "B1 drug" has not yet been stored, and in addition to the information at the top of Figure 5, the item "drug name" = "A2 drug" (corresponding item "prescription date" and item "update date" = "2020 / 6 / 22") and the item "drug name" = "A3 drug" (corresponding item "prescription date" and item "update date" = "2020 / 6 / 25") are stored as information associated with the item "patient ID" = "IDp1", which is not shown.

[0136] In this case, the "information indicating the storage location" = "medical record prescription history detailed information - drug name" and "patient ID" = "IDp1" included in the transfer candidate medical information request signal received by SC1 are acquired, and the medical record medical information DB221 is referenced to the medical record prescription history detailed information table T93 in Figure 5 and to identify "Drug A1," "Drug A2" (not shown), and "Drug A3" (not shown), which are medical information for the item "Drug Name." Since the identified "Drug A1," "Drug A2," and "Drug A3" are all associated with the item "Patient ID" = "IDp1," these are acquired as "medical information candidate for transfer." In addition, in this case, the items "Prescription Date" and "Update Date" = "2020 / 7 / 1," "2020 / 6 / 22" (not shown), and "2020 / 6 / 25" (not shown) are acquired as "reference information" for "Drug A1," "Drug A2," and "Drug A3."

[0137] ===SC3=== 18, the control unit 23 of the electronic medical record information storage device 2 transmits a transfer candidate medical information response signal (a signal for transmitting at least the "transfer candidate medical information") to the medical support device 3. Specifically, although this is optional, for example, the control unit 23 may generate a transfer candidate medical information response signal including the "transfer candidate medical information" and "reference information" acquired in SC2 and transmit it to the medical support device 3.

[0138] Here, for example, a transfer candidate medical information response signal is generated including the "transfer candidate medical information" = "A1 drug" etc. and "reference information" = "2020 / 7 / 1" (here, the prescription date and update date are the same) acquired in SC2, and is sent to the medical support device 3.

[0139] ===SB5=== 18, the processing unit 331 of the medical support device 3 receives the transfer candidate medical information response signal transmitted at SC3. Here, for example, the transfer candidate medical information response signal is received, which includes "transfer candidate medical information" = "A1 drug" and the like and "reference information" = "2020 / 7 / 1" (here, the prescription date and update date are the same).

[0140] ===SB6=== At SB6 in FIG. 18, the processing unit 331 of the medical support device 3 displays a transfer candidate medical information display screen. FIG. 19 shows an example of the transfer candidate medical information display screen. The "transfer candidate medical information display screen" is a screen for displaying at least the "transfer candidate medical information" and, optionally, the "reference information." The specific processing of SB6 is arbitrary, but for example, the "transfer candidate medical information" and "reference information" included in the transfer candidate medical information response signal received at SB5 are acquired, and screen information for displaying the transfer candidate medical information display screen is generated based on the acquired "transfer candidate medical information" and "reference information." The generated screen information is sent to the terminal device 1, whereby the generated screen information is displayed on the display 13 of the terminal device 1.

[0141] Here, for example, the "transfer candidate medical information" (e.g., "A1 drug") and the "reference information" (e.g., "2020 / 7 / 1") included in the transfer candidate medical information response signal received by SB5 are acquired, and screen information for displaying the transfer candidate medical information display screen of FIG. 19 is generated based on the acquired information. Specifically, the screen information is generated to display the text "A1 drug" based on the "transfer candidate medical information" (e.g., "A1 drug"), and to display text such as "(prescription date: 2020 / 7 / 1, update date: 2020 / 7 / 1)" following the text "A1 drug" based on the "reference information" (e.g., "2020 / 7 / 1"). Furthermore, the screen information is generated so that each piece of information is sorted (i.e., rearranged) according to a predetermined sorting criterion (a predetermined criterion; in this embodiment, the closer the prescription date (or, in a modified example, the update date) of "transfer candidate medical information" is to the current date, the higher it is displayed on the screen). 19, for example, the screen information may be generated so that each piece of information is displayed by filtering (i.e., narrowing down each piece of information) according to a predetermined filtering criterion (predetermined criterion, for example, a criterion that narrows down to only two pairs of "transfer candidate medical information" and "reference information" whose prescription date (or, in a variant, update date) is close to the current date, and only these two narrowed down combinations of "transfer candidate medical information" and "reference information" are displayed on the screen information).The generated screen information is then transmitted, and the transfer candidate medical information display screen of FIG. 19 is displayed on the display 13 of the terminal device 1, for example.

[0142] With this configuration, for example, a user who taps and selects input field P31 in Fig. 14 can check the "medical information candidates for transfer" displayed on the transfer candidate medical information display screen, select one "medical information candidates for transfer" from this "medical information candidates for transfer" by any method, and input the same medical information as the selected "medical information candidates for transfer" into input field P31 via touchpad 12. In other words, it becomes possible to store the same medical information as the medical information stored on the electronic medical record information storage device 2 side in Fig. 1 on the medical support device 3 side.

[0143] ===Repetitive processing=== 18 described above and these SB3 to SB4, SC1 to SC3, SB5 to SB6, etc. are then appropriately repeated, and when "A1 drug" and "2020 / 7 / 1" are entered into the input fields P31 to P32 of the treatment information input screen in FIG. 14 and a record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information on each combination of "A1 drug" and "ID31", and "2020 / 7 / 1" and "ID32" to the medical support device 3. Then, when the processing unit 331 of the medical support device 3 receives the information on each combination, it determines that the medical information should be stored (YES in SB7) and proceeds to SB8.

[0144] Here, for example, in "First processing of SB8" in Figure 18, in the input screen related information in Figure 13, as in the case described above, "Treatment information table T3" is identified as the table to store "A1 drug" and "2020 / 7 / 1", and the items "Drug name" and "Prescription date" are identified as the items to store "A1 drug" and "2020 / 7 / 1".

[0145] Next, in the "second processing of SB8," the medical information entered into each input field on the treatment information input screen of FIG. 14 is newly stored as information in the treatment information table T3 of FIG. 6 and FIG. 9, so a unique treatment information ID is generated, an episode ID is identified using the method described below, and the current date is identified using any method. Then, in the treatment information table T3 of FIG. 9, the information in the item "treatment information ID," the item "episode ID," the item "patient ID," and the item "update date" are stored as the information in the item "treatment information ID," the information in the item "episode ID," the information in the item "patient ID," and the information indicating the generated treatment information ID, the identified episode ID, the patient ID identified by SB1, and the identified date, and the medical information received from the terminal device 1 is stored in association with each of the stored information.

[0146] Note that any method for identifying an episode ID may be used. For example, information in the "episode ID" item associated with information in the "patient ID" item in which the same information as the patient ID identified in SB1 is stored may be identified by referring to episode information table T2 in Fig. 6. In this case, it is expected that 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 episode information table T2 in Fig. 8 in various cases, such as when the patient's cancer has progressed, when the patient is currently suffering from a cancer different from the cancer the patient previously had, or when the patient is suffering from multiple types of cancer. In such cases, one episode ID may be identified using the following "first method" or "second method."

[0147] The "first method" focuses on the information in the item "update date" in the episode information table T2 of Fig. 8. In this method, for example, if there is a plurality of pieces of information in the item "episode ID" associated with the patient ID identified in SB1 in the episode information table T2, the information in the item "episode ID" that stores information indicating the date closest to the current date is identified as the information in the item "update date" associated with each piece of information in the item "episode ID."

[0148] The "second method" is a method in which the user makes a selection. In this method, for example, when there are multiple pieces of information for the item "episode ID" associated with the patient ID identified by SB1 in the episode information table T2, each piece of information associated with the multiple pieces of information for the "episode ID" items (i.e., the information for each item shown in FIG. 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 the "episode ID" item 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 information for the "episode ID" item.

[0149] As an example, a "treatment information ID" = "IDsm1" is generated, and by referring to the episode information table T2 in Figure 8, an "episode ID" = "IDse1" item associated with the information in the "patient ID" item, which stores the same information as the "patient ID" = "IDp1" identified in SB1, is identified, and "2020 / 7 / 1" is identified as the current date using any method.Then, as shown in the top row of Figure 9, the item "treatment information ID" = "IDsm1", the item "episode ID" = "Dse1", the item "patient ID" = "IDp1" (the patient ID identified in SB1), and the item "update date" = "2020 / 7 / 1" are stored, and the items "drug name" = "A1 drug" and "prescription date" = "2020 / 7 / 1" are also stored.

[0150] ===Storing other tables (effect determination information table)=== 10. Also, for example, when "progress" and "2020 / 8 / 15" are entered in input fields P41 to P42 of the effect assessment information input screen in FIG. 14 and a record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information on 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 on each combination, performs "SB8 first processing" and "SB8 second processing" based on the received combination information, and stores the information in the top row of FIG. 10.

[0151] In particular, in the "second processing of SB8," the information in the effectiveness assessment information table T4 of Figures 6 and 10 is newly stored, so a unique effectiveness assessment information ID is generated, the episode ID is identified in the same manner as described above, the treatment information ID is identified using the method described below, and the current date is identified using any method.Then, in the effectiveness assessment information table T4 of Figure 10, information indicating the generated effectiveness assessment information ID, the identified episode ID, the patient ID identified by SB1, the identified treatment information ID, and the identified date are stored as information in the item "effectiveness assessment information ID," information in the item "episode ID," information in the item "patient ID," information in the item "treatment information ID," and information in the item "update date," and the medical information received from the terminal device 1 is stored in association with each of the stored information.

[0152] The method for identifying the treatment information ID is arbitrary. For example, the treatment information table T3 in Fig. 9 may be referenced to identify information in the "patient ID" item that stores the same information as the patient ID identified in SB1, and information in the "treatment information ID" item associated with the identified episode ID. In this case, in various cases, such as when multiple drugs are administered for treatment, it is assumed that there are multiple treatment information IDs associated with the patient ID identified in SB1 (i.e., the patient ID that identifies the patient whose information is to be stored) and the identified episode ID in the treatment information table T3 in Fig. 9. In this case, similar to the "first method" and "second method" in the case of the episode ID, one treatment information ID may be identified using a method that focuses on information in the "update date" item in the treatment information table T3 in Fig. 9, or a method that allows the user to select.

[0153] ===Storing other tables (side effect information table)=== Furthermore, for example, when "vomit" and "2" are entered into the input fields P51 to P52 of the side effect information input screen of FIG. 14 and a record button (not shown) is tapped, the control unit 15 of the terminal device 1 transmits information on each combination of "vomit" and "ID51," and "2" and "ID52," etc., to the medical support device 3. The processing unit 331 of the medical support device 3 receives the information on each combination, performs "SB8 first processing" and "SB8 second processing" based on the received combination information, and stores the information in the top row of FIG. 11. In this case, as shown in FIG. 6, the side effect information table T5 is associated with the treatment information table T3 in the same manner as the effect determination information table T4 described above, and therefore is stored in the same manner as the effect determination information table T4.

[0154] ===Storing other tables (test information table)=== Fig. 20 is a display example of the transfer candidate medical information display screen. For example, when the user first taps to select input field P61 in order to input information into input fields P61 to P64 of the examination information input screen of Fig. 14, in the same manner as described above, after YES at SB3, SB4, SC1 to SC3, and SB5 of Fig. 18, for example, the transfer candidate medical information display screen of Fig. 20 is displayed on the display 13 at SB6.

[0155] Then, when the user checks this transfer candidate medical information display screen or another transfer candidate medical information display screen that appears when another input field is selected, enters "D3" and "2020 / 7 / 1" into input fields P61-P62 of the test information input screen in FIG. 14 , and taps the record button (not shown), the control unit 15 of the terminal device 1 transmits information on each combination of "D3" and "ID61," and "2020 / 7 / 1" and "ID62," etc., to the medical support device 3. The processing unit 331 of the medical support device 3 receives the information on each combination, performs "SB8 first processing" and "SB8 second processing" based on the received combination information, and stores the information in the third row of FIG. 12 . In particular, "KRAS" is stored as the test item for "D3," which is medical information on the test value, as information on the item "test item name." In this case, as shown in FIG. 6 , the test information table T6 is associated with the episode information table T2 in the same way as the treatment information table T3 described above, and therefore is stored in the same way as the treatment information table T3. This concludes the explanation of the support-side medical information storage process.

[0156] (Effects of the embodiment) Thus, 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 an input field associated with a predetermined storage location (second storage location) of medical information in the support side medical information DB321 and a predetermined storage location (first storage location) of medical information in the medical record side medical information DB221 in a mutually associated manner, thereby enabling medical information to be stored efficiently.

[0157] Furthermore, by displaying the medical information stored in a predetermined storage location for medical information in the medical record side medical information DB221 associated with at least one input field selected by the user, it is possible to quickly and accurately transcribe, for example, the medical information stored in a predetermined storage location for medical information in the medical record side medical information DB221, thereby enabling efficient storage of medical information.

[0158] Furthermore, by filtering or sorting the medical information before displaying it, for example, the visibility of the medical information can be improved, and therefore the medical information can be stored efficiently.

[0159] [Modifications to the embodiment] Although the embodiments of the present invention have been described above, the specific configurations and means of the present invention can be modified and improved as desired within the scope of the technical ideas of the inventions set forth in the claims. Such modifications will be described below.

[0160] (About the problem 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 of the invention and the details of the configuration, and may solve only some of the problems described above or achieve only some of the effects described above.

[0161] (Regarding decentralization and integration) Furthermore, the above-described configuration is a functional concept and does not necessarily have to be physically configured as illustrated. In other words, the specific form of distribution or integration of each part is not limited to that illustrated, and all or part of it can be functionally or physically distributed or integrated in any unit. In this application, the term "system" is not limited to one configured by multiple devices, but also includes one configured by a single device. In this application, the term "device" is not limited to one configured by a single device, but also includes one configured by multiple devices.

[0162] (About filtering and sorting) Furthermore, regarding the filtering and sorting described in the above embodiment, the configuration may be such that both are performed, or alternatively, only one of them is performed.

[0163] (Automatic storage of medical information) In the above embodiment, the case where the information of the "transcription items" is input and stored by the user has been described, but this is not limited to this. For example, the information of the "transcription items" may be configured to be stored automatically. The specific implementation method of such a configuration is arbitrary, and for example, it may be configured to execute another support-side medical information storage process.

[0164] (Automatic storage of medical information - Medical information storage process on other support sides) 21 is a flowchart of the other support-side medical information storage process. The "other support-side medical information storage process" is, roughly speaking, a process executed by the electronic medical record information storage device 2 and the medical support device 3, and specifically, a process for automatically storing information on the "transcription items." The timing for executing this other support-side medical information storage process is arbitrary, but for example, it may be repeatedly started every predetermined time (e.g., 24 hours), and the description will begin from the point where the other support-side medical information storage process has started.

[0165] ===SD1=== In SD1 of FIG. 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 for requesting the transmission of medical information stored when medical information corresponding to the information in the "transcription items" is newly stored in the medical record medical information DB221. Note that the medical information on the medical record medical information DB221 side corresponding to the information in the "transcription items" is also referred to as "medical information to be transcribed on the medical record side." While specific details are arbitrary, for example, the item "medical record storage location information" in the storage location identification information of FIG. 15 stores information on a combination of table name information and item name information in the medical record medical information DB221 to be transcribed as information in the "transcription items," and the following processing is performed based on the fact that the "medical information to be transcribed on the medical record side" can be identified based on each of this information.

[0166] In detail, the information in the item "Medical record side storage location information" in Figure 15 (hereinafter simply referred to as "Medical record side storage location information") is obtained, and a medical information request signal including the obtained medical record side storage location information is generated and transmitted to the electronic medical record information storage device 2.

[0167] Here, for example, a medical information request signal 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 is generated and sent to the electronic medical record information storage device 2.

[0168] ===SE1=== 21, the control unit 23 of the electronic medical record information storage device 2 receives the medical information request signal transmitted via SD1. Here, for example, the received medical information request signal includes "medical record storage location information" = "medical record prescription history detailed information - drug name," "medical record prescription history detailed information - prescription date," and "medical record test information - test value (KRAS)."

[0169] ===SE2=== In SE2 of Fig. 21, the control unit 23 of the electronic medical record information storage device 2 acquires the newly stored "medical information to be transferred to the medical record side." Although the specific details are optional, for example, in general, it is assumed that the "other support-side medical information storage process" is configured to be executed at the end of the day, and when information indicating the current date is stored as information for the item "update date" 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, the "medical information to be transferred to the medical record side" is considered to have been newly stored.

[0170] Specifically, the "medical record storage location information" included in the medical information request signal received by SE1 is acquired, and each table in the medical record medical information DB221 is referenced to identify the information corresponding to the table and item indicated by the "medical record storage location information" as "medical information to be transferred to medical record," and information on the "update date" item associated with the identified "medical information to be transferred to medical record" in the table is acquired, and the current date is identified using any method. If the acquired "update date" item information does not match the identified information indicating the current date, it is determined that the identified "medical information to be transferred to medical record" was stored before the previous day and was already stored in the support-side medical information DB321 as "transfer item" information in a process before the previous day, and that the identified "medical information to be transferred to medical record" has not been newly stored in the medical record medical information DB221. On the other hand, if the information stored in the aforementioned acquired item "update date" is the same as the information indicating the identified current date, it is determined that the aforementioned identified "medical information to be transferred to the medical record" was newly stored today and has not yet been stored in the support-side medical information DB 321 as information in the "transfer item," and the aforementioned identified "medical information to be transferred to the medical record" has been newly stored in the medical record medical information DB 221. After these determinations, the "medical information to be transferred to the medical record" determined to have been newly stored is acquired.

[0171] Here, for example, a detailed description will be given of the "medical record storage location information" = "medical record prescription history detailed information-drug name" included in the medical information request signal received by SE1. Also, as explained in "SC2" of Fig. 18, for example, in Fig. 5, the items "drug name" = "A1 drug" and "B1 drug" are specifically illustrated, but the "B1 drug" has not yet been stored, and in addition to the information at the top of Fig. 5, the item "drug name" = "A2 drug" (corresponding item "prescription date" and item "update date" = "2020 / 6 / 22") and the item "drug name" = "A3 drug" (corresponding item "prescription date" and item "update date" = "2020 / 6 / 25") are stored as information associated with the item "patient ID" = "IDp1" (not shown).

[0172] In this case, the ``medical record side storage location information'' = ``medical record side prescription history detailed information - drug name'' included in the medical information request signal is obtained, and each table in the medical record side medical information DB221 is referenced to identify the medical record side prescription history detailed information table T93 in Figure 5 indicated by the ``medical record side storage location information'' = ``medical record side prescription history detailed information - drug name'' and the items ``drug name'' = ``A1 drug,'' ``A2 drug'' (not shown), and ``A3 drug'' (not shown) as ``medical information to be transferred to the medical record side'', and 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 side prescription history detailed information table T93 are obtained, and the ``current date'' = ``2020 / 7 / 1'' is identified. Then, only the item "Update Date" = "2020 / 7 / 1" associated with "A1 Drug" has the same information as "Current Date" = "2020 / 7 / 1", so it is determined that "A1 Drug" has been newly stored, and that "A2 Drug" and "A3 Drug" have not been newly stored, and the item "Drug Name" = "A1 Drug" is obtained.

[0173] In addition, similar processing is performed on other "medical record side storage location information" (for example, the information shown in the "medical record side storage location information" item in Figure 15) included in the medical information request signal received by SE1, to obtain the item "Prescription date" = "2020 / 7 / 1" in Figure 5, and the item "Test value" = "D3" and item "Test date" = "2020 / 7 / 1" associated with the test item name = "KRAS" in Figure 4.

[0174] ===SE3=== In SE3 of FIG. 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 combining the aforementioned “medical information to be transferred to the medical record,” “medical record related information,” and “medical record storage location information.” The “medical record related information” is information associated with the “medical information to be transferred to the medical record” in each table of the medical record medical information DB 221. Specifically, it is information required when storing the “medical information to be transferred to the medical record” on the medical support device 3 in the process described below. In this embodiment, when the “medical information to be transferred to the medical record” is information in the medical record test information table T92 of FIG. 4, the “medical record related information” is information in the “patient ID” and “test item name” items. When the “medical information to be transferred to the medical record” is information in the medical record prescription history detailed information table T93 of FIG. 5, the “medical record related information” is information in the “patient ID” item. The related information on the medical record side is not limited to this example, and any other information may be used based on the applied data structure, etc.

[0175] The specific processing of SE3 is optional, but for example, it may refer to each table in the medical record side medical information DB221 to obtain "medical record side related information" associated with the "medical information to be transferred to the medical record side" obtained by SE2, and identify the "medical record side storage location information" indicating the storage location of the "medical information to be transferred to the medical record side" obtained by SE2 from the "medical record side storage location information" included in the medical information request signal received by SE1, and generate and transmit a medical information response signal including information on the combination of the "medical information to be transferred to the medical record side" obtained by SE2, the aforementioned acquired "medical record side related information," and the aforementioned identified "medical record side storage location information."

[0176] For example, for the "medical information to be transferred to the medical record" acquired by SE2, the "patient ID" = "IDp1" is acquired as "medical record related information." Furthermore, the "medical record prescription history detailed information - drug name" is identified from the "medical record storage location information" included in the medical information request signal received by SE1, and "medical record prescription history detailed information - drug name" is associated as a combination of information. Similarly, for other information, "2020 / 7 / 1," "IDp1," and "medical record prescription history detailed information - prescription date" are associated as a combination of information, "D3," "IDp1," and "KRAS," and "medical record laboratory information - laboratory value (KRAS)" are associated as a combination of information, and "2020 / 7 / 1," "IDp1," and "KRAS," and "medical record laboratory information - laboratory date (KRAS)" are associated as a combination of information. Then, a medical information response signal including this combination of information is generated and transmitted.

[0177] ===SD2=== 21, the processing unit 331 of the medical support device 3 receives the medical information response signal transmitted by SE3. Here, for example, the medical information response signal includes information such as a combination of "Drug A1," "IDp1," and "Medical Record Side Prescription History Detailed Information-Drug Name."

[0178] ===SD3=== 21, the processing unit 331 of the medical support device 3 stores medical information in the support-side medical information DB 321 based on the medical information response signal received at SD2. Specifically, this is optional, and generally, for example, the storage location of the "medical information to be transferred to the medical chart" and "medical chart related information" included in the medical information response signal is identified, and the "medical information to be transferred to the medical chart" and "medical chart related information" are stored in the identified storage location. In detail, for example, "first processing of SD3" to "second processing of SBD3" are executed.

[0179] = SD3 first process = In the "first processing of SD3," first, the "medical record side storage location information" contained in the medical information response signal received by SD2 is obtained, and the storage location identification information in Figure 15 is referenced to identify the information for the item "input field ID" that is associated with the same information as the obtained "medical record side storage location information." Then, by reference to the input screen related information in Figure 13, the table and item indicated by the information for the item "medical information" that is associated with the same information as the information for the identified item "input field ID" are identified as the storage location of the "medical information to be transferred to the medical record side" contained in the "medical record side storage location information" contained 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 transferred to the medical record side" is identified as the storage location of the "medical record side related information."

[0180] Here, for example, a detailed description will be given of information combining "A1 drug," "IDp1," and "medical record side prescription history detailed information-medicinal name" included in the medical information response signal received by SD2. In this case, in the "first process of SD3," first, the "medical record side storage location information" = "medical record side prescription history detailed information-medicinal name" included in the medical information response signal received by SD2 is acquired, and the storage location identification information in FIG. 15 is referenced to identify the item "input field ID" = "ID31" associated with the same information as the acquired "medical record side storage location information" = "medical record side prescription history detailed information-medicinal name," and the input screen related information in FIG. 13 is referenced to identify the item "input field ID" = "ID31" associated with the same information as the identified item "input field ID" = "ID31." The treatment information table T3 and the item "drug name" in Figure 9 indicated by the information in the item "medical information" (item "table" = "treatment information" and item "information" = "drug name") stored in the medical information response signal are identified as the storage location of the "medical information to be transferred to the medical record side" = "A1 drug" included in the "medical record side storage location information" included in the medical information response signal, and the item "patient ID" corresponding to the type of "medical record side related information" = "IDp1" in the treatment information table T3 in Figure 9 is identified as the storage location of the "medical record side related information" = "IDp1".

[0181] Similar processing is also performed on other combinations of information included in the medical information response signal received by SD2, for example, identifying the treatment information table T3 in Figure 9 and the item "Prescription date" as the storage location for "Medical information to be transferred to the medical record" = "2020 / 7 / 1", and identifying the treatment information table T3 in Figure 9 and the item "Patient ID" as the storage location for "Medical record related information" = "IDp1". Furthermore, for example, identifying the test information table T6 in Figure 12 and the item "Test value" associated with "Item" = "KRAS" as the storage location for "Medical record related information" = "D3", and identifying the items "Patient ID" and "Test date" associated with "Item" = "KRAS" as the storage location for "Medical record related information" = "IDp1" and "KRAS". Furthermore, for example, the storage location for "Medical information to be transferred to the medical record side" = "2020 / 7 / 1" is identified as the item "Examination date" associated with the examination information table T6 in Figure 12 and "Item" = "KRAS", and the storage location for "Medical record side related information" = "IDp1" and "KRAS" is identified as the items "Patient ID" and "Examination date" associated with the examination information table T6 in Figure 12 and "Item" = "KRAS".

[0182] =SD3 second process= In "SD3 second processing", the "medical information to be transferred to the medical record side" and "medical record side related information" contained in the medical information response signal received by SD2 are stored according to the results of the identification in "SD3 first processing".

[0183] Here, for example, for information identified in the "first processing of SD3" as being stored in the treatment information table T3 of Figure 9, the information in the treatment information table T3 of Figures 6 and 9 will be newly stored, so a unique treatment information ID is generated, an episode ID is identified using the method described in the embodiment, and the current date is identified using any method.Then, in the treatment information table T3 of Figure 9, the information in the item "treatment information ID", the information in the item "episode ID", the information in the item "patient ID", and the information in the item "update date" are stored as the generated treatment information ID, the identified episode ID, the patient ID included as "medical record-side related information" in the medical information response signal received by SD2, and information indicating the identified date, and "medical information to be transferred to the medical record" is stored in association with each of the stored information.

[0184] 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 information in the item "patient ID" that stores the same information as the "patient ID" = "IDp1" included as "medical record related information" in the medical information response signal received by SD2 is identified. Furthermore, after identifying "2020 / 7 / 1" as the current date using any method, the items "treatment information ID" = "IDsm1", "episode ID" = "Dse1", "patient ID" = "IDp1", and "update date" = "2020 / 7 / 1" are stored, as shown in the top row of Figure 9, and the items "drug name" = "A1 drug" (corresponding to "medical information to be transferred to medical record" = "A1 drug") and "prescription date" = "2020 / 7 / 1" (corresponding to "medical information to be transferred to medical record" = "2020 / 7 / 1") are also stored.

[0185] Here, for example, for information identified in the "first processing of SD3" as being stored in the test information table T6 of Figure 12, the information in the test information table T6 of Figures 6 and 12 will be newly stored, so a unique test information ID is generated, an episode ID is identified using the method described in the embodiment, and the current date is identified using any method.Then, in the test information table T6 of Figure 12, the information in the item "Test Information ID", the information in the item "Episode ID", the information in the item "Patient ID", and the information in the item "Update Date" are stored as the generated test 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 information indicating the identified date, and the "medical information to be transferred to the medical record" is stored in association with each of the stored information.

[0186] As an example, a "Test Information ID" = "IDst3" is generated, an "Episode ID" = "IDse1" is identified, and the current date is identified as "2020 / 7 / 1" using any method. Then, as shown in the third row of Figure 12, the following items are stored: "Test Information ID" = "IDst3", "Episode ID" = "Dse1", "Patient ID" = "IDp1", and "Update Date" = "2020 / 7 / 1". The following items are also stored: "Test Item Name" = "KRAS" (corresponding to "Medical Record Related Information" = "KRAS"), "Test Value" = "D3" (corresponding to "Medical Record Transfer Target Medical Information" = "D3"), and "Test Date" = "2020 / 7 / 1" (corresponding to "Medical Record Transfer Target Medical Information" = "2020 / 7 / 1"). This concludes the explanation of the other support-side medical information storage process.

[0187] By configuring in this manner, medical information newly stored in a predetermined storage location for medical information in the medical record side medical information DB221 can be stored in a predetermined storage location for medical information in the support side medical information DB321, thereby automating the storage work of medical information, for example, and enabling medical information to be stored efficiently.

[0188] (Features) Furthermore, the features of the above-described embodiments and modifications may be combined in any manner.

[0189] (Addendum) The medical system of Appendix 1 comprises: a second medical information storage means for storing medical information about a patient that is stored in a predetermined first storage location in a first medical information storage means, the second medical information storage means storing the medical information in a predetermined second storage location in the second medical information storage means; an association information storage means for storing association information that correlates information indicating the information input field displayed on a display means with information indicating the first storage location in the first medical information storage means; and a processing means for performing processing related to storing the medical information in the second medical information storage means based on the association information stored in the association information storage means.

[0190] The medical system of Appendix 2 is the medical system described in Appendix 1, wherein when a plurality of information input fields are displayed on the display means and at least one of the plurality of information input fields is selected by a user, the processing means 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.

[0191] The medical system of Appendix 3 is the medical system described in Appendix 2, wherein in the second process, the processing means filters or sorts the medical information stored in the first storage location identified in the first process based on predetermined criteria and displays it.

[0192] The medical system of Supplementary Note 4 is a medical system described in any one of Supplementary Notes 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 at least 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.

[0193] The medical program of Appendix 5 causes a computer to function as: second medical information storage means for storing medical information about a patient that is stored in a predetermined first storage location in a first medical information storage means, the second medical information storage means storing the medical information in a predetermined second storage location in the second medical information storage means; association information storage means for storing association information that correlates information indicating the information input field displayed on a display means with information indicating the first storage location in the first medical information storage means; and processing means for performing 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.

[0194] (Effect of supplementary notes) 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 correlation information, for example, it is possible to process the information input field associated with the second storage location in association with the first storage location, thereby making it possible to store medical information efficiently.

[0195] 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 is possible to, for example, quickly and accurately transcribe the medical information stored in the first storage location, thereby enabling efficient storage of medical information.

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

[0197] According to the medical system described in Appendix 4, by storing medical information newly stored in a first storage location in a second storage location, for example, the task of storing medical information can be automated, thereby making it possible to store medical information efficiently. [Explanation of symbols]

[0198] 1 Terminal device 2. Electronic medical record information storage device 3 Medical support equipment 11 Communications Department 12 Touchpad 13. Display 14 Recording section 15 Control Unit 21 Communications Department 22 Recording section 23 Control Unit 31 Communications Department 32 Recording section 33 Control Unit 100 Medical-related Systems 221 Medical record side medical information DB 321 Supporting Medical Information DB 322 Input screen related information DB 323 Storage Location Specific Information DB 331 Processing Section T91 Medical Record Patient Information Table T92 Medical Record Examination Information Table T93 Medical Record Prescription History Detailed Information 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 Effect determination information table T5 Side Effect Information Table T6 Examination Information Table

Claims

[Claim 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 second storage locations that are predetermined in the second medical information storage means; an association information storage means for storing association information that correlates information indicating an information input field associated with any of the plurality of second storage locations in the second medical information storage means with information indicating a first storage location in the first medical information storage means; a processing means for performing processing to store the medical information input into 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; A healthcare system with:

Images