JP5444278B2 - Medical examination data management device, medical examination data management method and program - Google Patents

Description

  The present invention relates to a medical examination data management device, a medical examination data management method, and a program suitable for use in a local government or the like.

  Local governments such as municipalities often aggregate the results of health checkups (hereinafter referred to as health checkups) when providing various health checkup services such as cancer checkups to residents. To report to. However, in many cases, the item names and diagnosis codes of the medical examinations used in the medical examinations conducted in each local government are different from those used when reporting to the country. Therefore, the administrator of the medical examination data in the municipalities often takes time to create the total data to be reported to the country.

  Patent Document 1 standardizes each individual's medical examination data composed of different medical examination items and diagnostic codes for each received medical institution, accumulates the standardized medical examination data in a predetermined database, and accumulates the data in the database. An example of a medical examination data totaling system capable of acquiring various types of medical totaling data using the medical examination data is disclosed.

Japanese Patent Laid-Open No. 06-337901

  However, Patent Document 1 does not describe any technique for using the medical examination data collection system in common in a plurality of municipalities. Moreover, the adoption of this medical examination data totaling system by each municipality means that it is necessary to completely replace the medical examination data management system that is currently used in each municipality. The replacement is costly.

  Accordingly, the present invention provides a medical checkup data that can be easily shared between a plurality of municipalities and a medical checkup data database and a summary process without substantially changing the medical checkup data management system currently used in each municipality. An object of the present invention is to provide a management device, a medical examination data management method, and a program.

The medical examination data management apparatus according to the present invention includes at least one processing device and a storage device, and a first field format (determined for each site) collected at one site for each type of medical examination. and the medical examination data that have a field format), is converted into checkups data having a second field format that is common between the different site and the one site the storage device on The medical checkup data management apparatus registered in the medical checkup result database configured as described above has the following characteristics.

In the storage device in advance,
(1-1) The field name in the medical examination data configured for each type of the medical examination and having the first field format directly corresponds to the field name in the medical examination data having the second field format. A first conversion table to be attached and converted;
(1-2) The values used in the medical examination data field having the first field format configured for each type of the medical examination are used in the medical examination data field having the second field format. A second conversion table for converting in direct correspondence with values;
(1-3) A count condition table that represents count conditions for acquiring specific checkup data for each type of checkup from the checkup result database is stored.
And the processing device
(2-1) A medical examination data input unit that receives input of medical examination data having the first field format according to the type of the medical examination ;
(2-2) Using the first conversion table and the second conversion table according to the type of the medical examination , the second medical examination data having the accepted first field format is used as the second conversion table. A data converter for converting into medical examination data in field format;
(2-3) a database management unit that registers the converted medical examination data in the second field format in the medical examination result database for each type of the medical examination;
(2-4) The case of accepting a request for current meter processing, medical examination data corresponding to the aggregation condition for each type of the medical examination specified by the previous SL current meter condition table is acquired from the medical examination result database A totalization processing unit that totalizes the acquired medical examination data for each type of the medical examination ;
(2-5) and aggregate data output unit for outputting to an output device aggregated results for each type of the medical examination,
It is provided with.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes easy to make common the database and totaling process of medical examination data between several municipalities, without changing the medical examination data management system currently used in each municipality.

The figure which showed the example of the structure of the medical examination data management apparatus which concerns on embodiment of this invention. The figure which showed the example of the structure of the stomach cancer medical examination master table and the colon cancer medical examination master table which are contained in a medical examination result database. The figure which showed the example of the structure of the stomach cancer consultation data and the colorectal cancer consultation data which are used in the site A (municipalities A). The figure which showed the example of the structure of the stomach cancer medical examination data and the colorectal cancer medical examination data which are used in the site B (municipalities B). The figure which showed the example of the structure of the field name conversion table and the field value conversion table. The figure which showed the example of the structure of the total condition table. The figure which showed the example of the processing flow of the medical examination data registration process and the medical examination data totaling process in the medical examination data management apparatus which concerns on embodiment of this invention. The figure which showed the example of the document which printed the total result of medical examination data.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an example of the configuration of a medical examination data management apparatus according to an embodiment of the present invention. As shown in FIG. 1, a medical examination data management apparatus 100 according to an embodiment of the present invention includes a medical examination database management apparatus 1 and one or a plurality of medical examination data management terminals 2.

  The medical examination database management device 1 is configured by a so-called computer having at least a processing device 10 and a storage device 15. The storage device 15 includes a field name conversion table 16, a field value conversion table 17, a totaling condition table 18, a medical examination result database 19, and the like. The processing device 10 includes a data conversion unit 12, Functional blocks such as the database management unit 11 and the aggregation processing unit 13 are configured. Note that the functions of these functional blocks (the data conversion unit 12, the database management unit 11, and the totalization processing unit 13) are all the programs stored in the storage device 15 by the arithmetic processing unit (not shown) of the processing device 10 in advance. This is realized by reading and executing.

  The medical examination data management terminal 2 includes a processing device 20, a storage device (not shown), an input device 25 (such as a keyboard and a mouse), a display device 24 (such as a liquid crystal display), and a personal computer that includes a printer 26. The The processing device 20 includes functional blocks such as a medical examination data input unit 21, a totaling process request unit 22, and a totaling data output unit 23. Note that all of the functions of these functional blocks (the medical examination data input unit 21, the totaling process request unit 22, and the totaling data output unit 23) are stored in a storage device (not shown) by an arithmetic processing unit (not shown) of the processing device 20. This is realized by reading and executing the program being executed.

  Here, it is assumed that the medical examination database management device 1 and the medical examination data management terminal 2 are communicably connected via a communication bus or a communication network (not shown). Further, the medical examination database management device 1 and the medical examination data management terminal 2 may be configured by one computer, or may be configured by a plurality of computers housed in one housing or the like. .

  The medical examination result database 19 is a database in which data of health examination results such as individual cancer medical examinations (hereinafter simply referred to as medical examination data) is registered. Consists of tables. Hereinafter, in this embodiment, a table constituting the medical examination result database 19 is referred to as a master table. In the present specification, a table referred to as a master table means a table shared by a plurality of sites, that is, a plurality of municipalities.

  Next, an example of the configuration of the master table in the medical examination result database 19 will be described with reference to FIGS. FIG. 2 is a diagram illustrating an example of the configuration of the stomach cancer medical examination master table 191 and the colorectal cancer medical examination master table 192 included in the medical examination result database 19.

  First, as shown in FIG. 2 (a), the stomach cancer medical examination master table 191 includes fields of “diagnosis code”, “date of medical examination”, “medical institution”, and “stomach cancer medical examination result”. Consists of. In addition, as shown in FIG. 2B, the colorectal cancer health checkup master table 192 includes the “checkee code”, “date of checkup”, “medical institution”, and “colorectal cancer checkup result”. Consists of fields. It should be noted that the stomach cancer medical examination master table 191 and the colorectal cancer medical examination master table 192 may include other fields, for example, a field such as “age of the examinee”.

  FIG. 3 is a diagram showing an example of the configuration of stomach cancer consultation data and colorectal cancer consultation data used at site A (city / town / village A). FIG. 4 is a diagram showing an example of the configuration of stomach cancer medical examination data and colorectal cancer medical examination data used at site B (municipal town B). In addition, these data are data input into the data conversion part 12 via the input device medical examination data input part 21 (refer FIG. 1).

  As shown in FIG. 3A, the stomach cancer consultation data 211 at “site A” is configured to include fields such as “consultant code”, “visit date”, “hospital name”, and “visit result”. . In addition, as shown in FIG. 3B, the colorectal cancer medical examination data 212 in “site A” includes fields such as “diagnosis code”, “visit date”, “hospital name”, and “visit result”. Consists of including.

  Similarly, as shown in FIG. 4A, the stomach cancer medical examination data 211b in “site B” includes fields such as “examinee”, “health examination hospital”, “health examination date”, “gastric cancer determination”, and the like. Consists of including. Further, as shown in FIG. 4B, the colorectal cancer medical examination data 212b at “Site B” includes “examinee”, “health examination hospital”, “health examination date”, “colorectal cancer determination”, and the like. It is comprised including the field of.

  As described above, as can be seen from the examples of FIGS. 3 and 4, the medical checkup data used at each site includes the names of the medical checkup data and the fields constituting the medical checkup data for each site or for each type of checkup data. , The order of fields, and the data (values) used in each field are slightly different.

  In view of this, in the medical examination database management apparatus 1 according to the present embodiment, the data conversion unit 12 stores medical examination data such as stomach cancer medical examination data 211 and colorectal cancer medical examination data 212 input via the medical examination data input unit 21. The field format is converted into a common (standardized) field format in advance, and then registered in the medical examination result master table of the medical examination result database 19 via the database management unit 11. Here, the field format of the medical examination data is a generic name of the names of the fields constituting the medical examination data, the order of field arrangement, the values used in the fields, and the like.

  FIG. 5 is a diagram showing an example of the configuration of the field name conversion table 16 and the field value conversion table 17. The field name conversion table 16 is a table for associating the field names of the medical examination data input from the medical examination data input unit 21 with the field names of the master table in the medical examination result database 19. The field value conversion table 17 includes a value used in a field of medical examination data input from the medical examination data input unit 21 and a value used in a field of a master table corresponding to the field of medical examination data. It is a table for associating.

  That is, as shown in FIG. 5A, the field name conversion table 16 for the site A includes “master table name”, “input data name”, “master table / field name (# 1)”, “input data”. -Field name (# 1) ", ...," master table / field name (# 4) "," input data field name (# 4) ". Here, the structure of the record is shown in the vertical direction.

  In the record configuration, the master table corresponding to the “input data name” can be selected by the fields of “master table name” and “input data name”. Further, the subsequent fields of “master table field name (#j)” and “input data field name (#j)” (j = 1,... Corresponds to field names. In FIG. 5A, the number of fields is four, but is not limited to four.

  Similarly, the field value conversion table 17 includes a value registered in a field of the master table and a value of a field of input data corresponding to the field of the master table for each field of the master table of the medical examination result. It is a table to associate.

  That is, as shown in FIG. 5B, the field value conversion table 17 for the site A includes “master table name”, “input data name”, “master table / field name”, “input data / field name”. , “Master table value (# 1)”, “input data value (# 1)”, “master table value (# 2)”, “input data value (# 2)”, “master table value (# 3)” , “Input data value (# 3))”. Each of the fields is shown in the vertical direction.

  And in the record structure, the fields of the master table and the input data are defined by the fields of “master table name” and “input data name”, and “master table field name” and “input data field name”. Fields are associated. Further, according to the fields of “input data value (#k)” and “master table value (#k)” (k = 1,..., 3), the corresponding master table field and input data field respectively. The values used in are associated. In FIG. 5B, the maximum value of k is “3”, but is not limited to “3”.

  Incidentally, according to the first record (vertical direction) of the field value conversion table 17 in FIG. 5B, it is used in the “consultation result” field of the stomach cancer consultation data 211 (see FIG. 3A) as input data. The values of “no abnormality”, “necessary examination”, and “stomach cancer” are used in the “stomach cancer checkup result” field of the stomach cancer checkup master table 191 (see FIG. 2A), respectively. Corresponding values of “1”, “2” and “3” are shown. The values “1”, “2”, and “3” may be text values such as “normal”, “necessary examination”, and “stomach cancer”, respectively.

  Similarly, according to the second record (vertical direction), “normal” and “necessary examination” used in the “consultation result” field of the colorectal cancer consultation data 212 (see FIG. 3B). , The values “colon cancer” are “1”, “2”, “value” used in the “stomach cancer checkup result” field of the colorectal cancer checkup master table 192 (see FIG. 2B), respectively. It corresponds to a value of “3”. The values “1”, “2”, and “3” may be text values such as “normal”, “need detailed examination”, and “colorectal cancer”, respectively.

  Therefore, the data conversion unit 12 refers to the field name conversion table 16 and the field value conversion table 17 to change the field format of the medical examination data input from the medical examination data input unit 21 to the name of the medical examination data. Convert to master table field format with associated name. And the database management part 11 registers the converted medical examination data in the master table in the medical examination result database 19 matched with the medical examination data.

  In the field value conversion table 17, “master table name” and “master table / field name” do not exist for “input data name” and “input data / field name” of the medical examination result data to be input. In that case, the value of that field shall not be converted.

  For example, it is assumed that the input data is stomach cancer consultation data 211 (see FIG. 3A). At that time, in the field value conversion table 17 in FIG. 5B, there is a record in which “input data name” is “stomach cancer consultation” and “input data field name” is “consultation result”. . Therefore, the value of the “consultation result” field of the gastric cancer consultation data 211 corresponds to the “input data value (#k)” and “master table value (#k)” (k = 1,..., 3) of the record. Converted according to On the other hand, in the field value conversion table 17 in FIG. 5B, there is no record in which “input data name” is “stomach cancer consultation” and “input data field name” is “health care hospital”. . Therefore, the value of the “health checkup hospital” field of the stomach cancer consultation data 211 is not converted.

  As described above, according to the present embodiment, the medical examination data management apparatus 100 has, for example, a field format of a master table in which medical examination result data having a field format arbitrarily defined for each site is shared by a plurality of sites. Can be easily converted and stored in the medical examination result database 19. Therefore, for example, even if a certain municipality (site) employs the medical examination data management apparatus 100 according to this embodiment, it is not necessary to change the current medical examination data management.

  In addition, although it is preferable to prepare one set of the medical examination data management apparatus 100 for each site, the part of the medical examination database management apparatus 1 of the medical examination data management apparatus 100 may be shared by a plurality of sites. Is possible. In this case, the field name conversion table 16, the field value conversion table 17, and the medical examination result database 19 are provided for each site.

  FIG. 6 is a diagram showing an example of the configuration of the aggregation condition table 18. As shown in FIG. 6, the aggregation condition table 18 includes “master table name”, “field name (# 1)”, “field value (# 1)”, “field name (# 2)”, “field value ( # 2) ”field.

  Here, the “master table name” field is information for specifying a master table to be aggregated. The “field name (#m)” and “field value (#m)” fields (m = 1, 2) are “field name (#m)” of the master table specified in the “master table name” field. This is condition information that means that the value of the field specified by is “field value (#m)”. In this condition information, two conditions of m = 1 and 2 are provided here, but the number of conditions is not limited to “2”.

  Incidentally, the condition information represented by the aggregation condition table 18 in the example of FIG. 6 is “the date of medical examination” in the stomach cancer medical checkup master table 191 (see FIG. 2A) is “10 ***”. * "And the value of the field of" stomach cancer checkup result "is" 3 ", and the" date of consultation "in the colorectal cancer checkup master table 192 (see FIG. 2B) Records with a field value of “10 ***” (ie, “date of medical examination” is “2010”) and a field value of “colorectal cancer medical examination result” is “3” The numbers and numbers are summed up. ] Means. Note that “***” in the “Date of Visit” field is a wild card.

  As described above, the value of each field of the aggregation condition table 18 is expressed using the table name, field name, and field value included in the master table included in the medical examination result database 19 shared by a plurality of sites. The Therefore, when the same contents are aggregated at a plurality of sites, the contents of the aggregation condition table 18 are the same at the plurality of sites. That is, the aggregation condition table 18 is shared by a plurality of sites.

  Note that the totaling condition table 18 is not limited to one, and a plurality of types may be created in advance and stored in the storage device 15 of the medical examination database management device 1. Therefore, the totalization processing unit 13 uses the various totaling condition tables 18 stored in the storage device 15 as appropriate, so that, for example, the national government can easily calculate the total data regarding the medical examination data that the country requests to be submitted to each local government. Can be sought.

  In this case, since the totaling condition table 18 is shared by each site, even if the method of totaling medical checkup data required by the country is changed, in this embodiment, any one site is used. If the contents of the aggregation condition table 18 are changed, the contents can be applied to the aggregation condition table 18 of another site as it is. That is, in the present embodiment, the aggregation condition table 18 is unified between sites.

  FIG. 7 is a diagram illustrating an example of a processing flow of the medical examination data registration process and the medical examination data aggregation process in the medical examination data management apparatus 100 according to the embodiment of the present invention. The processing flow will be described below with reference to the drawings such as FIG.

  When a medical examination is performed at a medical institution or the like, medical examination data representing the result of the medical examination is first input to the medical examination data management terminal 2 via the input device 25. In general, medical examination data of a medical institution is often described on a paper sheet or the like. In this case, an operator inputs the description content from a keyboard or the like. Alternatively, when the medical examination data of the medical institution is composed of a mark sheet, an OCR (Optical Card Reeder) or the like is used as the input device 25.

  If there is some medical examination data management system in a municipality or the like and the medical examination data is already stored in the form of a database table in a hard disk device or the like, the input device 25 is stored from the hard disk device. It is also possible to directly read the medical examination data.

  Therefore, as shown in FIG. 7A, the processing device 20 (checkup data input unit 21) of the checkup data management terminal 2 first reads checkup data input via the input device 25 (step). S11), the read medical examination data is transferred to the medical examination database management apparatus 1. Note that the field format of the medical examination data used when reading the medical examination data differs depending on the type of the medical examination data as shown in FIGS. 3 and 4, and also differs from site to site. It doesn't matter.

  Next, the processing device 10 (data conversion unit 12) of the medical examination database management device 1 converts the transferred medical examination data into the field format of the master table (step S12). Here, as described above, the master table is a table in which medical examination data is registered in the medical examination result database 19 (for example, FIG. 2 (a) stomach cancer medical examination master table 191 and (b) colorectal cancer medical examination master. Table 192 etc.).

  Next, the processing apparatus 10 (database management unit 11) registers the medical examination data converted into the field format of the master table in the master table corresponding to the medical examination data (step S13).

  Here, the process of converting the medical examination data field format in step S12 will be briefly supplemented below. In step S12, the processing device 10 refers to the field name conversion table 16 (for example, see FIG. 5A) using the input data name of the input data to be converted, and converts the field name (that is, the field Record to be used for association). Further, the processing device 10 refers to the field value conversion table 17 (for example, see FIG. 5B) using the input data name and field name of the input data to be converted, and converts the value in the field. Get the record to use.

  Next, the processing device 10 uses the acquired record data for field name conversion and the record data for field value conversion to use the field format (field name, order, Field value) is converted to the field format of the master table.

  Through the above-described medical examination data registration process, the medical examination data input from the input device 25 or the like is stored in a master table shared by a plurality of sites even if the field format is different for each type of medical examination data or each site. It is converted into a field format and registered in the medical examination result database 19.

  On the other hand, in the medical examination data totaling process shown in FIG. 7B, the processing device 20 (totaling processing request unit 22) of the medical examination data management terminal 2 first receives a totalization processing request input via the input device 25. (Step S21), the medical examination database management device 1 is requested to specify the totaling conditions and request the medical data to be totaled.

  When receiving the aggregation request from the medical examination data management terminal 2, the processing device 10 (aggregation processing unit 13) of the medical examination database management apparatus 1 acquires the aggregation condition table 18 corresponding to the designated aggregation condition (step S22). ), Through the database management unit 11, medical examination data that meets the aggregation conditions is acquired from the master table specified in the aggregation condition table 18 (step S23). Then, the processing device 10 (aggregation processing unit 13) aggregates the acquired medical examination data (step S24), and returns the aggregation result to the medical examination data management terminal 2.

  Next, when the processing device 20 (aggregation processing request unit 22) of the medical examination data management terminal 2 receives the aggregation result from the medical examination database management device 1, the aggregation result is output to an output device such as the printer 26 or the display device 24. Output (step S25).

  FIG. 8 is a diagram showing an example of a document on which the result of the medical examination data is printed. As shown in FIG. 8, the medical checkup results are described for each type of medical checkup, for example, the number of people whose gastric cancer checkup results were “normal”, “necessary examination”, or “stomach cancer”, respectively. Configured. Item names such as “normal”, “necessary examination”, and “stomach cancer” used here are printed at multiple sites by matching the field names and field values used in the master table. Documents can be easily shared.

  As described above, according to the present embodiment, the field name conversion in which the field name of the medical examination data input at each site is associated with the field name of the master table in the medical examination result database 19 in which the medical examination data is registered. By using the table 16 and the field value conversion table 17 in which the field value used in the field of the medical examination data input at each site and the field value used in the master table corresponding to the field are associated, Even if the field format of input data is different at each site, those field formats can be easily shared.

  In the present embodiment, a totaling condition table 18 is prepared, and a master table corresponding to the totaling condition represented by the totaling condition table 18 and its records can be easily extracted from the medical examination result database 19. In addition, field names and field values used in the master table in the medical examination result database 19 are used as the aggregation conditions. For this reason, the aggregation conditions, that is, the aggregation process can be easily made common to a plurality of sites.

  As described above, in the present embodiment, it is easy to construct the medical examination result database 19 including a master table having a field format common to a plurality of sites. Furthermore, by preparing the tabulation condition table 18 that is shared among a plurality of sites, it is easy to share the tabulation processing performed between the plurality of sites.

DESCRIPTION OF SYMBOLS 1 Medical examination database management apparatus 2 Medical examination data management terminal 10 Processing apparatus 11 Database management part 12 Data conversion part 13 Total processing part 15 Storage device 16 Field name conversion table 17 Field value conversion table 18 Totaling condition table 19 Medical examination result database 20 Processing device 21 Medical examination data input unit 22 Total processing request unit 23 Total data output unit 24 Display device 25 Input device 26 Printer 100 Medical examination data management device 191 Gastric cancer medical examination master table 192 Colon cancer medical examination master table 211 Gastric cancer medical examination data (Checkup data)
211b Gastric cancer medical examination data (medical examination data)
212 Colorectal cancer consultation data (medical examination data)
212b Colorectal cancer health examination data (health examination data)

Claims (3)

Comprising at least one or more processing devices and the storage device, for each type of medical examination, the medical examination data that have a first field type collected in 1 site, different from said first site A medical examination data management device for converting into medical examination data having a second field format shared with a site and registering it in a medical examination result database configured on the storage device,
In the storage device in advance,
A field name in the medical examination data that is configured for each type of the medical examination and has the first field format is converted in association with a field name in the medical examination data that has the second field format. 1 conversion table,
The value used in the medical examination data field having the first field format, which is configured for each type of the medical examination, is directly set to the value used in the medical examination data field having the second field format. A second conversion table for conversion in association;
A totaling condition table representing a totaling condition for acquiring specific medical examination data for each type of the medical examination from the medical examination result database;
And store
The processor is
A medical examination data input unit for receiving input of medical examination data having the first field format according to the type of the medical examination ;
Using the first conversion table and the second conversion table corresponding to the type of the medical examination , the medical examination data having the received first field format is used as the medical examination data in the second field format. A data conversion unit for converting data,
A database management unit for registering the converted medical examination data in the second field format in the medical examination result database for each type of the medical examination;
Ken upon receiving a request for collecting a total treatment, medical examination data corresponding to the count condition of each type of the medical examination specified by the previous SL current meter condition table, which is obtained from the medical examination result database, and the acquired A summary processing unit for summing up medical examination data for each type of medical examination ;
And aggregate data output unit for outputting to an output device results aggregated per type of the medical examination,
A medical examination data management device characterized by comprising: At least includes a computer with one or more processing devices and the storage device, for each type of medical examination, the medical examination data that have a first field format that is collected on one site, and the one site a is a second converted to examination data with field format, the stored configuration on the device the checkup result to register in the database checkup data management method that is common between the different sites ,
In the storage device in advance,
A field name in the medical examination data that is configured for each type of the medical examination and has the first field format is converted in association with a field name in the medical examination data that has the second field format. 1 conversion table,
The value used in the medical examination data field having the first field format, which is configured for each type of the medical examination, is directly set to the value used in the medical examination data field having the second field format. A second conversion table for conversion in association;
A totaling condition table representing a totaling condition for acquiring specific medical examination data for each type of the medical examination from the medical examination result database;
And store
The processor is
A process of receiving input of medical examination data having the first field format according to the type of the medical examination ;
Using the first conversion table and the second conversion table corresponding to the type of the medical examination , the medical examination data having the received first field format is used as the medical examination data in the second field format. Processing to convert to data,
Processing for registering the converted second field format medical examination data in the medical examination result database for each type of the medical examination;
Ken upon receiving a request for collecting a total treatment, medical examination data corresponding to the count condition of each type of the medical examination specified by the previous SL current meter condition table, which is obtained from the medical examination result database, and the acquired A process of summing up medical examination data for each type of medical examination ;
And outputting to an output device results aggregated per type of the medical examination,
The medical examination data management method characterized by performing this.   A program for causing a computer to execute the medical examination data management method according to claim 2.

Images