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 provision system, a server, a medical information provision device, a medical information provision medium, a medical information provision method, and a program. [[Background Art]]

[0002] Conventionally, systems that provide information related to drug prescription for the purpose of appropriate use of drugs are known. For example, in the proper drug use monitoring system described in Patent Document 1, important information necessary for safe use of drugs (such as interactions, side effects, contraindications, etc.) is displayed on a list screen with different display colors according to the degree (importance) that should be considered for proper use of the prescribed drug. [[Prior Art Documents]] [[Patent Documents]]

[0003] [[Patent Document 1]] Japanese Unexamined Patent Publication No. 2002-197188 [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0004] Here, some drugs require predetermined examinations at the time of prescription, and when such a drug is prescribed, a physician or pharmacist is required to pay attention to ensure that the necessary examinations are performed. In addition, in prescription review, a pharmacist is required to reliably grasp whether any of the prescribed drugs require a predetermined examination at the time of prescription, and then perform high-quality prescription review. However, the aforementioned drug use monitoring system does not identify drugs that require specific tests at the time of prescription. Therefore, physicians or pharmacists must individually check package inserts and other documents to determine whether a drug requires specific tests at the time of prescription. However, since there are tens of thousands of types of drugs, it is not easy for physicians to individually check whether a prescribed drug requires specific tests at the time of prescription or dispensing by a pharmacist. This poses problems in terms of reduced work efficiency for physicians and pharmacists, the reliability of test execution, and ensuring the quality of prescription review. Thus, with conventional technology, it was not easy to determine whether or not a prescribed drug required testing in the patient.

[0005] The objective of this invention is to make it easier to determine whether or not a prescribed drug requires testing in the patient. [Means for solving the problem]

[0006] To solve the above problems, a medical information provision system according to one aspect of the present invention is: A medical information provision system including a terminal device and a server configured to communicate, The aforementioned server, A drug testing information extraction means for extracting information on tests required for prescribing drugs from at least one of the data from package inserts of multiple types of drugs and data from documents showing prescribing guidelines for impaired organ function, A database generation means generates a drug testing information database in which information on drug testing extracted by the drug testing information extraction means is stored in association with the drug; A drug testing information providing means that, in response to a request from the terminal device, refers to the drug testing information database generated by the database generation means and provides the terminal device with information regarding the testing of the target drug, It is characterized by having the following features. [Effects of the Invention]

[0007] According to the present invention, it is possible to more easily determine whether or not a prescribed drug requires testing in the patient. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the system configuration of a medical information provision system 1 according to one embodiment of the present invention. [Figure 2] This block diagram shows the specific configuration of each device included in Medical Information Provision System 1. [Figure 3] This is a schematic diagram showing an example of a prescription (outpatient prescription) P output in this embodiment. [Figure 4] This is a schematic diagram illustrating the data contents of the drug testing information DB22b. [Figure 5] This is a flowchart showing the flow of the prescription output processing performed by terminal device 10. [Figure 6] This flowchart shows the flow of the drug testing information database generation process performed by the drug testing information database server 20. [Figure 7] This flowchart shows the flow of the drug testing information database update process executed by the drug testing information database server 20. [Figure 8] This figure shows an example of a more advanced cloud-based system configuration for the medical information provision system 1. [Figure 9] This is a schematic diagram showing the configuration when medical information provision system 1 is implemented using a single information processing device. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described below with reference to the drawings.

[0010] [System Configuration of Medical Information Provision System 1] Figure 1 is a diagram showing the system configuration of a medical information provision system 1 according to one embodiment of the present invention. In this embodiment, we will describe an example where the medical information provision system 1 is configured as a prescription issuance system that issues prescriptions (here, outpatient prescriptions). As shown in Figure 1, the medical information provision system 1 is configured to include 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 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] Terminal device 10 is composed of an information processing device such as a PC (Personal Computer). Furthermore, terminal device 10 is connected to various systems (hereinafter referred to as "hospital systems") that manage medical information such as patient and medication information within the hospital, as well as to a network such as a VPN. Terminal device 10 is operated by a physician or a person in charge of issuing prescriptions and accepts requests to issue outpatient prescriptions for patients whose medical treatment has been completed. When an operation to issue an outpatient prescription is performed, terminal device 10 acquires prescription data for that patient and sends a search request to the drug test information DB server 20 to determine whether the drugs included in the prescription data are drugs that require testing before prescription (here, this includes drugs that require dosage adjustment due to impaired organ function). For drugs that require testing before prescription, terminal device 10 acquires the patient's test value data from the hospital system and adds the test value data to the prescription data. Terminal device 10 outputs the outpatient prescription by printing the prescription data with the added test value data onto paper or by other means. Incidentally, as an output format of an out-of-hospital prescription, besides printing on a paper medium, it is also possible to output the prescription as electronic data in a predetermined format, or display it on a non-volatile display (such as electronic paper). Further, when outputting an out-of-hospital prescription, besides representing data of test items or test values as character strings, it is also possible to represent the data as one-dimensional or two-dimensional barcodes. In this case, by reading the barcode with a terminal of a patient or a pharmacy, etc., the character strings of the test items or test values can be displayed. Specifically, in consideration of the appropriateness of having test item or test value data directly exposed to the eyes of the patient or a third party, part or all of the test item or test value data can be represented as a barcode.

[0012] The drug test information DB server 20 automatically generates a drug test information database (drug test information DB) that indicates a list of drugs requiring testing at the time of prescription, by referencing, for each of various drugs, document data including data such as package insert data and prescription guideline data, the data indicating whether a drug requires testing at the time of prescription, and the reference value or reference range of the test value of the drug. For drugs that require testing at the time of prescription, a reference value (threshold) for the test value is set. When there is one reference value for the test value, with that reference value as a boundary, a larger range or a smaller range is the range suitable for prescribing 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 (that is, upper and lower threshold values are set), the range sandwiched between these threshold values is the reference range. The drug test information DB server 20 stores the reference range for drugs that require testing at the time of prescription. When the drug test information DB server 20 receives, from the terminal device 10, a search request for inquiring whether a drug is a drug that requires testing at the time of prescription, the drug test information DB server 20 searches the drug test information DB, and transmits search result data including the test items, the reference range of the test values, and the like, depending on whether the drug for which the search request was made is a drug that requires testing at the time of prescription.

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

[0014] [Specific Configuration of Terminal Device 10] As shown in Figure 2, in the medical information providing system 1, the terminal device 10 includes, as a hardware configuration, a control unit 11 that performs various arithmetic processes, a storage unit 12 that stores various types of information, an input unit 13 implemented by a keyboard, a touch panel or the like, a display unit 14 including a display, a communication unit 15 that controls communication with other devices via a network, and an imaging unit 16 that captures images. Various programs are installed in the storage unit 12 of such a terminal device 10, and the control unit 11 operates in accordance with these programs, thereby exerting functions such as an out-of-hospital prescription issuance function. Further, in such a hardware configuration of the terminal device 10, when a program for prescription output processing described later is executed, 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 are implemented in the control unit 11.

[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 instructing 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 created by a physician from an in-hospital system such as an electronic medical record system, or 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 prescribed drugs entered in an electronic medical record by a physician.

[0016] The drug testing information confirmation unit 11b checks whether each drug included in the prescription data acquired by the prescription information acquisition unit 11a is stored in the drug testing information DB as a drug that requires testing when prescribing. Specifically, the drug testing information confirmation unit 11b sends a search request to the drug testing information DB server 20, using the name of each drug included in the prescription data as the key to search the drug testing information DB. The drug testing information confirmation unit 11b then acquires the search results sent from the drug testing information DB server 20.

[0017] The test result data acquisition unit 11c refers to the search results from the drug test information DB server 20 acquired by the drug test information confirmation unit 11b. If the search request includes drugs that require testing when prescribed, the unit acquires data on the test values ​​(hereinafter referred to as "drug-specific test values") for the patient corresponding to that prescription from the hospital system. In this embodiment, when the test result data acquisition unit 11c acquires data on test values ​​from the hospital system, it also acquires data for a predetermined number of past tests (in this case, three) for that patient. However, depending on the type of test, a validity period is set for the test values, 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 pre-set test values ​​(hereinafter referred to as "fixed test values") common to all patients from the hospital system for each patient. The fixed test values ​​are selected from test values ​​related to diseases that cause serious side effects due to the prescription of medication.

[0018] The prescription output unit 11d integrates the prescription data acquired by the prescription information acquisition unit 11a with the fixed test values ​​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 patient's test value data together.

[0019] Figure 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 patient information, a medical institution information area P2 representing the medical institution that issued the prescription P, a fixed test value area P3 representing fixed test value data, and a drug-specific test value area P4 representing drug-specific test value data.

[0020] The patient information area P1 displays various information about the patient, such as the patient's name, age, gender, address, and insurance type. The medical institution information area P2 displays various information about the medical institution that issued the prescription, such as the name of the medical institution that issued the prescription and contact information. The fixed test value area P3 displays a list of test value data for test items common to all patients. Fixed test values ​​can include all or some of the following: AST, ALT, ALP, T-BIL, CRE, eGFR, Cys-C, K, CPK, WBC, HGB, PLT, SEG, ST, TSH, HbA1C, etc. It is effective to select these fixed test values ​​for side effects that cannot be detected early through subjective symptoms, and side effects where clinical test values ​​change before subjective symptoms appear.

[0021] The drug-specific test value area P4 displays a list of test value data for drugs that require testing before prescription. For example, in the drug-specific test value area P4, the drug name of the drug that requires testing before prescription, "A Tablet 17.5mg", the classification (code unit name) of the test item and the test value data "renal function {eGFR,CRE,Cys-C}", "CA 8.5", "ALB 3.5", and the symbols "-", "L", or "H" indicating the trend of the test value are shown in correspondence. In the symbols indicating the trend of the test value, "-" indicates that it is within the reference range, "L" indicates that it is below the reference range, and "H" indicates that it is above the reference range. In the prescription P in this embodiment, the trends of each test value are shown from left to right in the order of the test value from two tests ago, the test value from the previous test, and the test value from the current (most recent) test. For example, if the trend of the test value is shown as "--L", it indicates that the test value from two tests ago and the previous test was within the reference range, but the test value in the most recent test was below the reference range. In the drug-specific laboratory value area P4, if the laboratory value data for a drug requiring testing for prescription is not within the reference range, that laboratory item may be indicated in a specific way (e.g., in red or underlined). In this way, by representing the trends in past test values ​​on prescription P, it becomes possible to more accurately assess the patient's condition and prescribe medication more appropriately.

[0022] Furthermore, in prescription P of this embodiment, as a classification of test items, for some test items, a code unit name representing a combination of multiple test items is displayed. For example, the combination of the 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 classification of test items "renal function." The data of the test values ​​of the test items displayed as these combinations are displayed elsewhere, for example, as fixed test values. However, when displaying a combination of test items, it is possible to display the data of those test values ​​together. Moreover, instead of displaying the data of the test values ​​of the test items included in the combination (or together with the data of the test values), the symbols "-," "L," or "H" indicating the trend of the test values ​​mentioned above may be displayed, and if the data of the test value is not within the reference range, it is possible to display that test item in a specific form (such as in red or underlined). By using code unit names that represent combinations of test items in this way, it becomes possible to represent, for example, test items that would normally require three lines of text in a single line, allowing for efficient representation of test value data in prescription areas where space is limited. Furthermore, when representing test item or test value data with barcodes, it is possible to represent either or both of the fixed test value area P3 or the drug-specific test value area P4 with barcodes, or to represent data for specific test items or test values ​​within both the fixed test value area P3 and the drug-specific test value area P4 with barcodes.

[0023] [Specific configuration of drug testing information DB server 20] As shown in Figure 2, in the medical information provision system 1, the drug test information DB server 20 has a hardware configuration comprising a control unit 21 that performs various calculations, a storage unit 22 that stores various information, an input unit 23 implemented 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. In such a drug test information DB server 20, various programs are installed in the storage unit 22, and the control unit 21 operates according to these programs to perform functions such as generating the drug test information DB, updating the drug test information DB, or searching the drug test information DB. Furthermore, in this hardware configuration, the drug testing information DB server 20 executes programs for drug testing information DB generation processing or drug testing information DB update processing, as described later, thereby realizing a drug document information acquisition unit 21a, an item-specific condition setting unit 21b, an exception information acquisition unit 21c, a drug testing information extraction unit 21d, and a database management unit 21e in the control unit 21. In addition, the storage unit 22 of the drug testing information DB server 20 stores a drug document data storage unit 22a, a drug testing information DB 22b, and an exception information storage unit 22c.

[0024] The drug information data storage unit 22a stores data on package inserts for various drugs obtained from external databases that store data on package inserts for various drugs (such as databases of pharmaceutical manufacturers and public institutions), and data on guideline documents obtained from external databases that store data on prescription guidelines related to the decline of organ (such as kidney) function (for example, the Japanese Society of Nephrology's CKD (Chronic Kidney Disease) treatment guidelines). The data on various documents stored in the drug information data storage unit 22a is updated in accordance with any updates made to the source databases.

[0025] The drug testing information DB22b stores data on the necessary tests for prescribing various drugs mentioned in package inserts and prescribing guidelines for impaired organ function, along with the reference ranges of the test values. Figure 4 is a schematic diagram showing the data contents of the drug testing information DB22b. As shown in Figure 4, the drug test information DB22b stores the following information in association with each other: the drug code, which is a code unique to the drug; the name of the drug (trade name or generic name); the string indicating the test item extracted from the package insert or guideline (test item); the paragraph name of the package insert or guideline name from which the 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. For example, in Figure 4, the first row of the drug test information DB22b stores the results of extracting the string "hyperkalemia" from the "Contraindications" section for the drug with drug code "xxxxxx" and drug name "Solution C for Injection," extracting "K" (potassium) as the code unit and "3.5~4.8mEq / L" as the reference range for the test value. Each of these drug testing information DB22b data points is automatically generated by the drug testing information DB generation process described later. Alternatively, the contents of the automatically generated drug testing information DB22b may be finalized by approval from a specialist such as a physician or pharmacist.

[0026] The exception information storage unit 22c stores exception information regarding drug prescriptions issued sequentially by pharmaceutical manufacturers, public institutions, etc. For example, safety information not described in package inserts or guidelines (exceptional safety information), such as emergency safety information and safety alert emails issued by the Pharmaceuticals and Medical Devices Agency (PMDA), is stored in the exception information storage unit 22c as exception information. Furthermore, if the content of the exception information stored in the exception information storage unit 22c is included in the attached documents or guidelines due to updates or other reasons, the exception information stored in the exception information storage unit 22c will be deleted sequentially by the exception information acquisition unit 21c.

[0027] The drug information acquisition unit 21a acquires data on package inserts for various drugs and guideline documents from external databases that store data on package inserts for various drugs (databases of pharmaceutical manufacturers or public institutions, etc.) and external databases that store data on guidelines for prescriptions related to organ function decline. In this embodiment, the drug information acquisition unit 21a accesses the external databases at predetermined times (for example, at predetermined intervals such as once a month or when a specific instruction is entered) to acquire data on package inserts and guideline documents.

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

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

[0030] The drug testing information extraction unit 21d retrieves data from the package inserts and guideline documents for each drug stored in the drug document data storage unit 22a in order to generate the drug testing information DB. It then extracts strings representing the reference values ​​or reference ranges of the test items and test values ​​for each drug according to the item-specific extraction conditions 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 strings representing the reference values ​​or reference ranges of test items and test values ​​that are not included in the data of various documents stored in the drug document data storage unit 22a, it adds these to the string extraction results. This makes it possible to search for the reference values ​​or reference ranges of test items and test values ​​for drugs that require testing when prescribing, including safety information issued before the update of the drug testing information DB.

[0031] The drug test information extraction unit 21d then converts the extracted test items into code unit names representing the classification of the test items, based on the extraction results of the test items and reference values ​​or reference ranges for each drug. Furthermore, the drug test information extraction unit 21d associates the drug code, which is a code unique to the drug, the name of the drug (trade name or generic name), the string indicating the test item extracted in the package insert or guideline (test item), the paragraph name of the package insert or guideline name from which the 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 test information DB.

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

[0033] [Operation] Next, we will explain the operation of the medical information provision system 1. [Processing by terminal device 10]

[0034] Figure 5 is a flowchart showing the flow of prescription output processing performed by the terminal device 10. The prescription output process is initiated in response to an instruction input to execute the prescription output process 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 for patients to whom prescriptions are to be issued. In step S2, the drug testing information confirmation unit 11b obtains the names of the drugs included 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, using the name of the drug included in the prescription data as the key, to search the drug testing information DB, and obtains the search results from 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, it is possible to use information that can uniquely identify the drug as the key, in addition to the name of the drug, such as using the drug code as the key.

[0036] In step S4, the test result data acquisition unit 11c refers to the search results from the drug test information DB server 20 acquired by the drug test information confirmation unit 11b and determines whether or not each drug for which a search request was made contains a drug that requires testing when prescribing. If any of the drugs for which a search request was made include drugs that require testing before prescription, the result in step S4 is determined to be YES, and the process proceeds to step S5. On the other hand, if none of the drugs for which a search request was made require testing before prescribing, the result is determined as NO in step S4, and the process proceeds to step S6.

[0037] In step S5, the test result data acquisition unit 11c acquires drug-specific test value data for the medications that require testing when prescribing for the patient corresponding to the prescription from the hospital system and adds it to the prescription data.

[0038] In step S6, the drug testing information confirmation unit 11b determines whether the search of the drug testing information database has been completed for all drugs included in the prescription data. If the drug testing information database search is completed for all drugs included in the prescription data, the result is determined as YES in step S6, and the process proceeds to step S7. On the other hand, if the drug testing information database search has not been completed for all the drugs included in the prescription data, the result will be NO in step S6, and the process will proceed to step S2. In step S7, the test result data acquisition unit 11c acquires fixed test value data for the patient corresponding to the prescription from the hospital system and adds it to the prescription data. In step S8, the prescription output unit 11d integrates the prescription data acquired by the prescription information acquisition unit 11a with the fixed test values ​​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 is completed.

[0039] Through this process, if a prescription includes medications that require testing before prescription, the necessary test items and reference ranges for those test values ​​are retrieved from the drug testing information database. Simultaneously, the test value data for those test items is retrieved from the hospital's internal system and can be presented together with the prescription for the patient in question. In other words, the medical information provision system 1 makes it easier to confirm whether or not a prescribed drug requires testing in the patient. Therefore, according to the medical information provision system 1, it becomes possible to more reliably perform the necessary tests for drugs that require testing when prescribing. Furthermore, since medications requiring testing are indicated on the prescription, and the patient's test results are also shown, the pharmacist reviewing the prescription can clearly determine whether or not it is appropriate to prescribe that medication. This provides pharmacists with an opportunity to raise concerns with healthcare institutions and makes the basis for such concerns more reliable. Therefore, according to the medical information provision system 1, it is possible to improve the quality of prescription review by pharmacists (improvement of pharmaceutical management).

[0040] [Processing by Drug Test Information DB Server 20] Figure 6 is a flowchart showing the flow of the drug testing information database generation process performed by the drug testing information database 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 it in the drug testing information DB update process described later.

[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 guideline documents from external databases that store data on package inserts for various drugs (databases of pharmaceutical manufacturers, public institutions, etc.) and external databases that store data on prescription guidelines related to organ function decline. In step S12, the item-specific condition setting unit 21b sets extraction conditions for extracting strings of reference values ​​or reference ranges for each drug, targeting the package insert and guideline documents, for each item in the package insert and guideline (such as dosage, administration, or contraindications). Alternatively, the extraction conditions for extracting strings of reference values ​​or reference ranges for each drug may be set in advance and saved as a setting file, and this setting file may be read.

[0042] In step S13, the drug testing information extraction unit 21d retrieves data from the package inserts and guideline documents for 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 test information extraction unit 21d extracts strings of reference values ​​or reference ranges for test items and 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 test information extraction unit 21d appropriately refers to the exception information stored in the exception information storage unit 22c, and if there are strings of reference values ​​or reference ranges for test items and test values ​​that are not included in the data of various documents stored in the drug document data storage unit 22a, it adds these to the string extraction results.

[0043] In step S15, the drug test information extraction unit 21d determines whether or not the strings of the test items and the reference values ​​or reference ranges for the test values ​​for each drug have been extracted. If the strings for the test items and the reference values ​​or reference ranges for each drug are extracted, the result is determined to be YES in step S15, and the process proceeds to step S16. On the other hand, if the reference values ​​or reference ranges for the test items and test values ​​for each drug are not extracted, the result is determined as NO in step S15, 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 test information extraction unit 21d associates the drug code, which is a code unique to the drug, the name of the drug (trade name or generic name), the string indicating the test item extracted from the package insert or guideline (test item), the paragraph name of the package insert or guideline name from which the 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 test information DB.

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

[0046] This process allows for the extraction of drug testing requirements from package inserts or guideline documents, and the automatic generation of a drug testing information database including the test items and reference ranges for those test values. Therefore, compared to manually generating the drug testing information database, it is possible to reduce the time and effort required to generate the database, and to efficiently generate a more accurate database.

[0047] Next, we will explain the drug testing information database update process performed by the drug testing information database server 20. Figure 7 is a flowchart showing the flow of the drug testing information database update process executed by the drug testing information database server 20. The drug testing information database update process is initiated at predetermined intervals or other pre-set times.

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

[0049] In step S22, the drug document information acquisition unit 21a executes the drug test information DB generation process. In step S23, the exception information acquisition unit 21c deletes the contents of the exception information that have been added to the attached documents or guidelines due to updates, etc., from the exception information storage unit 22c. After step S23, the drug test information database update process is completed. This process updates the drug testing information database to the latest state, enabling the generation of more appropriate prescriptions.

[0050] [Example 1] In the above-described embodiment, the medical information provision system 1 can be realized as a more advanced cloud-based system. Figure 8 shows an example of a more advanced cloud-based system configuration for the medical information provision system 1. As shown in Figure 8, the drug testing information DB server 20 is configured as a virtual server implemented on the cloud, and an API (Application Program Interface) can be provided to accept search requests for whether or not a drug requires testing when prescribing it. In this case, it becomes possible to easily use the functions of the drug testing information DB server 20 from various terminal devices 10 with different platforms, making the medical information provision system 1 more user-friendly for many users. Furthermore, if the drug testing information DB server 20 is implemented as a virtual server 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 Figure 8, the functions of the drug testing information DB server 20—specifically, the function for automatically generating the drug testing information DB, the function for searching the drug testing information DB, and the function for maintaining the drug testing information DB (such as updating the drug testing information DB)—can each be configured using different virtual servers. This effectively separates the multiple functions provided by the drug testing information DB server 20, allowing for flexible operation of the drug testing information DB server 20, such as running only the functions that are used and shutting down functions that are not used. Furthermore, if the drug testing information DB server 20 is a virtual server implemented on the cloud, it is possible to configure the entire drug testing information DB server 20, or some of its functions, in a redundant manner using multiple virtual servers. For example, in the functionality of the drug testing information DB server 20, the function of searching the drug testing information DB can be configured to be duplicated across multiple virtual servers 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. This allows the functional configuration to be appropriately changed according to the processing capacity required of the drug testing information DB server 20 and operational considerations. Furthermore, to change the processing capacity required for the drug testing information DB server 20, it is possible to duplicate the entire drug testing information DB server 20 or some of its functions using multiple virtual servers, or to change the specifications of the virtual servers.

[0051] [Differentiation 2] In the above-described embodiment and modification 1, a cloud-based medical information provision 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 a drug requires testing when prescribing. Alternatively, by providing the drug testing information database in the terminal device 10, the functions of the medical information provision system 1 may be realized with a single information processing device (i.e., realized as a standalone system). In this case, the terminal device 10 should be equipped with the functions of the drug document information acquisition unit 21a, item-specific condition setting unit 21b, exception information acquisition unit 21c, drug test information extraction unit 21d, drug document data storage unit 22a, drug test information DB 22b, and exception information storage unit 22c of the drug test information DB server 20.

[0052] Figure 9 is a schematic diagram showing the configuration when the medical information provision system 1 is implemented using a single information processing device. In Figure 9, the terminal device 10 is equipped with the main functional configuration of the drug testing information DB server 20 shown in Figure 2, thereby enabling the terminal device 10 to perform the functions of the medical information provision system 1 on its own. With the configuration shown in Figure 9, a single device can search for drugs that require testing before prescribing. Therefore, without using a network, doctors and pharmacists can easily check whether a prescribed drug contains drugs that require testing, and if so, the test items and reference ranges for the test values.

[0053] As described above, the medical information provision system 1 according to this embodiment includes a drug test information DB server 20, which comprises a drug test information extraction unit 21d (drug test information extraction means, database generation means) and a database management unit 21e (drug test information provision means). The drug testing information extraction unit 21d extracts information regarding tests for drugs that require testing when prescribing, from at least one of the data from package inserts for multiple types of drugs and data from documents showing prescribing guidelines for impaired organ function. Furthermore, the drug testing information extraction unit 21d generates a drug testing information database in which the extracted drug testing information and the drug itself are stored in association. Furthermore, the database management unit 21e, in response to a request from the terminal device 10, refers to the generated drug testing information database and provides the terminal device 10 with information regarding the testing of the target drug. This configuration makes it possible to extract drugs that require testing before prescription from the data in package inserts or guideline documents, and to automatically generate a drug testing information database that includes the test items and reference ranges for the test values. Then, using this generated drug testing information database, it becomes easier to confirm whether or not a prescribed drug requires testing for the patient.

[0054] Furthermore, the medical information provision system 1 includes an item-specific condition setting unit 21b in the drug test information DB server 20. The item-specific condition setting unit 21b sets extraction conditions for each item of the package insert data and guideline data, for extracting information on tests required for prescription drugs. Furthermore, the drug testing information extraction unit 21d extracts information regarding drug testing required for prescription, for each item of data from the package insert and the document showing the guidelines, according to the extraction conditions set by the item-specific condition setting unit 21b. This configuration allows for the setting of extraction criteria for each item in the attached document and guidelines, making it possible to set more appropriate extraction criteria that reflect the characteristics of the description in each item.

[0055] Furthermore, the extraction criteria define strings set for each item of data in the attached document and the document showing the guidelines, specific strings that are related to those strings, and the relationships between these strings. This configuration makes it possible to automatically and appropriately extract the reference values ​​or reference ranges for test items or test values ​​included in the data of the attached documents and guidelines.

[0056] Furthermore, the medical information provision system 1 is equipped with an exception information acquisition unit 21c (safety information acquisition means). The exception information acquisition unit 21c acquires information regarding the safety of drugs that are not included in the drug testing information database. Furthermore, the drug testing information extraction unit 21d refers to the drug testing information database and drug safety information to provide information regarding the testing of the target drug. This configuration makes it possible to search for the test items and reference values ​​or reference ranges of test values ​​for drugs that require testing before prescription, including safety information issued before the update of the drug testing information database.

[0057] Furthermore, the medical information provision system 1 is equipped with a drug document information acquisition unit 21a (drug document information acquisition means). The drug information acquisition unit 21a acquires data from at least one of the following sources: package inserts for multiple types of drugs and documents providing guidelines for prescriptions related to impaired organ function. Furthermore, the drug information acquisition unit 21a acquires and updates data from package inserts for multiple types of drugs and data from documents showing prescription guidelines related to impaired organ function at a predetermined timing. This configuration ensures that the contents of the drug testing information database are updated to the latest state, enabling the generation of more appropriate prescriptions.

[0058] Furthermore, 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 represents information about the patient. The medical institution information area P2 represents the medical institution that issued the prescription. The fixed laboratory value region P3 represents data for fixed laboratory values ​​that are common to multiple patients regardless of the prescribed medication. The drug-specific laboratory value area P4 displays data on drug-specific laboratory values, which are related to drugs prescribed to a patient that require testing at the time of prescription, while identifying the patient's past trends. This configuration allows for a more accurate assessment of the patient's condition and enables more appropriate medication prescriptions.

[0059] Furthermore, the present invention is not limited to the embodiments described above, and any modifications, improvements, etc., that can achieve the objectives of the present invention are included in the present invention. For example, in the above-described embodiment, the prescription output by the medical information provision system 1 was described as an outpatient prescription, but it is not limited to this. That is, the medical information provision system 1 can output in-hospital prescriptions, and it can also be applied to various medical information provision media other than prescriptions that output the prescribed medications.

[0060] Furthermore, in the embodiments described above, the reference range data for test values ​​related to drugs that require testing when prescribing were described as being stored in a drug test information database, but this is not limited to that. For example, the reference range data for test values ​​related to drugs that require testing when prescribing may be stored in a hospital system or the like, and when the test result data acquisition unit 11c acquires the test value data, it may also acquire the reference range for the test value.

[0061] Furthermore, in the above-described embodiment, prescription P was explained as showing the changes in each test value from left to right, in the order of the test value from two tests ago, the test value from the previous test, and the current (most recent) test value, but it is not limited to this. In other words, the drug-specific laboratory value area P4 only needs to clearly show the patient's laboratory value trends. For example, past laboratory value trends can be visually identified using upward-right arrows for increasing trends, downward-right arrows for decreasing trends, and rightward arrows for maintaining trends. Furthermore, past laboratory value trends can be represented as line graphs, and the relative relationship of past laboratory values ​​to the reference range can be represented by the position of predetermined symbols (such as dots or asterisks).

[0062] Furthermore, while the Pharmaceuticals and Medical Devices Agency (PMDA) was used as an example of a source for obtaining exceptional information regarding drug prescriptions in the embodiments described above, the method is not limited to this. In other words, it is possible to obtain exceptional information issued by public institutions in Japan or abroad that are similar to the Pharmaceuticals and Medical Devices Agency.

[0063] Furthermore, in the above-described embodiment, when outputting outpatient prescriptions as electronic data, it is possible to use data in a proprietary format of the medical information provision system 1, or to use prescription data in a specific format that is publicly used. For example, it is possible to make electronic prescriptions intended by the Ministry of Health, Labour and Welfare usable in the medical information provision system 1, and output outpatient prescription data that includes this electronic prescription. By using outpatient prescription data that corresponds to a specific format that is publicly used, it becomes possible to more easily link with electronic medication records and medical information managed by medical institutions.

[0064] Furthermore, in the above-described embodiment, if the medical information provision system 1 is configured as a cloud-based system, the drug testing information DB server 20 may provide different responses 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 the API request to the drug testing information DB server 20. For example, even with the same API request, the drug testing information DB server 20 may send search results that correspond to the level granted to the system or user making the request. When granting levels (permissions) to the requesting system or user, levels can be set based on organizational units such as medical institutions, medical facilities, or departments, or on individual medical professionals such as doctors or pharmacists. Furthermore, on the user side of Medical Information Provision System 1, administrator privileges (e.g., full access permission) may be set for the administrator who manages the system. This allows for the use of a standardized interface via APIs, while also providing appropriate search results that take user permissions into consideration. [Explanation of Symbols]

[0065] 1 Medical information provision system, 10 Terminal device, 11,21 Control unit, 11a Prescription information acquisition unit, 11b Drug test 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 test information extraction unit, 21e Database management unit, 12,22 Storage unit, 22a Drug document data storage unit, 22b Drug test information DB, 22c Exception information storage unit, 13,23 Input unit, 14,24 Display unit, 15,25 Communication unit, 16 Imaging unit, 20 Drug test 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 drug information acquisition means that accesses a database containing data on documents related to drugs issued by drug manufacturers and obtains data on such documents related to drug prescriptions, A prescription data acquisition means for acquiring data representing the prescriptions of the target patient, A means for acquiring test result data that acquires data representing the test results of the aforementioned target patient, An information output means that, based on data of documents relating to the said drugs obtained from a database storing data of documents relating to the said drugs, determines whether the drugs shown in the prescription include drugs that require testing before prescription, which should be determined in advance based on data representing the patient's test results to determine whether the drug can be taken, and if drugs requiring testing before prescription are included, adds data representing the patient's test results necessary for prescribing the said drugs to the data representing the prescription and outputs it. Equipped with, The aforementioned information output means is A medical information provision system characterized in that, in data representing the past test results of the aforementioned target patient, if a test value related to a drug requiring testing for prescription is not within the reference range, the system identifies that the test value is not within the reference range and adds data representing the patient's test results necessary for prescribing the drug to the data representing the prescription and outputs it.

2. The medical information provision system according to Claim 1, characterized in that the test result data acquisition means acquires data representing the test results of the target patient when the drugs indicated in the prescription include drugs that require testing at the time of prescription.

3. The information output means outputs data representing the examination results of the target patient, Fixed test value data, which are common test values ​​for multiple patients regardless of the prescribed medication, Among the medications prescribed to the aforementioned patient, the drug-specific laboratory data, which are the laboratory values ​​related to the medications that require testing at the time of prescription, A medical information provision system according to claim 1 or 2, characterized in that it outputs [something].

4. Based on the data of documents relating to the said drugs obtained from a database storing data of documents relating to the said drugs, a drug testing information database is formed in which information on tests for drugs that require testing when prescribing is associated with the drugs themselves. The medical information provision system according to any one of claims 1 to 3, wherein the data that the information output means can obtain by accessing the drug testing information database differs depending on the type of permission set for the user or system that accessed the drug testing information database.

5. The medical information provision system according to any one of claims 1 to 4, characterized in that the information output means prints data on paper media which is obtained by adding data representing the patient's test results necessary for prescribing the drug to the data representing the prescription.

6. A method of providing medical information that is implemented by a medical information provision system, A drug information acquisition step involves accessing a database containing data on documents related to drugs issued by drug manufacturers, and obtaining data on such documents related to drug prescriptions. A prescription data acquisition step to obtain data representing the prescriptions of the target patient, A step of acquiring test result data to acquire data representing the test results of the aforementioned target patient, An information output step in which, based on data of documents relating to the said drugs obtained from a database storing data of documents relating to the said drugs, determines whether the drugs shown in the prescription include drugs that require testing before prescribing, which should be determined in advance based on data representing the patient's test results to determine whether the drug can be taken, and if drugs requiring testing before prescribing are included, adds data representing the patient's test results necessary for prescribing the said drugs to the data representing the prescription and outputs it; Includes, In the aforementioned information output step, A method for providing medical information, characterized in that, in data representing the past test results of the aforementioned target patient, if a test value related to a drug requiring testing for prescription is not within the reference range, the method identifies that the test value is not within the reference range and adds data representing the patient's test results necessary for prescribing the drug to the data representing the prescription and outputs it.

7. The computers that make up the medical information provision system, A drug information acquisition function that accesses a database containing data on drug-related documents issued by drug manufacturers and obtains data on said drug-related documents related to drug prescriptions, A prescription data acquisition function that obtains data representing the prescriptions of the target patient, A function for acquiring test result data that acquires data representing the test results of the aforementioned target patient, Based on the data of documents relating to the said drugs obtained from a database storing data of documents relating to the said drugs, the system determines whether the drugs listed in the prescription include drugs that require testing before prescription, which should be determined in advance based on data representing the patient's test results to determine whether the drug can be taken. If drugs requiring testing before prescription are included, the system outputs data representing the patient's test results necessary for prescribing the said drugs, adding this data to the data representing the prescription. To make it happen, The aforementioned information output function is, A program characterized by, in data representing the past test results of the aforementioned target patient, if a test value related to a drug requiring testing for prescription is not within the reference range, identifying that the test value is not within the reference range, and adding data representing the patient's test results necessary for prescribing the drug to the data representing the prescription and outputting it.

Images