Healthcare Information Management Device

Abstract

This system centrally manages and utilizes diverse forms of healthcare-related information generated from various facilities and systems. [Solution] The healthcare information management device 1 comprises a document management table 2, a detail data table 3, extended index tables 4a, 4b, ... 4n for high-speed searching within a preset data range, a document processing program 5 that detects records stored and updated in the document management table 2 in real time, reads, analyzes, and decomposes the stored document data, and automatically stores, updates, and deletes it in the detail data table 3, a document processing rule table 6 that defines the processing of the document processing program 5, an index creation program 7 that automatically stores, updates, and deletes the contents of the index section and the contents of the extended index tables 4a, 4b, ... 4n, and an index creation rule table 8 that defines the processing of the index creation program 7.

Description

Technical Field

[0001] The present invention relates to a healthcare information management apparatus and method, and more particularly, to an invention that applies a database program for integrally managing healthcare-related information including medical care, nursing care, and health management, and for using the accumulated data in multiple purposes in real time.

Background Art

[0002] In order to solve regional healthcare issues, promote efficient regional comprehensive care, and promote cooperation of digital services across fields and DX, it is necessary to collect and handle various healthcare-related information including medical care, nursing care, and health management intensively and efficiently, and to make the information available for distribution and utilization in various applications. In order to achieve this, it is common to construct a database that centrally aggregates the necessary information as a data warehouse (DWH: Data Ware House).

[0003] On the other hand, due to differences in facilities, systems, devices, standards, etc., even in different fields such as medical care, nursing care, and health management, or even in the same field and the same business, there are various forms and types of data. Although there are some data formats that have been partially standardized such as receipts, the scope of their correspondence is extremely limited, and new data items are constantly generated with the progress of various medical devices and system development. That is, it is practically impossible to handle all healthcare-related information in a standard manner.

[0004] Furthermore, in the general database design of a system (such as an electronic medical record system) that handles healthcare-related information, normalization is performed from the viewpoints of data storage efficiency and ensuring high speed during retrieval, and it is common to store data using multiple tables for each type and hierarchy of data. Therefore, various tables and a huge number of data items are generated in handling various healthcare-related information.

[0005] While a simple method for collecting and utilizing this information is to aggregate the data by copying it to a data warehouse (DWH) while maintaining its original structure, if any items are added or the structure of the original data changes, the DWH side will need to make the same changes each time. Failure to do so increases the likelihood of data loss. Consequently, the management costs of a database with such a large number of finely subdivided and strictly structured tables inevitably increase.

[0006] In contrast, a conventional method has been used to extract, transform, and aggregate raw data in various formats by mapping them to a format defined on the data warehouse side. However, if errors or omissions occur in the mapping set at the time of data collection, it becomes necessary to collect and transform past data again, which can result in enormous work costs and periods when the data is unavailable.

[0007] To address the challenges of constructing a data warehouse (DWH) for this healthcare-related information, the present inventors, as shown in Non-Patent Documents 1 and 2, have implemented a highly versatile and reliable DWH construction method that overcomes the aforementioned challenges. This method involves using a document database of an electronic medical record system within a hospital, which stores relevant data as structured text such as XML in a single record. The DWH generates key-value format data consisting of data items and values ​​by realizing this data in real time, and then deploying a virtual table that reconstructs this information upon extraction. [Prior art documents] [Patent Documents]

[0008] [Non-Patent Document 1] Masamasa Iida, "Practical Application of a Data Utilization Model Directly Linked to HIS: Approaches and Realities of Real-Time BI," Presentation materials from the Luncheon Seminar at the 41st Japan Society for Medical Informatics Conference, Nagoya International Conference Center, November 19, 2021. [Non-Patent Document 2] Masamasa Iida, "Achievements and Considerations of ETL for Data Management and Utilization within Hospitals," June 29, 2023, Okinawa Convention Center, Presentation materials for Tutorial 6, 27th Spring Academic Conference of the Japanese Society for Medical Informatics. [Overview of the project] [Problems that the invention aims to solve]

[0009] However, Non-Patent Documents 1 and 2 deal with the utilization of information stored in electronic medical record databases and remain within the scope of real-time utilization of medical data within a single hospital. They do not present concrete methods for centrally managing and utilizing diverse forms of healthcare-related information generated from various facilities and systems. Furthermore, they do not disclose specific methods for ensuring reversibility or compatibility between document data with complex and diverse structures and decomposed key-value format data, nor for ensuring high-speed processing of the enormous number of records generated by data decomposition.

[0010] Therefore, in order to solve the aforementioned problems, the present invention aims to realize a database infrastructure that stores all healthcare-related information, which originates from various information sources and has all forms and formats, without any loss, centrally manages all information and its location, and enables real-time and multipurpose use of all stored information, thereby significantly improving efficiency and optimizing costs related to expanding data utilization and management. [Means for solving the problem]

[0011] As shown in Figure 1, the healthcare information management device 1 of the present invention includes a document management table 2 that stores healthcare-related information as aggregate data of information management units, represented as document data in structured text or binary data, manages the uniqueness, data format and structure of the document data, and manages the basic identifiers and evidence information of the document data as an index; a detail data table 3 that stores healthcare-related information as the smallest unit of information data in a key-value format consisting of data items and their values, manages the association with the document management table 2 and the document structure, and has an index to ensure high-speed searchability; extended index tables 4a, 4b, ... 4n that enable high-speed searching within a pre-set data range by creating an arbitrary table by combining arbitrarily selected items from the data items written in the detail data table 3 as column names; and a device that detects records stored and updated in the document management table 2 in real time and stores the stored document data The system is characterized by comprising: a document processing program 5 that reads, analyzes, and decomposes data and automatically stores, updates, and deletes it in the detail data table 3; a document processing rule table 6 that pre-defines and manages the format of document data stored in the document management table 2 and defines the processing of the document processing program 5 in association with it; an index creation program 7 that, after the completion of the document processing program 5, reads and processes the data in the detail data table 3 processed by the document processing program 5, and automatically stores, updates, and deletes the contents of the index section provided in the document management table 2 and the detail data table 3, as well as the contents of the extended index tables 4a, 4b, ... 4n; and an index creation rule table 8 that defines the processing of the index creation program 7 by associating the data items written in the detail data table 3 with the item names that form the index section of the document management table 2 and the detail data table 3, and the table names and item names of the extended index tables 4a, 4b, ... 4n.

[0012] This invention enables the storage of healthcare-related information, which originates from various information sources such as medical information systems, nursing care information systems, and health management systems, and takes on various forms and formats, without any data loss. It also realizes a database infrastructure that allows for the centralized management of various types of information and their locations, and enables real-time and multi-purpose utilization of the stored information. Furthermore, it significantly improves efficiency and optimizes costs related to expanding data utilization and management.

[0013] Specifically, the present invention provides a database infrastructure that allows for the storage and management of healthcare-related information in various forms and formats, and enables high-speed and multipurpose utilization of that information. This is achieved by using a document management table 2 that stores a collection of information that can be represented as text data as a single record, and a detail data table 3 that stores information in data item units while ensuring reversibility by managing the data hierarchy and order in the original document information.

[0014] Specifically, this invention ensures reversibility by clearly identifying the origin of the input healthcare-related information, and ensures that the data can be analyzed and decomposed, making the stored information usable. The index creation program 7 and the index creation rule table 8 enable flexible index creation. The extended index tables 4a, 4b, ... 4n ensure high-speed data retrieval processing from vast amounts of information.

[0015] As a prerequisite for storing healthcare-related information, identifiers for each facility that is the source of the information, such as medical institutions, and identifiers for each source of information that correspond to differences in systems and information management organizations within the same facility must be set in advance. Furthermore, the relationship between the source of healthcare-related information and the information stored in the database will be managed by assigning a unique document key for each combination of these identifiers. By using information regarding the uniqueness of the data shown within the stored healthcare-related information, the same level of uniqueness as the source can be ensured.

[0016] Identifiers and document-specific keys based on information source can clearly identify the origin of healthcare-related information.

[0017] The document management table 2 stores one record for each healthcare-related information document to be stored, and includes a document unique key to ensure the uniqueness of the stored document, identification and management information of the information source corresponding to the above conditions, information regarding the acquisition of the stored document, a document format ID that represents the format of the document data, and a document data item that stores healthcare-related information read from files or databases as is, and the basic structure of the database is the document management unit 2a.

[0018] This allows the document management unit 2a to manage documents collectively based on their origin, clearly defining their source. It also manages the format of documents, allowing them to be stored without damaging their content.

[0019] The document unique key should be assigned a unique value each time a new record is written to document management table 2, and it is desirable to use automatic numbering by the database management function.

[0020] Document data items should preferably be stored in binary format to accommodate long strings of text and text data with various character encodings, as well as object-type data containing various types of data such as PDFs, Word documents, Excel spreadsheets, and image files.

[0021] Document Management Table 2, in addition to Document Management Section 2a, includes fields for recording the identifier of the person (patient, citizen, etc.) whose healthcare-related information is stored, history management information for the same record, record type and purpose, recorder, record date and time, and other index and basic evidence information related to the record. This is designated as Document Index Section 2b as an extended configuration of the database. This allows for the explicit recording of evidence information for documents, thereby improving search efficiency and management capabilities.

[0022] The detailed data table 3 stores each piece of included data in one record as a result of analyzing the content (structured text) of the healthcare-related information stored in the document management table 2. It has items for storing a data value, a data item name, a data unique key that ensures uniqueness in terms of the data item unit, a document unique key that associates the decomposed data item with the original document, a document format ID, and configuration information of the structured text (such as the data item name, the path of the data hierarchy, the parent-child identifier of the data hierarchy, the order of appearance of the data, etc., content that enables restoration from the decomposed detailed data to the original structured text), and is taken as the detailed data part 3a of the database's basic configuration. Thereby, the data in the document is decomposed and its content can be used as a database.

[0023] The data unique key assigns a unique value each time a new record is written to the detailed data table 3, and it is desirable to use automatic numbering by the database management function. Thereby, the uniqueness of all data can be maintained.

[0024] Regarding the path indicating the data hierarchy among the configuration information of the structured text, since it may become a long string depending on the configuration of the original data and is assumed not to directly function as an index for the detailed data table 3, an index item for storing compressed data hierarchy path information that ensures the uniqueness of this information is added to the detailed data part 3a. Thereby, the search efficiency is enhanced.

[0025] In addition to the detailed data part 3a, the detailed data table 3 has an item for recording an identifier of the person being recorded (such as a patient, citizen, etc.) of the healthcare-related information to be stored, and an index identifier and index value that can be set when it is desirable to use them as an index among various data items, and is taken as the detailed index part 3b of the extended configuration of the detailed data table 3.

[0026] The extended index tables 4a, 4b, ··· 4n shall be provided with one or more document unique keys associated with the original document and any item names corresponding to the item names in the document management table 2 or the data item names stored in the detail data table 3. This enables explicit management of the relationship between the document unique key and the data of the arbitrarily set items in the same record, thereby improving the search efficiency.

[0027] The document processing rule table 6 is a setting table for defining the operations of the document processing program 5 corresponding to the document format ID, and is provided with items of a document format ID having a unique value, a document format name for uniquely setting the name representing the origin and format of the document, a data format representing the representation format of structured text or binary data, and data processing option items for defining item names, data lengths, etc. for data for which item names and delimiter characters are not defined as processing conditions for the operations of the processing program corresponding to the data format.

[0028] The indexing rule table 8 is a setting table for defining the operations of the indexing program 7 corresponding to the document format ID, and includes items of a document format ID and index target data items for defining the data item names and the paths of data hierarchies in the detail data table 3 as the acquisition sources of the indexing data, which is referred to as an index target definition unit 8a. Subsequently, as the definition of the storage destination of the acquired indexing data, there are provided items of a basic index item name for arbitrarily setting the item name of the document index part 2b in the document management table 2, a detail index identifier value for arbitrarily setting the value of the index identifier of the detail index part 3b in the detail data table 3, and a combination of the table name and item name of the extended index tables 4a, 4b, ··· 4n, which is referred to as an index item definition unit 8b.

[0029] The document processing program 5 automatically detects records written to the document management table 2, retrieves the contents of the document data items, retrieves the settings in the document processing rule table 6 by matching them with the document format ID, and then analyzes and decomposes the contents in a format suitable for the stored healthcare-related information data format, thereby automatically writing, updating, and deleting in the detail data table 3.

[0030] Document processing program 5 controls the processing program corresponding to the document format ID defined in document processing rule table 6, and can execute arbitrary program processing according to the format of structured text and the content of binary data, and performs branch processing control based on the document format ID. This makes it possible to appropriately process healthcare-related information expressed in various forms and formats from various information sources for each format, and to reflect healthcare-related information in detail data table 3 without any loss.

[0031] The indexing program 7 is executed immediately after the document processing program 5 has completed its processing successfully, and retrieves the settings of the indexing rule table 8 by matching them with the document format ID processed by the document processing program 5. Subsequently, it retrieves the data values ​​of the detail data table 3 by searching using the document unique key processed by the document processing program 5 and the settings of the index target data items in the index target definition unit 8a, and uses this as index data.

[0032] The index creation program 7 is a processing program that writes, updates, and deletes the index data for the corresponding items in the document index section 2b of the document management table 2, the detail index section 3b of the detail data table 3, and the extended index tables 4a, 4b, ... 4n, according to the storage location of the index data defined in the index item definition section 8b of the index creation rule table 8. [Brief explanation of the drawing]

[0033] [Figure 1] This is a diagram showing an example of a healthcare information management device according to an embodiment of the present invention. [Figure 2] This is a block diagram showing an example of the hardware configuration of the apparatus according to an embodiment of the present invention. [Figure 3] This is flowchart 1, showing an example of the operation of the apparatus according to an embodiment of the present invention. [Figure 4] This flowchart 2 shows an example of a subroutine in the indexing program for the operation of the device according to an embodiment of the present invention. [Figure 5] Flowchart 3 shows a specific example of a subroutine in the document processing program for the operation of the device according to an embodiment of the present invention. [Modes for carrying out the invention]

[0034] As shown in Figure 1, the healthcare information management device 1 of the embodiment of the present invention includes a document management table 2 that stores document data represented as structured text and binary data as aggregate data of information management units, manages the uniqueness of documents, data format and structure, and manages basic identifiers and evidence information of healthcare-related information as an index; a detail data table 3 that stores healthcare-related information as the smallest unit of information data in a key-value format consisting of data items and their values, manages the association with the document management table 2 and the document structure, and has an index to ensure high-speed searchability; extended index tables 4a, 4b, ... 4n that enable high-speed searching within a pre-set data range by creating an arbitrary table by combining arbitrarily selected items from the data items written in the detail data table 3 as column names; and a device that detects records stored and updated in the document management table 2 in real time and stores the stored documents The system is characterized by comprising: a document processing program 5 that reads, analyzes, and decomposes data and automatically stores, updates, and deletes it in the detail data table 3; a document processing rule table 6 that pre-defines and manages the format of document data stored in the document management table 2 and defines the processing of the document processing program 5 in association with this format; an index creation program 7 that, after the completion of the document processing program 5, reads and processes the data in the detail data table 3 processed by the document processing program 5, and automatically stores, updates, and deletes the contents of the index sections in the document management table 2 and the detail data table 3, as well as the contents of the extended index tables 4a, 4b, ..., 4n; and an index creation rule table 8 that defines the processing of the index creation program 7 by associating the data items to be written to the detail data table 3 with the item names that form the index sections of the document management table 2 and the detail data table 3, and the table names and item names of the extended index tables 4a, 4b, ..., 4n.

[0035] A processing unit 9, which performs writing, updating, and deletion operations to the document management table 2 using various programs or ETL (Extract Transform Load) processing, is connected to the document management table 2. The processing unit 9 is also connected to the database 10 of the medical information system 1, the output file 11 of the medical information system 2, the database 12 of the nursing care information system 1, the output file 13 of the nursing care information system 2, and the output file 14 of the health management system (these are examples, and the type and number of information sources are set as appropriate), and is configured to input this information into the healthcare information management device 1.

[0036] Figure 2 shows the hardware configuration of the healthcare information management device 1 of this embodiment. As shown in Figure 2, the healthcare information management device 1 includes an arithmetic control unit 101 that controls the calculation of information, a storage unit 102 that is responsible for storing information, a display control unit 103 that controls the display of information, a sound control unit 104 that controls sound, a communication control unit 105 that controls the transmission and reception of information with the outside, and an input / output unit 106. The arithmetic control unit 101, the storage unit 102, the display control unit 103, the sound control unit 104, and the communication control unit 105 are connected to the processing unit 9 by the input / output unit 106. The processing unit 9 is connected to medical information system 1, medical information system 2, nursing care information system 1, nursing care information system 2, and health management system. These are connected via a communication network such as wired or wireless, and are configured to communicate with each other.

[0037] Medical information systems 1 and 2 are information devices used by users, such as doctors and technicians. Examples of these include PCs (personal computers) and WS (medical workstations), and portable terminals (mobile devices) may also be used. Medical information here includes, for example, textual information such as the name of the medical institution, health checkup reports, and medical records, as well as numerical data and waveform data from tests, information related to medical images acquired (taken) by medical imaging diagnostic equipment such as X-ray CT scanners, and mixed text and image information such as test reports.

[0038] Care information systems 1 and 2 are care information devices used by care facilities. Examples of care information include the name of the care facility, care needs assessment data, and care records.

[0039] A health management system is a health management system used by a government agency or health management center. Examples of health management information include the name of the health management center and the examination data of the person being examined.

[0040] The information transmitted from these sources is collected by the healthcare information management device 1 via the communication network based on user requests, and displayed on the display device according to the display layout.

[0041] As a prerequisite for storing healthcare-related information, identifiers for each facility that is the source of the information, such as medical institutions, and identifiers for each source of information that correspond to differences in systems and information management organizations within the same facility must be set in advance. Furthermore, the relationship between the source of healthcare-related information and the information stored in the database will be managed by assigning a unique document key for each combination of these identifiers. By using information regarding the uniqueness of the data shown within the stored healthcare-related information, the same level of uniqueness as the source can be ensured. This makes it possible to clearly identify the origin of the information.

[0042] As shown in Table 1, Document Management Table 2 comprises a Document Management Section 2a and a Document Index Section 2b. The Document Management Section 2a stores one record for each healthcare-related information document to be stored, and includes a document unique key to ensure the uniqueness of the stored document, identification and management information of the information source corresponding to the above conditions (information source identification ID, information source (facility), information source (system), information source-specific document unique key), information regarding the acquisition of the stored document (document acquisition date and time), a document format ID representing the format of the document data, and a document data item that stores healthcare-related information read from files or databases as is, forming the basic structure of the database (Document Management Table in Table 1).

[0043] [Table 1]

[0044] This allows the document management unit 2a to manage documents collectively based on their origin, clearly defining their source. It also manages the format of documents, allowing them to be stored without damaging their content.

[0045] The document unique key shown in Table 1 should be assigned a unique value each time a new record is written to document management table 2, and it is desirable to use automatic numbering by the database management function.

[0046] Document data items should preferably be stored in binary format to accommodate long strings of text and text data with various character encodings, as well as object-type data containing various types of data such as PDF, Word, Excel, and image files.

[0047] In addition to the document management section 2a, the document index section 2b includes items for recording indexes and basic evidence information related to records, such as the record ID, which is a unique key for records managed by the information source; the version number, which indicates the history identifier of the same record; the record type; the record status; the record date and time; the record subject ID, which is an identifier for the person (patient, citizen, etc.) whose healthcare-related information is stored; the record department; the creator ID; the creation date and time; the updater ID; and the update date and time (referring to the respective items in Table 1: record ID, record version number; record type; record status; record date and time; record subject ID; record department; creator ID; creation date and time; updater ID; and update date and time), thus providing an extended configuration of the document management table 2.

[0048] The detail data table 3 comprises a detail data section 3a, which stores each data item as a record, resulting from the analysis of the structured text containing healthcare-related information stored in the document management table 2. The detail data section 3a includes items that store data values, data item names, a unique data key to ensure uniqueness at the data item level, a unique document key to associate the decomposed data items with the original document, a document format ID, and structured text configuration information (referring to the data hierarchy path, data hierarchy classification, and data appearance order items in Table 2) to enable reconstruction from the decomposed detail data back into the original structured text. This constitutes the basic configuration of the detail data table 3.

[0049] [Table 2]

[0050] A unique data key should be assigned a unique value each time a new record is written to detail data table 3, and it is desirable to use automatic numbering by the database management function.

[0051] The detail data section 3a includes a data hierarchy index value field to store compressed data hierarchy path information while ensuring the uniqueness of this information. This is because the paths indicating the data hierarchy within the structured text may be extremely long strings depending on the structure of the original data, and therefore are not expected to be effective as an index for the detail data table 3.

[0052] The detail data table 3 includes a detail data section 3a and a detail index section 3b, which includes a record subject ID that serves as an identifier for the person(s) whose healthcare-related information is stored (patients, citizens, etc.), and an index identifier / index value that can be set from among various data items if it is desirable to use it as an index, thus forming an extended configuration of the detail data table 3.

[0053] Extended index tables 4a to 4n are explained using the following examples, as shown in Table 3: Example 1 is patient information, and Example 2 is prescription information. Example 1, patient information, consists of a document unique key, patient ID, patient name, date of birth, and gender. Example 2, prescription information, is exemplified by a document unique key, patient ID, prescription ID, drug code, dosage, and prescription unit.

[0054] [Table 3]

[0055] The document processing rule table 6 is a configuration table for defining the operation of the document processing program 5 corresponding to the document format ID. It includes a document format ID with a unique value, a document format name that uniquely represents the origin and format of the document, a data format that represents the representation format of structured text or binary data, and data processing option items that define the processing conditions to be applied to the operation of the processing program corresponding to the data format, such as item names and data length for data where item names and delimiters are not defined.

[0056] [Table 4]

[0057] The document processing program 5 automatically detects records written to the document management table 2, retrieves the contents of the document data items, retrieves the settings in the document processing rule table 6 by matching them with the document format ID, and then analyzes and decomposes the contents in a format suitable for the stored healthcare-related information data format, thereby automatically writing, updating, and deleting in the detail data table 3.

[0058] Document processing program 5 obtains the document format ID written in document management table 2 and retrieves the corresponding processing definition information from document processing rule table 6. Next, it reads the contents of the document data itself from document management table 2 and performs processing control to branch to pre-prepared text processing for each data format. In this way, healthcare-related information expressed in various forms and formats held by information sources such as medical information systems, nursing care information systems, and health management systems is appropriately processed for each data format and reflected in detail data table 3.

[0059] [Table 5]

[0060] The index creation rule table 8 shown in Table 5 comprises an index target definition section 8a and an index item definition section 8b. The index target definition section 8a consists of a document format ID and an index target data item. The index item definition section 8b consists of a basic index item name, a detail index identifier value, and an extended index table name and item name. This will be explained in the flowchart section below.

[0061] Each of the data points in Tables 1 to 5 above is written to the storage unit 102, and when reading them, they are read from the storage unit 102.

[0062] With the above configuration, the healthcare information management device 1 of the embodiment of the present invention uses a document management table 2 that stores a collection of information that can be represented as text data as a single record, and a detail data table 3 that stores all information in units of data items while ensuring reversibility by managing the hierarchy and order of data in the original document information. This realizes a database infrastructure that can store and manage all healthcare-related information in various forms and formats, and utilize that information at high speed and for multiple purposes.

[0063] Next, the operation of the healthcare information management device 1 according to the embodiment of the present invention will be explained with reference to the flowchart in Figure 3.

[0064] This flowchart shows the process of acquiring and writing healthcare-related data (S1-S5) and the document processing program (S11-S18), but for the sake of clarity, it will be explained using the same Figure 3.

[0065] In the acquisition and writing of healthcare-related data by the processing unit 9 and the healthcare information management device 1, first, healthcare-related data obtained through ETL processing, etc., is acquired and read from the database 10 of the medical system 1, the output file 11 of the medical information system 2, the database 12 of the nursing care information system 1, ... output file 14 of the health management system via the processing unit 9 and the input / output unit 106, etc. (S1).

[0066] Based on the data acquisition method and data content, information source identification and management information is set (S2).

[0067] Set the document format ID (S3) to match the definition in document processing rule table 6.

[0068] The entire contents of the acquired data are set as text data or binary data in the document data item (the document data column in Table 1) (S4).

[0069] The contents of the configured document management unit 2a are written to the document management table 2 (S5). The document management table 2 consists of the document management unit 2a and the document index unit 2b (see Table 1 and Figure 3).

[0070] The process of acquiring and writing healthcare-related data is now complete.

[0071] Referring to Figure 3, the document processing program first detects updated records in document management table 2, and if detected, reads the corresponding records (S11).

[0072] Determine whether the read record has been written as a new record (S12).

[0073] If the answer to S12 is YES, the document unique key is automatically assigned (S13); if the answer to S12 is NO, the program jumps to S14.

[0074] From document processing rule table 6, read the document processing rule that matches the document format ID (S14).

[0075] Determine whether or not document processing rules have been set (S15).

[0076] If the answer in S15 is YES, the document data is converted into structured text in a unified format based on the processing rule settings (S16). The structured text is then analyzed, and each decomposed data item is written to detail data table 3 (S17), before proceeding to S18.

[0077] On the other hand, if the result in S15 is NO, the index creation program is executed (S18), and the process proceeds to S11, and the above process is repeated.

[0078] Next, the index creation program shown in Figure 4 is executed. First, the detail data section 3a generated by the document processing program 5 and written to the detail data table 3 is read (S21).

[0079] From indexing rule table 8, the indexing rule with a matching document format ID is read (S22).

[0080] The contents of the data value items in detail data table 3 that match the settings of the index target data item items in index creation rule table 8 are written to the item in document index section 2b of document management table 2 that matches the settings of the basic index item name item in index creation rule table 8 (S23).

[0081] The contents of the data value items in the detail data table 3 that match the settings of the index target data item items in the index creation rule table 8 are written to the index value item in the detail data table 3. Subsequently, the setting of the detail index identifier value item in the index creation rule table 8 is written to the index identifier item in the detail data table 3 (S24).

[0082] Determine whether or not there is a setting for extended index creation in the index creation rule table 8 (S25).

[0083] If the answer in S25 is YES, the contents of the data value items in the detail data table 3 and the document unique key, etc., that match the settings of the index target data item items in the index creation rule table 8 are written to the corresponding items in extended index table 1_4a, extended index table 2_4b, ... extended index table n_4n that match the settings of the extended index table name and item name items in the index creation rule table 8 (S26). After S26, or if the answer in S25 is NO, the index creation program is terminated.

[0084] A specific example of the processing of the document processing program shown in Figure 3 will be explained with reference to the document processing program in Figure 5. First, the program detects updated and deleted records and determines whether or not there is a value in the document unique key item of the document management table 2 that has been read, and then determines whether or not the record is a new record (S31).

[0085] If the answer to S31 is YES, a new, non-duplicate value is generated for the document unique key (S32).

[0086] After S32, the document unique key in document management table 2 is updated with the newly assigned value (S33).

[0087] After S33, the contents of the document management section 2a of document management table 2 (document management items and document data) are read (S34).

[0088] On the other hand, if the answer in S31 is NO, the unique key of the document to be updated or deleted is obtained (S35).

[0089] After S35, the records in detail data table 3 that match the unique key of the document to be updated / deleted, as well as records in extended index table 1_4a, extended index table 2_4b, ... extended index table n_4n are deleted (S36).

[0090] After S36, it is determined whether the updated / deleted record in document management table 2 that was read was a record that was to be deleted (S37).

[0091] If the answer in S37 is YES (when deleting a document record), the process ends; otherwise, proceed to S34.

[0092] After S34, the contents of document processing rule table 6 that match the document format ID obtained in S34 are read (S38).

[0093] After S38, it is determined whether the data format of document processing rule table 6 is other than XML (S39).

[0094] If the answer in S39 is YES, the document data is converted to XML format according to the contents of the data processing definition section 6b of the document processing rule table 6 (S40).

[0095] If the result is NO after S40, or if the result is NO in S39, the entire XML document data is read from the top-level element, and processing of each element begins (S41).

[0096] After S41, a new record is created in detail data table 3, and a new unique data key is assigned (S42).

[0097] After S42, the contents of the document unique key and document format ID in document management table 2 are written (S43).

[0098] After S43, the element name, XML hierarchy path, and value information of the element to be processed are written to the data item name, data hierarchy path, and data value fields of the new record in detail data table 3 (S44).

[0099] Next, the process of generating parent-child relationship determination values ​​for the XML hierarchy, calculated values ​​for data occurrence order, and data hierarchy index values ​​is performed, and the resulting values ​​are written to the data hierarchy classification, data occurrence order, and data hierarchy index value fields of the new record in detail data table 3 (S45).

[0100] After S45, refer to the following XML element (S46).

[0101] After S46, it is determined whether the following XML element is absent or not (S47).

[0102] If the answer in S47 is NO, the process returns to S42 and repeats the steps from S42 to S47.

[0103] If the answer to S47 is YES, the process is terminated (detail data creation complete).

[0104] Healthcare information management device 1 stores all healthcare-related information, originating from various sources and in all forms and formats, without any loss. It centrally manages all information and its location, realizing a database infrastructure that allows all stored information to be used in real time and for multiple purposes, and significantly improving efficiency and optimization in terms of expanding data utilization and management costs.

[0105] The healthcare information management device 1 utilizes a document management table 2 that stores a collection of information that can be represented as text data as a single record, and a detail data table 3 that stores information in units of data items while ensuring reversibility by managing the hierarchy and order of data in the original document information. This enables the storage and management of healthcare-related information in various forms and formats, and realizes a database infrastructure that allows for high-speed and multipurpose utilization of that information.

[0106] The healthcare information management device 1 can store data that can be handled in binary formats such as XML, JSON, and CSV used in medical data standards (SS-MIX, HL7-FHIR, etc.), or images and documents (PDF, Word, Excel, image files, etc.), as healthcare-related information in the document management table 2 without any data loss.

[0107] The healthcare information management device 1 ensures traceability of information sources by clearly managing the origin of healthcare-related information stored in the document management table 2.

[0108] In processing the document processing program 5, the healthcare information management device 1 analyzes and decomposes in real time the healthcare-related information stored in the document management table 2 that can be handled or extracted as structured text.

[0109] In the processing of document processing program 5, by adopting a method that converts the data to the XML format shown in Figure 5 before processing, it is possible to decompose the structured text data without loss and ensure reversibility with the original information.

[0110] The healthcare information management device 1 appropriately combines the processing of the document processing program 5 with the definition of the corresponding document processing rule table 6, thereby enabling it to utilize data from the detail data table 3 in real time and without data loss, as the smallest unit data in key-value format consisting of data items and their values, from the healthcare-related information stored in the document management table 2 that can be handled or extracted as structured text.

[0111] The index creation program 7 and index creation rule table 8 enable flexible index creation, ensuring high-speed data retrieval in the document management table 2 and detail data table 3. In addition, the extended index tables 4a, 4b, ... 4n allow for the creation of individual indexes specialized for the purpose and scope of information use, ensuring high-speed data retrieval even when a vast amount of information is stored in the document management table 2 and detail data table 3.

[0112] Since the healthcare information management device 1 can retrieve structured text information stored in the document management table 2 from the detail data table 3 as the smallest unit of data without any data loss, healthcare-related information stored in the healthcare information management device 1 can be applied in real time using SQL, a common database query language.

[0113] As an application of the aforementioned effects, a data conversion table can be arbitrarily created that contains the document format ID defined in the document processing rule table 6 and the contents associated with the data item names and data hierarchy paths in the detail data table 3. By joining or collating this table with the detail data table 3 using SQL, the contents of the data values, data item names, and data hierarchy paths in the detail data table 3 can be converted arbitrarily and in real time.

[0114] In the creation of the aforementioned data conversion table and the conversion process using SQL, by utilizing or creating program functions available within SQL, it is possible to implement a multi-functional and advanced real-time conversion process by combining the contents of the aforementioned data conversion table.

[0115] The creation of the aforementioned data conversion table and the conversion process using SQL can be performed using the SQL view function provided in general database management functions, allowing the converted results to be queried as a virtual table via SQL. This makes it possible to retrieve and use the results of arbitrarily created real-time data conversion processes as a single table.

[0116] As a result of the aforementioned effects, various processes in the application of healthcare-related information can be centrally managed in the healthcare information management device 1, making it available in a simple and reliable manner.

[0117] The present invention enables the centralized and permanent management and storage of medical information and related information generated from various systems and medical devices within a medical institution, as well as healthcare-related information generated from various services and businesses that transcend the boundaries of medical care, nursing care, and public health within a region, all within the healthcare information management device 1. This allows for the optimization of data preservation related to the addition, updating, and decommissioning of systems and equipment, and promotes the reduction of associated costs. Furthermore, because it can perform various data conversions in real time and efficiently simultaneously with information aggregation, it can be used as a foundation for relay devices in various collaborations between medical information within medical institutions and healthcare-related information within a region.

[0118] This invention allows for the storage of healthcare-related information in various forms and formats in text or binary format in a document management table 2 without any data loss. Furthermore, this information can be accessed in real time and without loss from a detail data table 3. Additionally, this information can be transformed according to various applications, and SQL can be used in its utilization. This enhances compatibility with general-purpose applications used for data analysis and visualization, while enabling real-time utilization. Moreover, efficient collaboration between AI and real-time data is possible through the use of SQL and program functions available within SQL, making it suitable as a foundation for learning and application using data across a wide range of healthcare-related fields.

[0119] The present invention is not limited to the embodiments described above, and modifications and other changes can be made without departing from the technical spirit of the present invention. Such modifications and equivalents are also included within the technical scope of the present invention. [Explanation of symbols]

[0120] 1. Healthcare Information Management Device 2. Document Management Table 3. Detailed Data Table 4a, 4b, ...4n... Extended Index Table 5. Document processing program 6. Document Processing Rule Table 7. Indexing program 8. Indexing Rules Table

Claims

1. It has a document management section and a document index section, and stores document data that represents healthcare-related information as a collection of data in structured text or binary data, manages the uniqueness, data format and structure of the document data, and manages the identifier and evidence information of the document data as an index, and a document management table, It has a detail data section and a detail index section, stores the healthcare-related information as unit data of information, consisting of data items and their values, manages the association with the document management table and the document structure, and has an indexed detail data table, By creating an arbitrary table by combining arbitrarily selected items from the data items written to the aforementioned detail data table as column names, an extended index table is created that performs searches within a predefined data range. A document processing program that detects records stored and updated in the aforementioned document management table in real time, reads, analyzes, and decomposes the stored document data, and automatically stores, updates, and deletes it in the aforementioned detail data table. A document processing rule table defines and manages the format of document data stored in the document management table, and defines the processing of the document processing program in association with this format. An index creation program automatically stores, updates, and deletes the contents of the document index section of the document management table, the detail index section of the detail data table, and the contents of the extended index table by reading and processing the data of the detail data table processed by the document processing program after the completion of the document processing program. An index creation rule table defines the processing of the index creation program by associating the data items written to the detail data table with the item names of the document index section of the document management table and the detail index section of the detail data table, and the table name and item names of the extended index table, A healthcare information management device characterized by being equipped with the following features.

2. The healthcare information management device according to claim 1, wherein the document management table pre-sets identifiers for each information source that is the source of the healthcare-related information, assigns a unique document key for each information source that is unique to each identifier, and provides conditions for managing the relationship between the source of the healthcare-related information and the information stored in the document management table.

3. The healthcare information management device according to claim 2, wherein the document management section of the document management table stores each document data item of healthcare-related information to be stored as one record, and includes an item for storing a unique document key to ensure the uniqueness of the stored document data, an identifier for each information source, a unique document key for each information source, information regarding the acquisition of the stored document data, a document format ID representing the format of the document data, and a document data item for storing healthcare-related information read from a file or database as is.

4. The healthcare information management device according to claim 3, wherein the document unique key is automatically assigned a unique value each time a new record is written to the document management table.

5. The healthcare information management device according to claim 1, wherein the document data items in the document management table store the healthcare-related information read from the source of the healthcare-related information in its original format.

6. The healthcare information management device according to claim 1, wherein the document index section of the document management table is provided with items for recording an index and evidence information relating to the recording of healthcare-related information.

7. The detail data section of the detail data table stores the document data stored in the document management table by breaking it down into unit data, and has a data unique key to ensure the uniqueness of the unit data and a document unique key to associate the broken-down data items with the original document, and manages the information necessary to restore the stored data back to the original document data, according to claim 1.

8. The healthcare information management device according to claim 7, wherein the data unique key is automatically assigned a unique value each time a new record is written to the detail data table.

9. The healthcare information management device according to claim 1, wherein the detail index section of the detail data table is provided with an identifier for the person whose healthcare-related information is recorded, and an item for recording an index identifier and index value that can be set from among various data items when used as an index.

10. The healthcare information management device according to claim 1, wherein the document processing program automatically detects records written to the document management table.

11. The healthcare information management device according to claim 1, wherein the document processing rule table is a setting table for setting the operation of a document processing program corresponding to a document format ID, and sets a document format ID, a data format, and processing definition information that defines the processing of a processing program corresponding to the data format.

12. The healthcare information management device according to claim 1, wherein the document processing program obtains a document format ID written to the document management table, obtains corresponding processing definition information from the document processing rule table, reads the document data from the document management table, and performs processing control that branches to pre-prepared processing for each data format, thereby processing the healthcare-related information obtained from various information sources and reflecting it in the detail data table without any loss.

Images