JP6433133B2 - Medical data management program and medical data management system - Google Patents

Description

  The present invention relates to a medical data management program and a medical data management system that integrate and manage data of a plurality of databases stored in different formats.

  Conventionally, a system ID capable of uniquely identifying a patient to be examined is presented in Japanese Patent Application Laid-Open No. 2009-266077 as an integrated management of electronic medical records provided separately by a plurality of hospitals. The electronic medical record information that is obtained through the electronic medical record including the medical examination contents of the patient and the electronic medical record information in which the electronic medical record information item in the acquired electronic medical record is adjusted is associated with the system ID to generate the electronic medical record information. An electronic medical record browsing request stored in the medical chart integrated DB and presenting a keyword is received via the communication network, the electronic medical chart integrated DB is referred to, the electronic medical chart integrated information matching the received keyword is searched, and the searched electronic The electronic medical record information included in the integrated medical record information is sorted into predetermined categories, and the sorted electronic medical record information is reviewed. Electronic medical record management server sending to the requesting terminal device is disclosed.

JP 2009-266077 A

  However, in the technique disclosed in Patent Document 1, when integrating electronic medical chart data in different systems, each data is verified, a certain rule is created, and data conversion work is performed based on the rule. It had to be stored again in one integrated database. In such a case, since the amount of medical data is enormous, it is not realistic to target all items of data from the viewpoint of labor and money, and in reality, only a part of the enormous amount of data is converted. There were many things. In addition, a great deal of labor and money are required in the conversion work of a part of this data.

  In addition, when using the integrated data, if the data is required beyond the scope of items originally assumed, the original data needs to be re-acquired and requires a lot of labor and money. It was necessary to perform the conversion work again. Furthermore, electronic medical record data is increasing year by year, and long-term data is stored in a single integrated database, and when searching or extracting statistical information from it, the database response time will increase. There were also challenges.

  The present invention has been made in view of the above points, and even if different types of databases exist due to changes in the manufacturers of electronic medical records and various departmental systems and the system itself, these integrated databases are created. It is an object of the present invention to provide a medical data management program and a medical data management system that are unnecessary and can perform data search, statistical processing, and inquiry promptly.

The medical data management program of the present invention is
In a clinical data management program that directly searches and manages multiple databases stored in different formats,
Computer
In order to collectively manage different tables provided for each database for the same purpose as one logical homogeneous target, the homogeneous target ID and the homogeneous target ID for identifying the homogeneous target for each homogeneous target A table for storing the display name corresponding to the table, and a table for a homogeneous target comprising a column for storing a target ID for identifying the table associated with the homogeneous target ID ;
In order to collectively manage the columns having the same meaning in the plurality of tables as the same target as a logical same type column, the same type column ID for specifying the same type column for each of the same type columns, and A table for a homogeneous column comprising a column for storing a display name corresponding to the homogeneous column ID, and a column for storing an item name of a column having the same meaning in the table associated with the homogeneous column ID ;
A table for data conversion rules for managing conversion rules for converting real data of different formats stored in a plurality of columns that are the same type columns to the same type data for integration;
When a search condition based on the homogeneous target, the homogeneous column, and the homogeneous data is input, the search target is based on the homogeneous target table, the homogeneous column table, and the data conversion rule table. A search control unit that identifies the table provided for each database and a column having the same meaning in the table, and retrieves the actual data from a plurality of the databases;
A conversion control unit that converts the searched real data into the same kind of data based on the table for the same kind column and the table for the data conversion rule, and converts it into view data as display data,
A view storage unit for temporarily storing the view data;
A display unit for displaying the view data stored in the view storage unit as visual information;
It is characterized by functioning

  According to the medical care data management program of the present invention, different tables provided for each database for the same purpose can be collectively managed as a single homogeneous target using the homogeneous target table. The same purpose includes, for example, those related to disease names, prescriptions, and injections, and these same purpose tables have different table names for each database. The same target table manages these different tables together with a superordinate concept of the same purpose.

  In addition, the same kind column can be managed as one logical same kind column by using the same kind column table in a plurality of tables set as the same kind target. The column having the same meaning is, for example, a column indicating a disease name, a column indicating a medical department, a column indicating a doctor in charge, or the like. A column indicating dosage, a column indicating usage, etc., and in a table relating to injection, there are a column indicating a drug name, a column indicating a dosage, a column indicating an administration method, and the like. These columns having the same meaning have different column names for different database tables. The table for the same type column manages a plurality of columns having different column names together by a superordinate concept of the same meaning.

  In addition, the data conversion rule table can manage conversion rules for converting different types of real data stored in a plurality of columns of the same type into the same type of data for integration. This is because the same-type column having the same meaning managed by the table for the same-type column differs in data format and data contents including the column name depending on the table for each database. For example, in the case of a column indicating the gender of a patient, a table of a certain database has a column name “seibeta”, a data format “number”, data “0” or “1”, and a table of another database has a column name “sex”. ", Data format" character ", data" M "or" F ". The table for data conversion rules manages the rules for converting the data format and data of the actual data of these columns into the data format and data of the same kind of data for integration.

  In addition, when a desired search condition is input by the search control unit, from the columns of a plurality of database tables to the database based on the same target table, the same column table, and the data conversion rule table. Stored actual data can be retrieved. When a desired search condition is input, the database, table, column, and data to be searched are specified from the table for the same target, the table for the same column, and the table for the data conversion rule. Search for the right data. Note that the data retrieved at this time is actual data that has been retrieved from a plurality of databases.

  In addition, the conversion control unit converts the actual data into the same kind of data based on the table for the same kind column and the table for the data conversion rule. For example, the column name “seibeta”, the data format “number”, the data “0” or “1”, and the column name “sex”, the data format “character”, the data “M” or “F”, which are the actual data described above. Are converted into column names “sex”, data format “character”, data “male” or “female”, which are examples of similar data. Note that the same kind of data refers to data that has been converted to a predetermined column name, data format, and data for the integration of the actual data, or the conversion process is performed, but the same kind of data is the same as the actual data and no conversion is required. Intended data. Further, the conversion control unit can use the converted similar data as it is or as view data as display data in a predetermined format.

  The view storage unit temporarily stores the view data created by the conversion control unit. The view storage unit does not need to store all the data retrieved and converted from a plurality of databases for a long period, and only needs to be able to temporarily store view data. Therefore, it is only necessary to have a capacity capable of storing necessary view data each time, and the system can be simplified and the cost can be reduced. The display unit displays the view data stored in the view storage unit in a predetermined format as visual information.

A preferred example of the medical data management program of the present invention is:
The plurality of databases are different databases based on different generations of medical information systems.

A preferred example of the medical data management program of the present invention is:
The plurality of databases are different databases based on different medical information systems existing in parallel.

  According to these preferable examples of the medical data management program of the present invention, different databases can be integrated and managed by different generations of medical information systems or by different medical information systems existing in parallel. Thus, even if the manufacturer of the medical information system is changed, or even medical institutions located at remote locations, data of a plurality of databases can be integrated to perform data search or the like.

In a medical data management system that directly searches and manages multiple databases stored in different formats,
In order to collectively manage different tables provided for each database for the same purpose as one logical homogeneous target, the homogeneous target ID and the homogeneous target ID for identifying the homogeneous target for each homogeneous target A table for storing the display name corresponding to the table, and a table for a homogeneous target comprising a column for storing a target ID for identifying the table associated with the homogeneous target ID ;
In order to collectively manage the columns having the same meaning in the plurality of tables as the same target as a logical same type column, the same type column ID for specifying the same type column for each of the same type columns, and A table for a homogeneous column comprising a column for storing a display name corresponding to the homogeneous column ID, and a column for storing an item name of a column having the same meaning in the table associated with the homogeneous column ID ;
A table for data conversion rules for managing conversion rules for converting real data of different formats stored in a plurality of columns that are the same type columns to the same type data for integration;
When a search condition based on the homogeneous target, the homogeneous column, and the homogeneous data is input, the search target is based on the homogeneous target table, the homogeneous column table, and the data conversion rule table. A search control unit that identifies the table provided for each database and a column having the same meaning in the table, and retrieves the actual data from a plurality of the databases;
A conversion control unit that converts the searched real data into the same kind of data based on the table for the same kind column and the table for the data conversion rule, and converts it into view data as display data,
A view storage unit for temporarily storing the view data;
A display unit for displaying the view data stored in the view storage unit as visual information;
It is characterized by providing.

  According to the medical data management system of the present invention, the same operational effects as the medical data management program can be achieved for the reasons described above.

  As described above, according to the present invention, there is no need to create these integrated databases even if different types of databases exist due to changes in the manufacturers and types of electronic medical records and various department systems. In addition, it is possible to provide a medical data management program and a medical data management system that can quickly retrieve data, perform statistical processing, and make inquiries.

It is a functional block diagram which shows the structure of the medical treatment data system which concerns on one Embodiment of this invention. It is a figure explaining the different table provided for the same objective in a different medical information system. It is a figure explaining the concept of a homogeneous target and a homogeneous row. It is a figure explaining the table for homogeneous targets. It is a figure explaining the table for homogeneous columns. It is a figure explaining the table for data conversion rules. It is a figure explaining a medicine name master table and a target master table. It is a figure explaining the process in which view data are produced by the search and conversion of data. It is a flowchart explaining the whole process which searches and converts data from a plurality of databases. It is a flowchart explaining the process of the input of search conditions, and the acquisition of the information required in order to search real data. It is a flowchart explaining the process of search of real data. It is a flowchart explaining the process which converts real data into the same kind data. It is a flowchart explaining the process of creation of view data.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of a medical data management system of the present invention will be described in detail with reference to the accompanying drawings. The medical data management program according to the present invention is for causing a computer to execute the medical data management system according to the present invention.

  FIG. 1 is a functional block diagram showing a configuration of a medical data system according to an embodiment of the present invention, FIG. 2 is a diagram for explaining different tables provided for the same purpose in different medical information systems, and FIG. FIG. 4 is a diagram for explaining the concept of targets and homogeneous columns, FIG. 4 is a diagram for explaining tables for homogeneous species, FIG. 5 is a diagram for explaining tables for homogeneous columns, and FIG. 6 is a diagram for explaining tables for data conversion rules FIG. 7 is a diagram for explaining a drug name master table and a target master table.

  First, the outline | summary of the medical treatment data management system 1 of this embodiment is demonstrated. As shown in FIG. 1, different databases 100 and 200 are connected to the medical data management system 1 of the present embodiment by different generations of medical information systems or by different medical information systems existing in parallel. As tables provided in the different databases 100 and 200, for example, as shown in FIG. 2A, the database of the medical information system A manages a disease name order table for the purpose of managing disease names and prescriptions. A prescription order table is provided for the purpose. As shown in FIG. 2B, the medical information system B database also includes a medical record record name table for searching for the purpose of managing disease names and a prescription table for searching for the purpose of managing prescriptions. Is provided. In these tables, even if the tables have the same purpose, the table names are different because the medical information systems are different.

  In addition, even if the columns have the same meaning in the table, their column names, data formats, and data contents are different. For example, in the case of a column indicating the gender of a patient, the disease name order table and the prescription order table of the medical information system A shown in FIG. 2 (A) include a column name “seibeta”, a data format “number”, and data “0”. Or “1”, and the medical record system for search disease name table and the prescription table for search of the medical information system B shown in FIG. 2B include a column name “sex”, a data format “character”, data “M”, or “F” or the like. As described above, if the medical information systems are different, even if the table has the same purpose and the column has the same meaning, the data format and the data contents are different, and the search cannot be performed collectively as it is.

  The medical data management system 1 according to the present embodiment collectively manages different tables having the same purpose but as logical one homogeneous target, and columns having the same meaning as homogeneous columns. Here, as an example, a homogeneous target for the purpose of a disease name and a homogeneous column related to the homogeneous target, and a homogeneous target for the purpose of prescription and a homogeneous column related to the homogeneous target will be described. 3A, the disease name order table of the medical information system A and the medical record disease name table for search of the medical information system B are collected. 3B, the prescription order table of the medical information system A and the search prescription table of the medical information system B are collected.

  In FIGS. 3A and 3B, the same kind of columns for description are described above these tables. This kind of column is a group that manages the same meaning columns in a plurality of tables that are the same kind of target as one logical column. As shown by the arrow line in the figure, the same kind column “Patient ID” manages the columns of “kanjyaID” and “patient number” together as a column having the same meaning, and the same type column “gender” makes the columns of “sebetu” and “sex” have the same meaning They are managed together. In addition, if the same kind target is different, the contents of the same kind row are also different.

  Also, the data format and data of columns arranged as the same type of column differ if the table is different. These different data formats and data are converted into data for integration using data conversion rules.

  Returning to FIG. 1, the configuration of the medical data management system 1 of the present embodiment will be described. As shown in FIG. 1, the medical data management system 1 of this embodiment includes an input unit 10, a storage unit 20, a control unit 11, and a display unit 14.

  Note that the original data stored in the plurality of connected databases 100 and 200, or a column that is retrieved from the plurality of databases 100 and 200 but is not subjected to conversion processing and remains in the original data state. The name and data are called actual data for convenience. Data obtained by converting the column name, data format, and data contents for integration of actual data, or data that has been converted but does not need to be converted is referred to as homogeneous data.

  The input unit 10 includes input devices such as a known keyboard, mouse, touch panel, and trackball, and a desired search condition can be input from these devices.

  The storage unit 20 is composed of a known hard disk drive, a semiconductor storage device, and the like, and includes a homogeneous target table 21, a homogeneous column table 22, a data conversion rule table 23, various master tables 24, and a view. A storage unit 25 is provided. In addition, the storage unit 20 stores a medical data management program and an operating system that are executed to realize the medical data management system 1 of the present embodiment, and other storage areas necessary for the operation of the computer are provided.

  The homogeneous target table 21 is a database 100 and 200 stored in different formats of different medical information systems. The different tables provided for each database for the same purpose are logically combined as one homogeneous target. This is for management, and includes a homogeneous target table shown in FIG. 4A and a homogeneous target management table shown in FIG. The homogeneous target table has items (columns) of “homogeneous target ID” and “display name”, and the homogeneous target management table has items of “homogeneous target ID” and “target ID”. The same target table is divided into two types, the same target table and the same target management table, to facilitate management. The same target table may be combined into one table, and other items Three or more tables may be added.

  The same-type target ID provided in the item of the same-type target table is an ID set for each table of the same purpose, and the display name sets a name representing the purpose as a superordinate concept. Here, the same-type target ID “1” is set to the display name “disease name”, and “2” is also set to “prescription”.

  Moreover, the target ID provided in the item of the same type target management table is an ID for specifying a table provided in each of a plurality of databases. That is, the homogeneous target set to the homogeneous target ID “1” by the homogeneous target table and the homogeneous target management table is a target table indicating “disease name”, and the table for this disease name is the target ID “A−”. It can be seen that the tables are indicated by “1” and “B-5”. Similarly, it can be seen that the same target ID “2” is intended for “prescription”, and the table is a table indicated by target IDs “A-8” and “B-3”.

  The same-type column table 22 manages columns having the same meaning among a plurality of tables set as the same-type target as one logical same-type column. The same-type column table shown in FIG. And the same kind column management table shown in FIG. The homogeneous column table includes items of “homogeneous column ID”, “same species target ID”, “display name”, and “data format”, and the homogeneous column management table includes “same column ID”, “target ID”, “column name”, and so on. It has items of “data conversion” and “data conversion rule ID”. Note that the table for the same kind column is divided into two parts, the same kind column table and the same kind column management table, in order to facilitate management, even if they are combined into one table or three or more tables. It may be divided into

  The homogeneous column ID provided in the item of the homogeneous column table is an ID set for each homogeneous column in which columns having the same meaning are collected. The same-type target ID is an ID set for each table for the same purpose as described above. The display name is a column name that is set for each homogeneous column ID, and is displayed when displaying data of a column that is a homogeneous column. Similarly, the data format is a data format that is set for each kind column ID and is used when displaying data in the same kind column. Here, the homogeneous target ID “1”, which is a table for disease names, has homogeneous column IDs “1” to “6” as its items, and a display name and a data format are set for each homogeneous column ID. ing. That is, the homogeneous column ID “1” is for collecting columns having the meaning of “patient ID” among the columns of the table of the homogeneous target ID “1”, and its data format is “numeric”. The same kind column ID “2” is for collecting the columns having the meaning of “sex” among the columns of the table of the same kind target ID “1”, and it can be seen that the data format is “character type”. Similarly, the same kind target ID “2” which is a table indicating the prescription includes the same kind column IDs “7” to “12” in the item, and a display name and a data format are set for each of the same kind column IDs. I understand that.

  The same kind column ID and target ID provided in the item of the same kind column management table are as described above. The column name item is for specifying a column having the same meaning in the table specified by the target ID, and the column name of actual data actually used for the column is stored. The data conversion item stores whether or not the actual data stored in the specified column needs to be converted. If the data is “Y”, data conversion is necessary. If “N”, the data conversion is necessary. Data conversion is not necessary. The item of data conversion rule ID stores an ID for specifying a rule how to convert actual data that needs to be converted into the same kind of data. Here, it can be seen that the data of the same kind column ID “2”, “8”, “11” needs to be converted. For example, the columns grouped by the same kind column ID “2” are columns represented by the column names “seibeta” and “sex” in the tables indicated by the target IDs “A-1” and “B-5”. It is understood that the data stored in these columns needs to be converted, and the data conversion rule IDs are “1” and “2”.

  The data conversion rule table 23 manages conversion rules for converting real data of a plurality of columns that are of the same type into the same type of data for integration. Here, the data conversion shown in FIG. A rule table and a data conversion rule detail table shown in FIG. The data conversion rule table has items of “data conversion rule ID” and “name”, and the data conversion rule detail table has items of “data conversion rule ID”, “kind data”, and “actual data”. The reason why the data conversion rule table is divided into two, a data conversion rule table and a data conversion rule detail table, is to make management easier. You may divide into the above table.

  The data conversion rule ID provided in the item of the data conversion rule table is for specifying the rule how to convert the actual data that needs to be converted into the same kind of data as already described. is there. The name item indicates what meaning of medical information system the actual data to be converted is.

  The data conversion rule ID provided in the item of the data conversion rule detail table is as described above. The item of the same kind data stores how the actual data is converted, and the item of actual data stores the data before conversion. Here, when the actual data is “0” or “1”, the data conversion rule IDs “1” and “3” are converted into “male” or “female” of the same kind of data, and the data conversion rule ID It can be seen that “2” and “4” are converted into “male” or “female” of the same kind of data when the actual data is “M” or “F”. Similarly, when the data conversion rule ID “5” is the code “K100” “K101”..., The data conversion rule ID “5” is converted into drug names “asinine” “isinine”. When the actual data is the code “M1000”, “M1001”..., The data conversion rule ID “6” is converted into the drug name “asinine” “isinine”. I understand that.

  The various master tables 24 store fixed and basic data. As examples, there are a drug name master table shown in FIG. 7A and a target master table shown in FIG. 7B. The medicine name master table stores medicine names in the same kind of data, and here, medicine names such as “Ashinin”, “Ishinin”,... Are stored.

  The target master table stores which table of which medical information system the above-mentioned target ID actually indicates, and has items of “target ID”, “system name”, and “table name”. The target ID is as already described. The item of system name stores whether the table indicated by the target ID is the medical information system A or the medical information system B. The table name item stores the name of an actual table provided in the database of the medical information system. Here, the table indicated by the target ID “A-1” is a table called “disease name order” of “medical information system A”, and the table indicated by the target ID “A-2” is “medical information”. It can be seen that the table is “Radiation Order” of “System A”. The target master table has been described as an example of various master tables here, but may be included in a table for similar targets.

  Returning to FIG. 1, the view storage unit 25 is an area for temporarily storing view data to be described later. The term “temporary” means that the view data is not stored as long as the medical data management system 1 according to the present embodiment continues to be operated. When the display of the view data by the display unit 14 is finished, the view storage unit 25. The view data may be immediately deleted from the view history, or the view data of the past search history may be stored for a predetermined period if the capacity of the view storage unit 25 is sufficient.

  The control unit 11 is realized by a CPU, a semiconductor auxiliary memory, and the like, and includes a search control unit 12 and a conversion control unit 13.

  When a desired search condition is input from the input unit 10, the search control unit 12 is a database to be searched based on the same target table 21, the same column table 22, and the data conversion rule table 23. A table and a column provided for each of 100 and 200 are specified, and actual data is searched from each database. As a specific procedure, when the same type target to be searched, the same type column of the same type target, and the same type data of the same type column are input by the input unit 10, the same type column of a plurality of tables collected as the same type target The actual data corresponding to the same kind of data is searched from a plurality of columns collected as, and the required range of data, for example, a record including the actual data is selected, and a new table (hereinafter referred to as “actual data”) is selected. A data table ") is created for each of a plurality of tables grouped together as a target of the same kind.

  The conversion control unit 13 converts the retrieved actual data table into a table of the same type data (hereinafter referred to as “same type data table”) based on the table for data conversion rule. The specific procedure is to determine whether or not the actual data including the column name of the actual data table needs to be converted by the same kind column management table, and which data conversion rule ID to convert if necessary. To do. Next, the actual data that needs to be converted is converted based on the data conversion rule table 23, and the conversion process is performed with the actual data that does not need to be converted intact. Then, a similar data table is created from the converted data.

  In principle, there are as many similar data tables converted from actual data tables retrieved from a plurality of databases 100 and 200 as there are databases of different medical information systems. The plurality of similar data tables are collected into view data, which is one table, as display data by the conversion control unit 13. In addition, this view data can be displayed only in a desired item in the collected table.

  The display unit 14 includes a known display device and the like, and displays the search condition input by the input unit 10 and the view data stored in the view storage unit 25 as visual information.

  Next, based on the function of each component described above, the operation of the medical data management system 1 of the present embodiment will be described with reference to FIGS. 2 to 7 are as already described. FIG. 8 is a diagram for explaining a process of creating view data by data search and conversion. FIG. 9 is a flowchart for explaining the overall processing for searching and converting data from a plurality of databases. FIG. 10 shows the processing for inputting search conditions and acquiring information necessary for searching actual data. FIG. 11 is a flowchart for explaining processing for searching for actual data, FIG. 12 is a flowchart for explaining processing for converting actual data into the same kind of data, and FIG. 13 is for explaining processing for creating view data. FIG.

  First, referring to FIG. 9, the medical data management system 1 of the present embodiment retrieves actual data from a plurality of databases 100 and 200, converts the retrieved actual data into the same kind of data, and further displays it as view data. The overall process will be described.

  When processing by the medical care data management system 1 of this embodiment is started, a screen for accepting input of search conditions is displayed on the display unit 14, and the search conditions are input by the operator operating the input unit 10. In addition to the input of the search condition, the same type target ID, target ID, and same type column ID necessary for searching the actual data are acquired (S1000). Next, based on the acquired homogeneous target ID, target ID, and homogeneous column ID, actual data is retrieved from a plurality of medical information system databases (S2000). Next, the retrieved actual data is converted to the same kind of data (S3000). Next, view data is created from the converted one or more similar data (S4000). Then, the display unit 14 displays the view data as visual information (S5000).

  Next, referring to the flowcharts shown in FIGS. 9 to 13, each step of the processing by the medical data management system 1 of the present embodiment will be described in detail, while referring to the tables shown in FIGS. A specific example of search and conversion will be described.

  In the input of the search condition and the acquisition of the same target ID, target ID, and same column ID in step S1000 shown in FIG. 10, first, the search control unit 12 sets the display name of the same target table (FIG. 4A). The item is referred to, and an input screen for the display name of the homogeneous target for determining the homogeneous target to be searched is displayed (S1010). Next, the display name of the same target to be searched, for example, “prescription” is input by the input unit 10 (S1020). Then, the search control unit 12 obtains the same target ID “2” of the display name “prescription” from the same target table (S1030), and further, from the same target management table (FIG. 4B), the same target ID “2”. Based on “2”, target IDs “A-8” and “B-3” indicating different tables provided for each database are acquired (S1040).

  Next, in order to determine the same type column to be searched, among the display name items of the same type column table (FIG. 5A), the record (“in the figure” related to the same type target ID “2” acquired above). The display name input screen of the same kind column for inputting “patient ID”, “sex”, “request department”,... which is the display name of the record indicated by “a” is displayed (S1050). Next, the display name of the same kind column to be searched, for example, “medicine name” is input by the input unit 10 (S1060). Then, the search control unit 12 acquires the same kind column ID “11” of the display name “drug name” from the same kind table (record indicated by “b” in the figure) (S1070).

  Next, in order to determine the same kind of data to be searched by referring to the item of the same kind of data in the medicine name master shown in FIG. 7A that stores the name of the same kind of data of the same kind column ID “11”. Then, the same type data input screen for inputting the same type data is displayed (S1080). Next, similar data to be searched for, for example, “Ishinin” is input by the input unit 10 (S1090). Through these processes, input of search conditions of “prescription”, “medicine name”, and “isinine” and acquisition of the same target ID “2”, target IDs “A-8”, “B-3”, and same type column ID “11” Is made. If conversion of data related to the same kind column ID acquired in step S1070 is not necessary (when the data conversion item of the same kind column management table corresponding to the obtained same kind column ID is “N”), step S1080. Then, the actual data master may be referred to and displayed. In addition, here, the drug name master is referred to and the drug name “Ishinin” is selected as a search condition. For example, when the search target is a test value, a range of a desired value can be designated by a number, Search conditions such as whether the test result is positive or negative can also be set.

  Next, in the search of actual data in step S2000 shown in FIG. 11, the search control unit 12 specifies the column of the table to be searched (S2010). Specifically, based on the same kind column ID “11” acquired in step S1070, a record (a record indicated by “c” in the figure) related to the same kind column ID “11” in the same kind column management table (FIG. 5B). ). Then, “yakusaimeiyou” and “drug number” corresponding to the target IDs “A-8” and “B-3” acquired in step S1040 are acquired from the column name item. Thereby, the column of “yakusaimeiyou” in the table of the target ID “A-8” and the column of “medicine number” in the table of the target ID “B-3” can be specified as search targets.

  Next, the search control unit 12 determines whether the same kind of data input in step S1090 is the same as the actual data (S2020). Here, among the data conversion items of the homogeneous column management table, the already acquired records of the identical column ID “11” and the target IDs “A-8” and “B-3” are referred to (“c” in the figure). Record). If the data is “Y”, the input similar data and the actual data are different. If the data is “N”, the input similar data and the actual data are the same. When the same kind data input and the actual data are different, the actual data cannot be searched even if the same kind data is used as a search key. Therefore, it is necessary to acquire the actual data serving as the search key. As this procedure, first, the data conversion rule ID is acquired from the data conversion rule ID item of the homogeneous column management table (S2030). Here, the data conversion item of the record of the same kind column ID “11” is “Y”, and it is understood that the same kind of data is different from the actual data, and data conversion is necessary. Data conversion rule IDs “5” and “6” are acquired.

  Next, the search control unit 12 performs a process of acquiring actual data serving as a search key based on the same kind of data (S2040). This is based on the data conversion rule IDs “5” and “6” acquired in step S2030, and records related to the data conversion rule IDs “5” and “6” in the data conversion rule detailed table (FIG. 6B). “Ishinin”, which is a search condition, is searched from items of the same kind of data (record indicated by “d” in the figure). Then, as actual data to be a search key from a record including “Ishinin” among the items of actual data, “K101” is set for the data conversion rule ID “5”, and “M1001” is set for the data conversion rule ID “6”. Get it. That is, by the processing from step S2010 to step S2040, the column name “yakusaimeiyou” for the target ID “A-8” and the actual data “K101” as the search key are stored, and the column name “drug” for the target ID “B-3”. Number ”and actual data“ M1001 ”as a search key are acquired. If the data conversion item is “N” in step S2020, the same kind of data is the same as the actual data, and the same kind of data itself can be used as a search key. Therefore, the processes in steps S2030 and S2040 are performed. Is skipped.

  Next, the search control unit 12 performs a process of searching for records related to the actual data from a plurality of databases based on the already acquired target ID, column name, and actual data or similar data serving as a search key (S2050). First, a medical information system and a table corresponding to the target ID “A-8” are specified with reference to the target master table (FIG. 7B). Here, it can be seen that the medical information system and table corresponding to the target ID “A-8” are “prescription orders” of “system A” (records indicated by “e” in the figure). Then, the actual data “K101” serving as a search key is searched from the item “yakusaimeiyou” in the “prescription order” table of the medical information system A shown in FIG. 2A, and the corresponding record is extracted. Then, an actual data table shown in FIG. 8B is created (S2060).

  Similarly, for the target ID “B-3”, it can be seen from the target master table that the medical information system and table corresponding to the target ID “B-3” are “prescription for search” of “system B” (FIG. Middle “f”). Then, the actual data “M1001” serving as a search key is searched from the item “drug number” in the “prescription for search” table of the medical information system B shown in FIG. 2B, and the corresponding record is extracted. An actual data table shown in (D) is created. In this way, the actual data search process and the actual data table are created.

  Next, in the conversion of the actual data in step S3000 shown in FIG. 12 to the same kind of data, the conversion control unit 13 converts the actual data table created above into the same kind of data table. First, an actual data table that has not been converted to the same kind of data table is selected (S3010). Here, an actual data table (hereinafter referred to as “A-8 actual data table”) retrieved from the target ID “A-8” shown in FIG. 8B is selected. Next, a column that is not subjected to conversion processing in the actual data table is selected, and the same type column ID, presence / absence of data conversion, and data conversion rule ID are acquired (S3020). Here, the first column “kaishibi” is selected from the unprocessed columns of the A-8 actual data table, and the same kind column management table (FIG. 5) is selected based on the target ID “A-8” and the column name “kaishibi”. (B)) (record indicated by “g” in the figure), the same kind column ID “10”, data conversion “N”, and data conversion rule ID “none” are acquired. Next, the display name of the same kind column is acquired, and the original column name is converted into the display name (S3030). Here, based on the same kind column ID “10” already acquired, the same kind column table (FIG. 5A) is referred to (a record indicated by “h” in the figure), the display name “prescription start date” and the data format. The “date type” is acquired, and the first column name “kaishibi” in the A-8 actual data table is converted into the acquired display name “prescription start date”.

  Next, based on the data conversion “N” and the data conversion rule ID “none” acquired in step S3020, it is determined whether or not the data conversion of the “prescription start date” column is necessary (S3040). Here, since data conversion is not necessary, the data in the column of the column name “prescription start date” in the A-8 actual data table is not changed, and step S3050 and step S3060 described later are skipped.

  Next, it is determined whether there is any remaining column of the A-8 actual data table that has not been converted (S3070). Here, since there is a column “kanjyaID”, the processing from step S3020 to step S3040 is also performed on this column, the column name is changed to “patient ID”, and the data in the column is not changed as it is.

  Next, the same process is repeated, and in step S3020, the column “seibetu” of the A-8 actual data table is selected, and the same column ID “8” and data conversion “from the same column management table (FIG. 5B)” are selected. Y ”and data conversion rule ID“ 3 ”are acquired (record indicated by“ i ”in the figure). Next, in step S3030, a record of the same kind column ID “8” (record indicated by “j” in the figure) is selected from the same kind column table (FIG. 5A), and the display name “sex” and the data format “character” are selected. "Type" is acquired, and the column name "seibeta" in the A-8 actual data table is converted into the acquired display name "sex".

  Next, in step S3040, it is determined whether data conversion is necessary. Here, since the item data of the data conversion acquired in step S3020 is “Y”, it is determined that data conversion is necessary. Next, based on the already obtained data conversion rule ID “3”, the data conversion rule detail table (FIG. 6B) is referred to, and the corresponding record (record indicated by “k” in the figure) is selected. A data conversion rule is acquired from the item of the same kind of data and the item of the actual data (S3050). Then, according to the acquired conversion rule and data format, the actual data is converted into the same kind of data (S3060). Here, the actual data “0” in the “gender” column of the A-8 actual data table is the same data “m” data format “character type”, and the actual data “1” is the same data “female” data format “character”. Convert to type. By repeating these steps S3020 to S3070, all the column names and actual data in the A-8 actual data table are processed and converted into the A-8 homogeneous data table shown in FIG. 8C.

  Next, it is determined whether there is any other actual data table that has not been converted (S3080). Here, there is an actual data table created from the target ID “B-3” shown in FIG. 8D (hereinafter referred to as “B-3 actual data table”), and the process returns to step S3010, and B-3 actual By selecting the data table and repeating the processing from step S3020 to step S3070 described above, the data table is converted into the B-3 homogeneous data table shown in FIG. In addition, in order to make it easy to understand that the column name is converted to the display name of the same kind column (item of the display name in FIG. 5A), FIG. 8A shows the display name of the same kind column.

  Next, in the creation of view data in step S4000 shown in FIG. 13, the conversion control unit 13 determines whether or not there are a plurality of similar data tables created by the processing from step S3000 to step S3080 (see FIG. 13). S4010). When there are a plurality of similar data tables, the conversion control unit 13 integrates the plurality of similar data tables into one table and creates view data (S4020). Here, there are an A-8 homogeneous data table and a B-3 homogeneous data table. These are integrated, and the order of items is rearranged in the same manner as the identical column shown in FIG. Create the view data table shown in Then, the created view data table is stored in the view storage unit 25 as view data (S4030). On the other hand, when there is one homogeneous data table, the homogeneous data table itself is view data, so the homogeneous data tables are not integrated and only the order of items is rearranged. As the view data, only a desired item can be extracted from the integrated table.

  Next, as shown in step S5000 of FIG. 9, the display unit 14 displays the view data as visual information. Then, the view data that has been viewed by the operator and is no longer displayed may be immediately deleted from the view storage unit 25. If the capacity of the view storage unit 25 is sufficient, a past search is performed for a predetermined period. It may be left as data.

  As described above, according to the medical data management program and the medical data management system of the present invention, there are different types of databases due to changes in the electronic medical record and various department system manufacturers and the system itself. However, it is not necessary to create these integrated databases, and a great amount of labor and money for creating the integrated database are not required, and computer resources can be saved. In addition, it is generally difficult to create an integrated database that covers all data from multiple databases, and some data is often not stored in the integrated database but is left only in the backup storage. However, according to the medical data management program and the medical data management system of the present invention, since it is not necessary to create an integrated database, it is possible to operate the original database as it is. It is advantageous.

  In addition, since only the necessary range is processed each time in data search or the like, data search, statistical processing, and inquiry can be performed quickly, and the load on the system itself can be reduced.

  In addition, while operating the medical data management program and the medical data management system of the present invention, the number of databases may be changed because the manufacturer or system itself of the electronic medical record or various department systems is changed again or merged with other hospitals, etc. Can be handled by maintenance of tables for homogeneous targets, tables for homogeneous columns, tables for data conversion rules, etc., eliminating the need to create a new consolidated database and reducing costs in the future It is possible to respond flexibly.

  The medical data management program and the medical data management system described above are examples of the present invention, and the configurations thereof can be changed as appropriate without departing from the spirit of the invention. For example, if the processing results are the same, the order of the above-described processing flows may be partially exchanged. In the data conversion process, the same data table can be created separately while leaving the actual data table as it is. In addition, in inputting search conditions, various input methods such as inputting desired search conditions as text data directly from a keyboard, etc., or selecting from a plurality of candidates using a pull-down menu, etc. are adopted. can do.

1. ・ Medical data management system,
10 .... Input unit 11 .... Control unit 12 .... Search control unit 13 .... Conversion control unit 14 ... Display unit 20 ... Storage unit 21 ... Same target table 22 ... Same type Table for columns, 23 .. Table for data conversion rules, 24 .. Various master tables, 25.
100, 200 ... database,

Claims (4)

In a clinical data management program that directly searches and manages multiple databases stored in different formats,
Computer
In order to collectively manage different tables provided for each database for the same purpose as one logical homogeneous target, the homogeneous target ID and the homogeneous target ID for identifying the homogeneous target for each homogeneous target A table for storing the display name corresponding to the table, and a table for a homogeneous target comprising a column for storing a target ID for identifying the table associated with the homogeneous target ID ;
In order to collectively manage the columns having the same meaning in the plurality of tables as the same target as a logical same type column, the same type column ID for specifying the same type column for each of the same type columns, and A table for a homogeneous column comprising a column for storing a display name corresponding to the homogeneous column ID, and a column for storing an item name of a column having the same meaning in the table associated with the homogeneous column ID ;
A table for data conversion rules for managing conversion rules for converting real data of different formats stored in a plurality of columns that are the same type columns to the same type data for integration;
When a search condition based on the homogeneous target, the homogeneous column, and the homogeneous data is input, the search target is based on the homogeneous target table, the homogeneous column table, and the data conversion rule table. A search control unit that identifies the table provided for each database and a column having the same meaning in the table, and retrieves the actual data from a plurality of the databases;
A conversion control unit that converts the searched real data into the same kind of data based on the table for the same kind column and the table for the data conversion rule, and converts it into view data as display data,
A view storage unit for temporarily storing the view data;
A display unit for displaying the view data stored in the view storage unit as visual information;
A medical data management program characterized in that it is made to function.   The medical data management program according to claim 1, wherein the plurality of databases are different databases based on different generations of medical information systems.   The medical data management program according to claim 1, wherein the plurality of databases are different databases based on different medical information systems existing in parallel. In a medical data management system that directly searches and manages multiple databases stored in different formats,
In order to collectively manage different tables provided for each database for the same purpose as one logical homogeneous target, the homogeneous target ID and the homogeneous target ID for identifying the homogeneous target for each homogeneous target A table for storing the display name corresponding to the table, and a table for a homogeneous target comprising a column for storing a target ID for identifying the table associated with the homogeneous target ID ;
In order to collectively manage the columns having the same meaning in the plurality of tables as the same target as a logical same type column, the same type column ID for specifying the same type column for each of the same type columns, and A table for a homogeneous column comprising a column for storing a display name corresponding to the homogeneous column ID, and a column for storing an item name of a column having the same meaning in the table associated with the homogeneous column ID ;
A table for data conversion rules for managing conversion rules for converting real data of different formats stored in a plurality of columns that are the same type columns to the same type data for integration;
When a search condition based on the homogeneous target, the homogeneous column, and the homogeneous data is input, the search target is based on the homogeneous target table, the homogeneous column table, and the data conversion rule table. A search control unit that identifies the table provided for each database and a column having the same meaning in the table, and retrieves the actual data from a plurality of the databases;
A conversion control unit that converts the searched real data into the same kind of data based on the table for the same kind column and the table for the data conversion rule, and converts it into view data as display data,
A view storage unit for temporarily storing the view data;
A display unit for displaying the view data stored in the view storage unit as visual information;
A medical data management system comprising:

Images