Medical information provision system, server, medical information provision device, medical information provision medium, medical information provision method, and program

Abstract

To make it possible to more easily confirm whether a prescribed medicine requires examination in a patient.SOLUTION: A medical information providing system 1 includes a medication examination information extracting unit 21d and a database management unit 21e in a medication examination DB server 20. The medication examination information extracting unit 21d extracts information on medication examination that requires examination when it is prescribed from at least one of package insert data for multiple types of the medications and document data indicating a prescription guideline concerning functional decline of internal organs. In addition, the medication examination information extracting unit 21d generates a medication examination database in which the extracted information on medication examination and the medication are stored in association with each other. In addition, in response to a request from a terminal device 10, the database management unit 21e refers to the generated medication examination database and provides information on medication examination of a target medication for the terminal device 10.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a medical information providing system, a server, a medical information providing device, a medical information providing medium, a medical information providing method, and a program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, a system is known that provides information regarding drug prescriptions for the purpose of appropriate use of drugs. For example, in the appropriate drug use monitoring system described in Patent Document 1, important information necessary for the safe use of drugs (interactions, side effects, contraindications, etc.) is displayed in different colors on a list screen according to the degree to which it should be taken into consideration (importance) for the appropriate use of prescribed drugs. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-197188 A Summary of the Invention [Problem to be solved by the invention]

[0004] Here, some drugs require certain tests when prescribed, and doctors or pharmacists are required to take care to ensure that necessary tests are carried out when prescribing such drugs. In addition, in prescription inspection, pharmacists are required to carry out high-quality prescription inspection after making sure that they know whether or not there are any prescribed drugs that require certain tests when prescribing. However, the above-mentioned drug appropriate use monitoring system does not distinguish between drugs that require a specific test when prescribed. Therefore, doctors or pharmacists must check the package insert, etc., one by one to determine whether a drug requires a specific test when prescribed. However, since there are tens of thousands of types of drugs, it is not easy to check one by one whether a prescribed drug requires a specific test when prescribed by a doctor or when dispensed by a pharmacist. This causes problems such as a decrease in the work efficiency of doctors or pharmacists, and the reliability of the execution of tests or the quality of prescription inspection. Thus, in the prior art, it was not easy to ascertain whether a prescribed drug required testing on the patient.

[0005] An object of the present invention is to make it easier to confirm whether or not a prescribed drug requires testing in a patient. [Means for solving the problem]

[0006] In order to solve the above problems, a medical information providing system according to one aspect of the present invention comprises: A medical information providing system including a terminal device and a server configured to be able to communicate with each other, The server, A drug test information extraction means for extracting information on tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on a document showing prescription guidelines for decreased visceral function; a database generating means for generating a drug testing information database in which information on the drug testing extracted by the drug testing information extracting means and the drug are stored in association with each other; a drug testing information providing means for providing information on the drug testing of a target drug to the terminal device in response to a request from the terminal device by referring to the drug testing information database generated by the database generating means; The present invention is characterized by comprising: Effect of the Invention

[0007] According to the present invention, it is easier to ascertain whether a prescribed drug requires testing in a patient. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing a system configuration of a medical information providing system 1 according to one embodiment of the present invention. [Diagram 2] 2 is a block diagram showing a specific configuration of each device included in the medical information providing system 1. FIG. [Diagram 3] 1 is a schematic diagram showing an example of a prescription (outpatient prescription) P output in this embodiment. FIG. [Figure 4] FIG. 2 is a schematic diagram showing data contents of a drug testing information DB 22b. [Diagram 5] 13 is a flowchart showing the flow of prescription output processing executed by the terminal device 10. [Figure 6] 13 is a flowchart showing the flow of a drug testing information DB generation process executed by the drug testing information DB server 20. [Figure 7] 13 is a flowchart showing the flow of a drug testing information DB update process executed by the drug testing information DB server 20. [Figure 8] FIG. 2 is a diagram showing an example of a system configuration in which the medical information providing system 1 is cloud-based to a higher degree. [Figure 9] FIG. 1 is a schematic diagram showing a configuration in which a medical information providing system 1 is realized by a single information processing device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0010] [System configuration of medical information provision system 1] FIG. 1 is a diagram showing the system configuration of a medical information providing system 1 according to one embodiment of the present invention. In this embodiment, a case will be described as an example in which the medical information providing system 1 is configured as a prescription issuing system that issues prescriptions (here, outpatient prescriptions). 1, the medical information providing system 1 includes a terminal device 10 and a drug testing information database server (drug testing information DB server) 20, and the terminal device 10 and the drug testing information DB server 20 are configured to be able to communicate with each other via a network such as a VPN (Virtual Private Network). In this embodiment, the drug testing information DB server 20 can be configured as a cloud server. However, the drug testing information DB server 20 can also be configured as a dedicated physical server.

[0011] The terminal device 10 is configured with an information processing device such as a PC (Personal Computer). The terminal device 10 is also connected to various systems (hereinafter referred to as "hospital systems") that manage medical information on patients, medicines, etc. in the hospital and to a network such as a VPN. The terminal device 10 is operated by a doctor or a prescription issuing person, and accepts an operation to issue an outpatient prescription for a patient whose medical treatment has been completed. When an operation to issue an outpatient prescription is performed, the terminal device 10 acquires prescription data for the patient, and transmits a search request to the drug testing information DB server 20 to determine whether or not a drug included in the prescription data is a drug that requires testing when prescribed (here, this includes drugs whose dosage needs to be adjusted due to a decline in organ function). Then, for drugs that require testing when prescribed, the terminal device 10 acquires test value data for the patient from the hospital system, and adds the test value data to the prescription data. The terminal device 10 outputs the outpatient prescription by, for example, printing the prescription data to which the test value data has been added on a paper medium. In addition, the outpatient prescription can be output in the form of being printed on paper, output as electronic data in a predetermined format, or displayed on a non-volatile display (such as electronic paper). When outputting an outpatient prescription, the test item or test value data can be represented as a one-dimensional or two-dimensional barcode, in addition to being represented as a character string. In this case, the test item or test value character string can be displayed by reading the barcode with a terminal of the patient or pharmacy. Specifically, taking into consideration the appropriateness of the test item or test value data being directly exposed to the eyes of the patient or a third party, it is possible to represent some or all of the test item or test value data as a barcode.

[0012] The drug testing information DB server 20 automatically generates a drug testing information database (drug testing information DB) showing a list of drugs that require testing when prescribed, by referring to data on package inserts and prescription guideline data, which indicate whether or not a drug requires testing when prescribed, and the reference value or reference range of the test value, for various drugs. For drugs that require testing when prescribed, a reference value (threshold value) of the test value is set, and when there is one reference value of the test value, a range larger or smaller than the reference value becomes a range that is suitable for the prescription of the drug (hereinafter referred to as the "reference range"). On the other hand, when the reference value of the test value is set as a range (i.e., upper and lower thresholds are set), the range between these thresholds becomes the reference range. The drug testing information DB server 20 stores the reference range for drugs that require testing when prescribed. When the drug testing information DB server 20 receives a search request from the terminal device 10 as to whether or not a drug requires testing when prescribed, it searches the drug testing information DB and determines whether the drug for which the search request was made requires testing when prescribed, and if so, transmits search result data including the test items and standard ranges of test values, etc.

[0013] [Specific configuration of each device] Next, a specific configuration of each device in the medical information providing system 1 will be described. FIG. 2 is a block diagram showing a specific configuration of each device included in the medical information providing system 1. As shown in FIG.

[0014] [Specific Configuration of Terminal Device 10] 2, in the medical information providing system 1, the terminal device 10 includes, as hardware configuration, a control unit 11 that performs various calculation processes, a storage unit 12 that stores various information, an input unit 13 realized by a keyboard, a touch panel, or the like, a display unit 14 that includes a display, a communication unit 15 that controls communication with other devices via a network, and an imaging unit 16 that captures images. Such terminal device 10 has various programs installed in the storage unit 12, and performs functions such as issuing outpatient prescriptions by the control unit 11 operating in accordance with these programs. In addition, in the terminal device 10, in such a hardware configuration, a program for the prescription output processing described later is executed, so that the control unit 11 realizes a prescription information acquisition unit 11a, a drug test information confirmation unit 11b, a test result data acquisition unit 11c, and a prescription output unit 11d.

[0015] The prescription information acquisition unit 11a acquires prescription data of a patient for whom a prescription is to be issued in response to an operation to instruct issuance of a prescription via the input unit 13. At this time, the prescription information acquisition unit 11a acquires prescription data by acquiring prescription data prepared by a doctor from an in-hospital system such as an electronic medical record system, or by accepting input of prescription data via the input unit 13. Note that the prescription information acquisition unit 11a may acquire prescription data by automatically extracting data of prescription drugs entered by a doctor in an electronic medical record.

[0016] The drug testing information confirming unit 11b confirms whether each drug included in the prescription data acquired by the prescription information acquiring unit 11a is stored in the drug testing information DB as a drug that requires testing when prescribed. Specifically, the drug testing information confirming unit 11b transmits a search request to the drug testing information DB server 20 to search the drug testing information DB using the name of each drug included in the prescription data as a key. Then, the drug testing information confirming unit 11b acquires the search result transmitted from the drug testing information DB server 20.

[0017] The test result data acquisition unit 11c refers to the search results of the drug testing information DB server 20 acquired by the drug testing information confirmation unit 11b, and if the drugs for which the search request has been made include a drug that requires testing when prescribed, it acquires data on the test values ​​(hereinafter referred to as "drug-specific test values") related to the test for the patient corresponding to the prescription from the hospital system. In this embodiment, when the test result data acquisition unit 11c acquires test value data from the hospital system, it also acquires data for the patient from a predetermined number of times in the past (here, three times). However, a validity period is set for the test values ​​depending on the type of test, and the test result data acquisition unit 11c acquires only data within the validity period from the hospital system. Furthermore, when a prescription is issued, the test result data acquisition unit 11c acquires data on test values ​​related to test items that are set in advance and common to all patients (hereinafter referred to as "fixed test values") from the hospital system for each patient. Note that the fixed test values ​​are selected test values ​​related to diseases that cause serious side effects when prescribed with medicines.

[0018] The prescription output unit 11d integrates the prescription data acquired by the prescription information acquisition unit 11a and the fixed test value and drug-specific test value data acquired by the test result data acquisition unit 11c, and outputs a prescription for the target patient that shows the prescribed drugs and, for drugs that require tests at the time of prescription, the test items and the test value data for the patient.

[0019] FIG. 3 is a schematic diagram showing an example of a prescription (outpatient prescription) P output in this embodiment. As shown in Figure 3, the prescription P output in this embodiment includes a patient information area P1 representing information about the patient, a medical institution information area P2 representing the medical institution that issued the prescription P, a fixed test value area P3 representing data on fixed test values, and a drug-specific test value area P4 representing data on drug-specific test values.

[0020] In the patient information area P1, various information about the patient, such as the patient's name, age, sex, address, insurance type, etc., is displayed. The medical institution information area P2 displays various information about the medical institution that issued the prescription P, such as the name of the medical institution that issued the prescription P and contact information. In the fixed test value area P3, test value data related to test items common to all patients are displayed in a list. As the fixed test values, for example, all or some of the test items such as AST, ALT, ALP, T-BIL, CRE, eGFR, Cys-C, K, CPK, WBC, HGB, PLT, SEG, ST, TSH, HbA1C, etc. can be set. As these fixed test values, it is effective to select test values ​​related to side effects that cannot be detected early by subjective symptoms and side effects whose clinical test values ​​change before subjective symptoms.

[0021] In the drug-specific test value area P4, test value data for drugs that require testing when prescribed are displayed in a list. For example, in the drug-specific test value area P4, the drug name of the drug that requires testing when prescribed, "Tablet A 17.5 mg", the classification (code unit name) of the test item, the test value data "renal function {eGFR, CRE, Cys-C}", "CA 8.5", "ALB 3.5", and the symbols "-", "L", or "H" indicating the change in the test value are displayed in correspondence with each other. In the symbols indicating the change in the test value, "-" indicates that the value is within the reference range, "L" indicates that the value is below the reference range, and "H" indicates that the value is above the reference range. In the prescription P in this embodiment, the changes in each test value are displayed from left to right in the order of the test value before last, the previous test value, and the current (most recent) test value. For example, when the change in the test value is displayed as "--L", it indicates that the test value before last and the previous test were within the reference range, and the test value in the most recent test was below the reference range. In the drug-specific test value area P4, if the test value data for a drug that requires testing for the prescription is not within the standard range, the test item may be represented in a specific form (such as in red or underlined). In this way, by showing the trends in past test values ​​on prescription P, it becomes possible to more accurately judge the patient's condition and more appropriately prescribe medicines.

[0022] In addition, in the prescription P in this embodiment, as a classification of test items, for some test items, a code unit name that represents a combination of multiple test items is displayed. For example, a combination of three test items, "eGFR", "CRE", and "Cys-C", is frequently listed as a test item for multiple drugs, and is therefore displayed as a combination of test items corresponding to the test item classification "renal function". Note that the test value data of the test items represented as these combinations is displayed elsewhere, for example, as a fixed test value. However, when a combination of test items is represented, it is possible to also display the test value data. Furthermore, instead of displaying the test value data of the test items included in the combination (or together with the test value data), the symbols "-", "L", or "H" indicating the above-mentioned test value trends can be displayed, and if the test value data is not within the reference range, the test item can be displayed in a specific form (e.g., in red or underlined). By using code unit names that represent combinations of test items in this way, it is possible to describe a test item that would normally require three lines in one line, making it possible to efficiently represent test value data in the prescription area, where there is not much space to write. In addition, when representing the test item or test value data in a barcode, it is possible to represent one or both of the fixed test value area P3 and the drug-specific test value area P4 in a barcode, or to represent the data of a specific test item or test value in the fixed test value area P3 and the drug-specific test value area P4 in a barcode.

[0023] [Specific configuration of drug testing information DB server 20] 2, in the medical information provision system 1, the drug testing information DB server 20 includes, as hardware components, a control unit 21 that performs various arithmetic processing, a storage unit 22 that stores various information, an input unit 23 realized by a keyboard or the like, a display unit 24 including a display, and a communication unit 25 that controls communication with other devices via a network. Such a drug testing information DB server 20 has various programs installed in the storage unit 22, and the control unit 21 operates in accordance with these programs to perform a drug testing information DB generation function, a drug testing information DB update function, and a drug testing information DB search function. In addition, in the drug testing information DB server 20, in such a hardware configuration, a program for a drug testing information DB generation process or a drug testing information DB update process, etc., described later, is executed, whereby a drug document information acquisition section 21a, an item-specific condition setting section 21b, an exception information acquisition section 21c, a drug testing information extraction section 21d, and a database management section 21e are realized in the control section 21. In addition, a drug document data storage section 22a, a drug testing information DB 22b, and an exception information storage section 22c are stored in the storage section 22 of the drug testing information DB server 20.

[0024] The drug document data storage unit 22a stores data of package inserts for various drugs acquired from an external database (such as a database of a pharmaceutical manufacturer or a public institution) that accumulates data of package inserts for various drugs, and data of guideline documents acquired from an external database that accumulates data of prescription guidelines for decreased function of organs (such as the kidney) (for example, the CKD (Chronic Kidney Disease) Treatment Guide compiled by the Japanese Society of Nephrology). When the data of various documents stored in the drug document data storage unit 22a is updated in response to an update in the database from which the data is acquired, the data is updated accordingly.

[0025] The drug test information DB 22b stores, for various drugs mentioned in the package insert and prescription guidelines for organ dysfunction, test items required for prescription of the drug in association with data on reference ranges of test values. FIG. 4 is a schematic diagram showing the data contents of the drug testing information DB 22b. As shown in FIG. 4, the drug testing information DB22b stores, in association with each other, a drug code which is a code specific to the drug, the name of the drug (product name or generic name), a character string (test item) indicating a test item extracted from the package insert or guideline, the name of the paragraph in the package insert or the name of the guideline from which the character string was extracted, a code unit name which indicates the classification of the test item, and reference range data which indicates the reference range of the test value. For example, the first row of drug test information DB22b in Figure 4 stores the results of extracting the string "hyperkalemia" from the "Contraindications" paragraph for a drug with drug code "xxxxxx" and drug name "C solution for injection," extracting "K" (potassium) as the code unit, and "3.5 to 4.8 mEq / L" as the reference range of the test value. Each data of the drug testing information DB 22b is automatically generated by a drug testing information DB generation process described later. Note that the contents of the automatically generated drug testing information DB 22b may be finalized by having an expert such as a doctor or a pharmacist approve the contents of the database.

[0026] The exception information storage unit 22c stores exception information related to drug prescriptions that is issued from time to time by pharmaceutical manufacturers, public institutions, etc. For example, safety-related information (exceptional safety information) that is not described in attached documents or guidelines, such as emergency safety information or safety flash emails issued by the Pharmaceuticals and Medical Devices Agency, is stored as exception information in the exception information storage unit 22c. In addition, if the contents of the exception information stored in the exception information storage unit 22c are included in an attachment or a guideline due to an update or the like, the exception information stored in the exception information storage unit 22c is deleted sequentially by the exception information acquisition unit 21c.

[0027] The drug document information acquisition unit 21a acquires data on package inserts and guideline documents for various drugs from an external database (databases of pharmaceutical manufacturers, public institutions, etc.) that accumulates data on package inserts for various drugs, and from an external database that accumulates data on prescription guideline documents for organ function decline. In this embodiment, the drug document information acquisition unit 21a accesses the external database at a predetermined timing (for example, at a predetermined period such as once a month or when a specific instruction is input) and acquires data on package inserts and guideline documents.

[0028] The item-specific condition setting unit 21b sets extraction conditions for extracting character strings of test items or reference values ​​or reference ranges of test values ​​for each drug for each item of the package insert and guideline (dosage and administration, contraindications, etc.) for each item of the package insert and guideline, targeting data of the package insert and guideline documents. For example, in the case of the package insert, extraction conditions are set for each item such as "dosage and administration," "warning," "contraindications," and "pharmacokinetics." The extraction conditions set here may include, for example, a word (character string) to be extracted, a predetermined word related to the word, and a character interval between these words (a relationship between the extracted word and the predetermined word). The extraction conditions set in this manner are stored in a predetermined storage area such as the storage unit 22 as a dictionary for each item. In the item-specific condition setting unit 21b, extraction conditions are set for each item of the package insert and guideline, making it possible to set more appropriate extraction conditions that reflect the characteristics of the description of each item. Furthermore, by including in the extraction conditions the word (character string) to be extracted, a specific word related to that word, and the character spacing between these words (the relationship between the word to be extracted and the specific word), it becomes possible to automatically and appropriately extract reference values ​​or reference ranges for test items or test values ​​contained in the package insert and guideline document data.

[0029] The exception information acquisition unit 21c sequentially acquires exception information (exceptional safety information) regarding drug prescriptions issued sequentially from pharmaceutical manufacturers, public institutions, etc., and stores it in the exception information storage unit 22c. Furthermore, when the content of the exception information stored in the exception information storage unit 22c is to be included in the package insert or guidelines due to an update or the like, the exception information acquisition unit 21c sequentially deletes the exception information stored in the exception information storage unit 22c.

[0030] In order to generate the drug testing information DB, the drug testing information extraction unit 21d acquires data of the package insert and guideline documents of each drug stored in the drug document data storage unit 22a, and extracts character strings of the test items and the reference values ​​or reference ranges of the test values ​​for each drug according to the extraction conditions for each item set by the item-specific condition setting unit 21b. At this time, the drug testing information extraction unit 21d appropriately refers to the exception information stored in the exception information storage unit 22c, and if there are character strings of the test items and the reference values ​​or reference ranges of the test values ​​that are not included in the data of various documents stored in the drug document data storage unit 22a, these are added to the extraction result of the character strings. This makes it possible to search for the test items and the reference values ​​or reference ranges of the test values ​​of drugs that require testing when prescribed, including information on safety issued before updating the drug testing information DB.

[0031] Then, based on the extraction result of the character string of the test item and the reference value or reference range of the test value for each drug, the drug testing information extraction unit 21d converts the extracted test item into a code unit name representing the classification of the test item. Furthermore, the drug testing information extraction unit 21d associates the drug code, which is a code unique to the drug, the name of the drug (product name or generic name), the character string (test item) representing the test item extracted from the package insert or guideline, the paragraph name of the package insert or the guideline name from which the character string was extracted, the code unit name representing the classification of the test item, and the reference range data representing the reference range of the test value, and stores them in the drug testing information DB.

[0032] When the database management unit 21e receives a search request from the terminal device 10, it searches the drug testing information DB using the name of the drug specified in the search request as a key, and transmits the search results to the terminal device.

[0033] [Operation] Next, the operation of the medical information providing system 1 will be described. [Processing of terminal device 10]

[0034] FIG. 5 is a flowchart showing the flow of the prescription output process executed by the terminal device 10. The prescription output process is started in response to an instruction to execute the prescription output process being input via the input unit 13.

[0035] When the prescription output process is started, in step S1, the prescription information acquisition unit 11a acquires prescription data of a patient for whom a prescription is to be issued. In step S2, the drug inspection information confirming unit 11b acquires the name of the drug contained in the prescription data. In step S3, the drug testing information confirmation unit 11b sends a search request to the drug testing information DB server 20 to search the drug testing information DB using the drug name included in the prescription data as a key, and obtains the search result in the drug testing information DB server 20. When the drug testing information confirmation unit 11b sends a search request to the drug testing information DB, in addition to using the drug name as a key, it is also possible to use information that can uniquely identify the drug as a key, for example, a drug code as a key.

[0036] In step S4, the test result data acquisition unit 11c refers to the search results of the drug testing information DB server 20 acquired by the drug testing information confirmation unit 11b, and determines whether or not each drug for which a search request has been made includes a drug that requires testing when prescribed. If the requested drugs include a drug that requires testing when prescribed, the determination in step S4 is YES, and the process proceeds to step S5. On the other hand, if the requested searched drugs do not include any drug that requires testing when prescribed, the result of the determination in step S4 is NO, and the process proceeds to step S6.

[0037] In step S5, the test result data acquiring unit 11c acquires, for the patient corresponding to the prescription, data on drug-specific test values ​​for drugs that require testing at the time of prescription from the hospital system, and adds the data to the prescription data.

[0038] In step S6, the drug inspection information checking section 11b judges whether or not the search in the drug inspection information DB has been completed for all drugs included in the prescription data. When the search of the drug inspection information DB has been completed for all drugs included in the prescription data, the determination in step S6 is YES, and the process proceeds to step S7. On the other hand, if the search of the drug inspection information DB has not been completed for all drugs included in the prescription data, the result of step S6 is NO, and the process proceeds to step S2. In step S7, the test result data acquiring unit 11c acquires data of fixed test values ​​for the patient corresponding to the prescription from the hospital system, and adds the data to the prescription data. In step S8, the prescription output unit 11d integrates the prescription data acquired by the prescription information acquisition unit 11a and the fixed test value and drug-specific test value data acquired by the test result data acquisition unit 11c, and outputs the prescription (see Figure 3). After step S8, the prescription output process ends.

[0039] Through this processing, when prescription data includes a drug that requires testing at the time of prescription, the necessary test items and standard ranges of test values ​​for that drug are obtained from the drug testing information DB, and the test value data for those test items are obtained from the hospital system, making it possible to present these together on the prescription for the patient in question. That is, the medical information providing system 1 makes it easier to check whether or not a prescribed medicine requires a test on the patient. Therefore, according to the medical information providing system 1, it is possible to more reliably carry out necessary tests for drugs that require tests when prescribed. In addition, since the prescription indicates which drugs require testing and the patient's test values, the pharmacist inspecting the prescription can clearly determine whether it is appropriate to prescribe the drug. This provides an opportunity for the pharmacist to inquire about the drug to the medical institution, and also makes the basis for the inquiry more certain. Therefore, the medical information providing system 1 can improve the quality of prescription inspection by pharmacists (improvement of pharmaceutical management).

[0040] [Processing of drug testing information DB server 20] FIG. 6 is a flowchart showing the flow of the drug testing information DB generation process executed by the drug testing information DB server 20. The drug testing information DB generation process is started in response to an instruction to execute the drug testing information DB generation process being input via the input unit 23, or in response to an instruction to execute the drug testing information DB update process described below.

[0041] When the drug testing information DB generation process is started, in step S11, the drug document information acquisition unit 21a acquires data on package inserts for various drugs and data on guideline documents from an external database (a database of pharmaceutical manufacturers, public institutions, etc.) that stores data on package inserts for various drugs, and an external database that stores data on prescription guidelines for decreased organ function. In step S12, the item-specific condition setting unit 21b sets extraction conditions for extracting character strings of test items or reference values ​​or reference ranges of test values ​​for each drug for each item of the package insert and guideline (dosage and administration, contraindications, etc.) for the package insert and guideline documents. Note that the extraction conditions for extracting character strings of test items or reference values ​​or reference ranges of test values ​​for each drug may be set in advance and saved as a setting file, and this setting file may be read out.

[0042] In step S13, the drug testing information extraction unit 21d acquires data on the package insert and guideline documents of each drug stored in the drug document data storage unit 22a in order to generate the drug testing information DB. In step S14, the drug testing information extraction unit 21d extracts character strings of the test items and the reference values ​​or reference ranges of the test values ​​for each drug according to the extraction conditions for each item set by the item-specific condition setting unit 21b. At this time, the drug testing information extraction unit 21d appropriately refers to the exception information stored in the exception information storage unit 22c, and if there are character strings of the test items and the reference values ​​or reference ranges of the test values ​​that are not included in the data of various documents stored in the drug document data storage unit 22a, these are added to the extraction result of the character strings.

[0043] In step S15, the drug test information extraction unit 21d determines whether or not character strings of the test items and reference values ​​or reference ranges of the test values ​​for each drug have been extracted. If character strings of test items and reference values ​​or reference ranges of test values ​​for each drug are extracted, the determination in step S15 is YES, and the process proceeds to step S16. On the other hand, if a character string of the test item and the reference value or reference range of the test value for each drug is not extracted, the result of step S15 is determined as NO, and the process proceeds to step S18. In step S16, the drug test information extraction unit 21d converts the extracted test items into code unit names that represent the classification of the test items.

[0044] In step S17, the drug testing information extraction unit 21d associates the drug code, which is a code unique to the drug, the name of the drug (product name or generic name), a character string indicating the test item (test item) extracted from the package insert or guideline, the paragraph name of the package insert or guideline name from which the character string was extracted, the code unit name indicating the classification of the test item, and reference range data indicating the reference range of the test value, and stores them in the drug testing information DB.

[0045] In step S18, the drug test information extraction unit 21d determines whether or not processing has been completed for all data of the package inserts and guideline documents of each drug stored in the drug document data storage unit 22a. If the processing has not been completed for all of the data of the package inserts and guideline documents of each drug stored in the drug document data storage unit 22a, the result of step S18 is determined to be NO, and the processing proceeds to step S13. On the other hand, when the processing has been completed for all the data of the package inserts and guideline documents of each drug stored in the drug document data storage unit 22a, the result of the determination in step S18 is YES, and the drug testing information DB generation processing is terminated.

[0046] This process makes it possible to extract drugs that require testing when prescribed from package insert or guideline document data, and automatically generate a drug testing information DB that includes the test items and reference ranges of test values. Therefore, compared to manually generating a drug testing information DB, it is possible to reduce the time and labor required to generate a database, and to efficiently generate a database with more accurate content.

[0047] Next, the drug testing information DB update process executed by the drug testing information DB server 20 will be described. FIG. 7 is a flowchart showing the flow of the drug testing information DB update process executed by the drug testing information DB server 20. The drug testing information DB update process is started at a preset timing, such as at a predetermined interval.

[0048] When the drug testing information DB update process is started, in step S21, the drug document information acquisition unit 21a determines whether there are any version updates in external databases (databases of pharmaceutical manufacturers, public institutions, etc.) that store data on package inserts for various drugs, and in external databases that store data on prescription guidelines for decreased organ function. If there is a version update, the determination in step S21 is YES, and the process proceeds to step S22. On the other hand, if there is no version update, the result of step S22 is NO, and the drug testing information DB update process ends.

[0049] In step S22, the drug document information acquiring section 21a executes a drug inspection information DB generating process. In step S23, the exception information acquisition unit 21c deletes the contents of the exception information that have come to be included in the attached document or the guideline due to an update or the like from the exception information storage unit 22c. After step S23, the drug testing information DB update process ends. By this process, the contents of the drug inspection information DB are updated to the latest state, making it possible to output a more appropriate prescription.

[0050] [Variation 1] In the above-described embodiment, the medical information providing system 1 can be realized as a more advanced cloud-based system. FIG. 8 is a diagram showing an example of a system configuration in which the medical information providing system 1 is cloud-based to a higher degree. As shown in FIG. 8, the drug testing information DB server 20 can be configured as a virtual server realized on the cloud, and an API (Application Program Interface) can be provided for accepting search requests to determine whether or not a drug requires testing when prescribed. In this case, the functions of the drug testing information DB server 20 can be easily used from various terminal devices 10 with different platforms, making the medical information providing system 1 easy to use for many users. Furthermore, when the drug testing information DB server 20 is a virtual server realized on the cloud, the functions of the drug testing information DB server 20 can be divided and a virtual server can be configured for each function. For example, as shown in FIG. 8, the functions of the drug testing information DB server 20, that is, the function of automatically generating the drug testing information DB, the function of searching the drug testing information DB, and the function of maintaining the drug testing information DB (such as updating the drug testing information DB), can each be configured by a different virtual server. This allows the multiple functions provided in the drug testing information DB server 20 to be essentially separated, making it possible to flexibly operate the drug testing information DB server 20, such as by running only the functions that are being used and suspending functions that are not being used. Furthermore, when the drug testing information DB server 20 is a virtual server realized on the cloud, it is possible to configure the entire drug testing information DB server 20 or some of the functions of the drug testing information DB server 20 to be duplicated by multiple virtual servers. For example, in terms of the functions of the drug testing information DB server 20, in response to an increase in the number of search requests from terminal devices 10, or in response to operational reasons (maintenance, etc.) of the drug testing information DB server 20, the function of searching the drug testing information DB, etc., can be configured to be duplicated on multiple virtual servers. This allows the functional configuration to be appropriately changed depending on the processing capacity required for the drug testing information DB server 20 and operational convenience. In addition, when changing the processing power required of the drug testing information DB server 20, it is possible to duplicate the entire drug testing information DB server 20 or some of the functions of the drug testing information DB server 20 by multiple virtual servers, or to change the specifications of the virtual servers.

[0051] [Variation 2] In the above-described embodiment and variant example 1, a cloud-based medical information providing system 1 is constructed, and a search request is made from the terminal device 10 to the drug testing information DB server 20 to confirm whether or not the drug requires testing when prescribed. On the other hand, by providing the drug testing information DB in the terminal device 10, the functions of the medical information providing system 1 may be realized by a single information processing device (that is, as a stand-alone system). In this case, the terminal device 10 may be provided with the functions of the drug document information acquisition unit 21a, item-specific condition setting unit 21b, exception information acquisition unit 21c, drug testing information extraction unit 21d, drug document data storage unit 22a, drug testing information DB 22b, and exception information storage unit 22c of the drug testing information DB server 20.

[0052] FIG. 9 is a schematic diagram showing a configuration in which the medical information providing system 1 is realized by a single information processing device. In FIG. 9, the main functional components of the drug testing information DB server 20 shown in FIG. 2 are provided in the terminal device 10, so that the terminal device 10 alone realizes the functions of the medical information providing system 1. With the configuration shown in Figure 9, a standalone device can search for drugs that require testing before being prescribed, so that doctors and pharmacists can easily check, without using a network, whether or not the prescribed drug contains a drug that requires testing before being prescribed, and if so, the test items and the standard ranges of the test values.

[0053] As described above, the medical information providing system 1 according to this embodiment includes the drug testing information DB server 20, which includes the drug testing information extracting unit 21d (drug testing information extracting means, database generating means) and the database managing unit 21e (drug testing information providing means). The drug test information extraction unit 21d extracts information regarding tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on documents showing prescription guidelines regarding decreased visceral functions. Furthermore, the drug testing information extraction unit 21d generates a drug testing information database in which the extracted information relating to testing of the drug is stored in association with the drug. Furthermore, in response to a request from the terminal device 10, the database management unit 21e refers to the created drug testing information database and provides the terminal device 10 with information related to testing of the target drug. With this configuration, it becomes possible to extract drugs that require testing when prescribed from package insert or guideline document data, and automatically generate a drug testing information DB that includes the test items and reference ranges of test values, etc. Then, by using the drug testing information DB generated in this way, it becomes easier to confirm whether or not a prescribed drug requires testing for a patient.

[0054] Furthermore, the medical information providing system 1 includes an item-by-item condition setting unit 21b in the drug testing information DB server 20. The item-specific condition setting unit 21b sets extraction conditions for each item of the package insert data and the guideline data to extract information regarding the testing of drugs that require testing when prescribing, targeting the package insert data and the guideline document data. Furthermore, the drug testing information extraction unit 21d extracts information regarding testing of drugs that require testing when prescribed for each item of the package insert data and the guideline document data, in accordance with the extraction conditions set by the item-by-item condition setting unit 21b. With this configuration, extraction conditions are set for each item in the package insert and guidelines, making it possible to set more appropriate extraction conditions that reflect the characteristics of the descriptions in each item.

[0055] The extraction conditions also define character strings set for each item of the data in the attached document and the data in the document indicating the guidelines, specific character strings that are associated with the character strings, and the relationships between these character strings. With this configuration, it becomes possible to automatically and appropriately extract reference values ​​or reference ranges for test items or test values ​​contained in the data of package inserts and guideline documents.

[0056] The medical information providing system 1 also includes an exception information acquiring unit 21c (safety information acquiring means). The exception information acquiring unit 21c acquires information on the safety of drugs that is not included in the drug testing information database. Furthermore, the drug testing information extraction unit 21d refers to the drug testing information database and information on drug safety, and provides information on testing of the target drug. With this configuration, it is possible to search for test items and reference values ​​or reference ranges of test values ​​for drugs that require testing when prescribed, including safety information issued before the drug testing information DB was updated.

[0057] The medical information providing system 1 also includes a drug documentation information acquiring section 21a (a drug documentation information acquiring means). The drug document information acquiring unit 21a acquires at least one of data on package inserts of a plurality of types of drugs and data on a document showing prescription guidelines regarding the decline of visceral functions from a preset acquisition source. Furthermore, the drug document information acquiring unit 21a acquires and updates at least one of data on package inserts of a plurality of types of drugs and data on documents showing prescription guidelines regarding decreased visceral functions at a preset timing. With this configuration, the contents of the drug testing information DB are updated to the latest state, making it possible to output more appropriate prescriptions.

[0058] Moreover, the prescription P according to this embodiment includes a patient information area P1, a medical institution information area P2, a fixed test value area P3, and a drug-specific test value area P4. The patient information area P1 displays information about the patient. The medical institution information area P2 indicates the medical institution that issued the prescription. The fixed test value area P3 represents data of fixed test values ​​that are test values ​​common to multiple patients regardless of the prescribed medication. The drug-specific test value area P4 shows data on drug-specific test values, which are test values ​​related to drugs that require testing when prescribed, among the drugs prescribed to the patient, by identifying past trends of the patient. With this configuration, it becomes possible to more accurately assess the patient's condition and more appropriately prescribe medicines.

[0059] The present invention is not limited to the above-described embodiment, and modifications and improvements within the scope of the present invention that can achieve the object of the present invention are included in the present invention. For example, in the above embodiment, the prescription output by the medical information providing system 1 is described as an outpatient prescription, but this is not limited to this. That is, the medical information providing system 1 can output an in-hospital prescription, and can also be applied to various medical information providing media other than prescriptions that output prescribed drugs.

[0060] In the above embodiment, the data on the reference ranges of test values ​​related to drugs that require testing when prescribed is described as being stored in the drug testing information DB, but this is not limited to the above. For example, data on the reference range of test values ​​related to drugs that require testing when prescribed may be stored in an in-hospital system, etc., and when the test result data acquisition unit 11c acquires the test value data, it may also acquire the reference range of the test value.

[0061] In addition, in the above-described embodiment, prescription P is described as showing the progress of each test value from left to right in the order of the test value before last, the previous test value, and the current (most recent) test value, but this is not limited to this. That is, in the drug-specific test value area P4, it is sufficient that the transition of the patient's test values ​​is identifiable, and for example, the transition of past test values ​​can be visually identifiable by an arrow pointing to the upper right for an increasing trend, an arrow pointing to the lower right for a decreasing trend, and an arrow pointing to the right for a maintaining trend. Furthermore, the transition of past test values ​​can be displayed as a broken line, and the relative relationship of past test values ​​to the reference range of test values ​​can be displayed by the display position of a predetermined symbol (dot, asterisk, etc.).

[0062] In the above embodiment, the Pharmaceuticals and Medical Devices Agency is used as an example of the source of exception information related to drug prescriptions, but the present invention is not limited to this. That is, it is possible to obtain exception information issued by a public institution in Japan or abroad similar to the Pharmaceuticals and Medical Devices Agency.

[0063] Furthermore, in the above-described embodiment, when an outpatient prescription is output as electronic data, it is possible to use data in a format unique to the medical information provision system 1, as well as prescription data in a specific format that is publicly used. For example, electronic prescriptions proposed by the Ministry of Health, Labor and Welfare may be made available in the medical information provision system 1, and outpatient prescription data that includes this electronic prescription may be output. By making the outpatient prescription data compatible with a specific format that is publicly used, it becomes easier to link with electronic medication notebooks and medical information managed by medical institutions.

[0064] Furthermore, in the above-described embodiment, when the medical information providing system 1 is configured as a cloud-based system, the drug testing information DB server 20 may respond differently depending on the level (type of authority) of the system (medical-related system to which the terminal device 10 belongs) or user (doctor, etc.) that made an API request to the drug testing information DB server 20. For example, even if the request is made via the same API, the drug testing information DB server 20 may transmit search results whose content corresponds to the level given to the system or user that is the request source. When giving a level (authority) to a system or user that is a request source, the level can be set for each organizational unit such as a medical institution, medical facility, or department, or for each individual medical professional such as a doctor or pharmacist. Also, on the user side of the medical information providing system 1, an administrator who manages the system may be given administrator authority (for example, full access permission). This makes it possible to use a common interface via the API while providing appropriate search results that take into account the user's authority. [Explanation of symbols]

[0065] 1 medical information providing system, 10 terminal device, 11, 21 control unit, 11a prescription information acquisition unit, 11b drug testing information confirmation unit, 11c test result data acquisition unit, 11d prescription output unit, 21a drug document information acquisition unit, 21b item-specific condition setting unit, 21c exception information acquisition unit, 21d drug testing information extraction unit, 21e database management unit, 12, 22 memory unit, 22a drug document data storage unit, 22b drug testing information DB, 22c exception information storage unit, 13, 23 input unit, 14, 24 display unit, 15, 25 communication unit, 16 imaging unit, 20 drug testing information DB server, P prescription, P1 patient information area, P2 medical institution information area, P3 fixed test value area, P4 drug-specific test value area

Claims

1. A medical information providing system including a terminal device and a server configured to be able to communicate with each other, The server, A drug test information extraction means for extracting information on tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on a document showing prescription guidelines for decreased visceral function; a database generating means for generating a drug testing information database in which information on the drug testing extracted by the drug testing information extracting means and the drug are stored in association with each other; a drug testing information providing means for providing information on the drug testing of a target drug to the terminal device in response to a request from the terminal device by referring to the drug testing information database generated by the database generating means; A medical information providing system comprising:

2. The method further includes a condition setting means for setting extraction conditions for extracting information on tests of drugs that require tests when prescribed, for each item of the data of the package insert and the data of the document showing the guidelines, The medical information provision system according to claim 1, characterized in that the database generation means extracts information regarding testing of drugs that require testing when prescribed for each item of data in the package insert and the document indicating the guidelines in accordance with the extraction conditions set by the condition setting means.

3. The medical information provision system according to claim 2, characterized in that the extraction conditions set by the condition setting means define character strings set for each item of the data of the attached document and the data of the document indicating the guidelines, specific character strings that are related to the character strings, and the relationships that these character strings have.

4. The pharmaceutical testing method further includes the steps of: (a) providing a pharmaceutical testing information database for a pharmaceutical product that is not included in the pharmaceutical testing information database; The medical information provision system described in any one of claims 1 to 3, characterized in that the drug testing information providing means refers to the drug testing information database generated by the database generation means and information regarding the safety of the drug acquired by the safety information acquisition means, and provides information regarding the testing of the target drug.

5. The method further includes a drug document information acquisition means for acquiring at least one of data of package inserts of the plurality of types of drugs and data of a document showing prescription guidelines for the decline of visceral functions from a preset acquisition source, The medical information provision system described in claim 4, characterized in that the drug document information acquisition means acquires and updates at least one of data on the package inserts of the multiple types of drugs and data on documents indicating prescription guidelines regarding decreased visceral function at a predetermined timing.

6. A server in a medical information providing system including a terminal device and a server configured to be able to communicate with each other, A drug test information extraction means for extracting information on tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on a document showing prescription guidelines for decreased visceral function; a database generating means for generating a drug testing information database in which information on the drug testing extracted by the drug testing information extracting means and the drug are stored in association with each other; a drug testing information providing means for providing information on the drug testing of a target drug to the terminal device in response to a request from the terminal device by referring to the drug testing information database generated by the database generating means; A server comprising:

7. A drug test information extraction means for extracting information on tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on a document showing prescription guidelines for decreased visceral function; a database generating means for generating a drug testing information database in which information on the drug testing extracted by the drug testing information extracting means and the drug are stored in association with each other; A drug testing information providing means for providing information on testing of a target drug by referring to the drug testing information database generated by the database generating means; A medical information providing device comprising:

8. A prescription information acquisition means for acquiring prescription data relating to a patient; A drug testing information confirmation means for confirming whether or not the prescription data contains a drug that requires testing when prescribed by searching a drug testing information database that stores information on testing of the drug that requires testing when prescribed; A test result data acquisition means for acquiring test value data of a test item related to a drug that requires testing when the prescription data includes the drug; a prescription output means for outputting the prescription data acquired by the prescription information acquisition means and the test value data acquired by the test result data acquisition means together on a prescription; A medical information providing device comprising:

9. a patient information area representing information about a patient; A medical institution information area representing the medical institution that issued the prescription; A fixed test value area representing data of fixed test values ​​that are test values ​​common to multiple patients regardless of prescribed drugs; A drug-specific test value area that identifies and represents data on drug-specific test values, which are test values ​​related to drugs that require testing when prescribed among drugs prescribed to the patient, and the past trends of the patient; A medical information providing medium comprising:

10. A drug test information extraction step of extracting information regarding tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on a document showing prescription guidelines regarding decreased visceral function; a database generating step of generating a drug testing information database in which the information on the drug testing extracted in the drug testing information extracting step is stored in association with the drug; A drug testing information providing step of providing information on the testing of a target drug by referring to the drug testing information database generated in the database generating step; A medical information providing method comprising:

11. A prescription information acquisition step for acquiring prescription data relating to a patient; A drug testing information confirmation step of checking whether or not the prescription data includes a drug that requires testing when prescribed by searching a drug testing information database that stores information on testing of the drug that requires testing when prescribed; a test result data acquisition step for acquiring test value data of a test item related to a drug that requires testing when the prescription data includes the drug; a prescription output step of outputting the prescription data acquired in the prescription information acquisition step and the test value data acquired in the test result data acquisition step together on a prescription; A medical information providing method comprising:

12. On the computer, A drug test information extraction function that extracts information regarding tests of drugs that require tests when prescribed from at least one of data on package inserts of multiple types of drugs and data on documents showing prescription guidelines regarding decreased visceral function; a database generating function for generating a drug testing information database in which the information on the drug testing extracted by the drug testing information extracting function is stored in association with the drug; A drug testing information providing function that refers to the drug testing information database generated by the database generating function and provides information on the testing of a target drug; A program for realizing the above.

13. On the computer, A prescription information acquisition function that acquires prescription data related to patients; A drug testing information confirmation function for checking whether or not the prescription data contains a drug that requires testing when prescribed by searching a drug testing information database that stores information on testing of drugs that require testing when prescribed; A test result data acquisition function that acquires test value data of a test item related to a drug that requires testing when the prescription data includes the drug; a prescription output function that outputs the prescription data acquired by the prescription information acquisition function and the test value data acquired by the test result data acquisition function together on a prescription; A program for realizing the above.

Images