JP2014157393A - Information management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information management system that can prevent a duplicative medication, medical insection and the like by checking a duplicative medical diagnosis such as the medication, the medical inspection and the like across a plurality of medical institutions when the insured gets a medical care from the plurality of medical institutions, and can prevent increase in a medical expenditure.SOLUTION: An information management system comprises: a receipt claim information editing process section 103 that when the insured gets a medical treatment from a plurality of medical institutions, receives information on the insured transmitted from the plurality of medical institutions and information on a use date when the insured uses the medical institution and a medical treatment compensation statement, and stores the received information in a database; a computer-assisted name identification process section 104 that verifies whether the insured uses a different medical institution for a fixed period of time to receive an offering of a medical action on the basis of the information stored in the database; and a recommendation medical institution list preparation process section 105 that verifies whether the insured receives the offering of the same medical action, using the different medical institution for the fixed period of time.

Description

  The present invention relates to an information management system for managing information such as service content and cost burden when a user receives a service provided by a plurality of service providing organizations, and in particular, a plurality of users who are insured persons. This relates to management of medical information on the insurer side when using a medical institution.

  With the spread of IT systems in recent years, the introduction of medical IT systems has been actively promoted in the medical industry.

  In particular, in the medical office system, the computer processing of the receipt, which is a medical fee remuneration statement to be submitted to the payment fund / National Federation of Health Insurance and the insurer, has been computerized [receipt computing system (guide for creating electronic receipts), Social insurance medical fee payment fund, see July 2012 (Non-Patent Document 1)].

  In addition, in the medical institution unit, duplicate medical checkups such as medication and examination are performed based on the receipt computer data [see Japanese Patent Laid-Open No. 2009-140057 (Patent Document 1)].

JP 2009-140057 A

Receipt computer system (Guide for creating electronic receipts), Social insurance medical fee payment fund, July 2012

  However, in the past, the insured has checked for duplicate medical treatment such as medication and inspection when the medical institution has visited each medical institution.・ Due to the lack of checking for duplicate medical examinations such as examinations, medical expenses were also increasing.

  In addition, there is no system for checking the use of duplicate services at a plurality of service providing organizations when a user uses a plurality of service providing organizations as well as medical institutions.

  Therefore, an object of the present invention is to provide an information management system capable of preventing duplication of services when a user uses a plurality of service providing organizations and receives the same service at a plurality of service providing organizations. There is to do.

  In addition, when the service provider is a medical institution, when the insured has received a plurality of medical institutions, by checking for duplicate medical treatment such as medication and inspection across multiple medical institutions, An object of the present invention is to provide an information management system capable of preventing duplicate medications and examinations and preventing an increase in medical expenses.

  The above and other objects and novel features of the present invention will be apparent from the description of this specification and the accompanying drawings.

  Of the inventions disclosed in the present application, the outline of typical ones will be briefly described as follows.

  In other words, the outline of typical ones is the user information transmitted from multiple service providers when the user uses multiple service providers, and the information when the user uses the service providers. Receives information on the date of use and service, and stores the received information in a database.

  Then, based on the information stored in the database, it is confirmed whether the user has been provided with a service by using a different service provider for a certain period, and further, a different service provider is used for a certain period. If the same service is received, information on the service provider nearest to the user is output.

  The effects obtained by typical ones of the inventions disclosed in the present application will be briefly described as follows.

  That is, the effect obtained by the representative one can prevent duplication of services when the user receives the same service at a plurality of service providing organizations when the user uses a plurality of service providing organizations.

  In addition, when the service provider is a medical institution, if the insured who is the user has received medical examinations from multiple medical institutions, check for duplicate medical treatments such as medication and inspection across multiple medical institutions. By doing so, it is possible to prevent duplicate medications and tests, and to prevent an increase in medical costs.

It is a block diagram which shows the structure of the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and data example of medical institution DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and data example of insured DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and example of data of standard receipt computer information DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and example of data of standard receipt computer information DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and example of data of standard receipt computer information DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and example of data of standard receipt computer information DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and example of data of standard receipt computer information DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and data example of insured medical care information storage DB used with the information management system which concerns on one embodiment of this invention. It is a figure which shows the structure and data example of work area DB which are used with the information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the whole information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the receipt claim information edit process of the whole information management system which concerns on one embodiment of this invention. It is a flowchart which shows operation | movement of the medical institution information determination process of the whole information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the insured person information determination process of the whole information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the whole medical treatment information determination process of the information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the whole name identification process of the information management system which concerns on one embodiment of this invention. It is a flowchart which shows the operation | movement of the recommendation medical institution list creation process of the whole information management system which concerns on one embodiment of this invention. It is a figure which shows the non-insured error list output during operation | movement of the information management system which concerns on one embodiment of this invention. It is a figure which shows the multiple medical institution consultation confirmation table output during the operation | movement of the information management system which concerns on one embodiment of this invention. It is a figure which shows the recommended medical institution list | wrist output during the operation | movement of the information management system which concerns on one embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

<Configuration of information management system>
With reference to FIG. 1, the configuration of an information management system according to an embodiment of the present invention will be described. FIG. 1 is a configuration diagram showing a configuration of an information management system according to an embodiment of the present invention. An insured person's insured medical information management system when an insured uses a plurality of medical institutions. It is shown as an example of an information management system.

  In FIG. 1, an insured medical care information management system 102, which is an information management system, operates on a server 101 installed on the insurer side.

  The insured medical information management system 102 includes a receipt request information editing processing unit 103 that is an information editing processing unit, a name identification processing unit 104, and a recommended medical institution list creation processing unit 105 that is a recommended service providing organization creation processing unit. The database includes a standard receipt computer information DB 106, an insured person DB 107, a medical institution DB 108, an insured person medical information storage DB 109, and a work area DB 115.

  On the medical institution side, each of the server of the medical institution A110 and the server of the medical institution B113 has standard receipt computer information DBs 111 and 114, and stores information on the receipt, which is medical information of the insured.

  The server of the medical institution A110, the server of the medical institution B113, and the insured medical information management system 102 are connected via the network 112, and the information stored in the standard receipt computer information DBs 111 and 114 is insured. To the medical care information management system 102.

  The insured medical information management system 102 receives information stored in the standard receipt computer information DBs 111 and 114 transmitted from each medical institution, and based on the received information, the insured has consulted with a plurality of medical institutions. Check for duplicate medical treatments such as medications and tests, and introduce recommended medical institutions close to the insured's address.

<Structure of each database>
Next, the structure and data example of each database used in the information management system according to the embodiment of the present invention will be described with reference to FIGS. 2 to 10 are diagrams showing structures and data examples of each database used in the information management system according to the embodiment of the present invention.

  2 shows the medical institution DB 108, FIG. 3 shows the insured person DB 107, FIGS. 4 to 8 show the standard receipt computer information DBs 106, 111, and 114, FIG. 9 shows the insured person medical information storage DB 109, and FIG. 10 shows the work area DB 115. ing.

  The medical institution DB 108 is a database that stores information on each medical institution. As shown in FIG. 2, the medical institution number “HP-NO” in which the medical institution is coded and the medical institution displayed in kanji as “ Data of “HP-NAME”, telephone number “HP-TEL”, postal code “HP-ADNO”, and address “HP-AD” are stored.

  As an example of data in the medical institution DB 108, as shown in FIG. 2, “HP-NO” is 131345, “HP-NAME” is Tokyo XX Information Hospital, “HP-TEL” is 03-1234-1234, “HP "-ADNO" is information such as 124-0011, and "HP-AD" is information such as Katsushika-ku, Tokyo.

  Further, the insured person DB 107 is a database storing information on the insured person and each medical institution visit history of the insured person, and as shown in FIG. The insured person number “P-HIPNO”, the name of the insured person “P-NAME”, the gender of the insured person (eg, male = 1, female = 2) Information of “P-SEX” and the date of birth “P-BIRTH” which is the date of birth of the patient is stored.

  Further, the insured person's postal code “P-ADNO”, the insured person's address “P-AD”, the insurer number “P-HONO”, the insured person's identification symbol “P-HIKIGO”, the insured person's identification number "P-HINO", medical treatment date (1) "P-HIYM01", consultation medical institution number (1) "P-HPNO01", medical treatment date (NN) "P-HIYMNN", medical examination institution number (NN) Information of “P-HPONN”, medical date (100) “P-HIYM100”, and medical institution number (100) “P-HPNO100” is stored.

  “P-HIYM01”, “P-HPNO01” to “P-HIYM100”, and “P-HPNO100” are stored repeatedly.

  As an example of data in the insured person DB 107, as shown in FIG. 3, “P-HIPNO” is 0123567, “P-NAME” is Taro XX, “P-SEX” is 1, and “P-BIRTH” is 19500110. , "P-ADNO" is 124-0111, "P-AD" is Katsushika-ku, Tokyo KK, "P-HONO" is 06130010, "P-HIKIGO" is Tama, "P-HINO" is 1234567, etc. is there.

  In addition, “P-HIYM01” is information such as “20113”, “P-HPNO01” is 13212345, etc., and “P-HIYM01”, “P-HPNO01” to “P-HIYM100”, “P-HPNO100” are changed to the medical year. Month and medical institution number are stored repeatedly.

  The standard receipt computer information DB 106 is a database in which medical information sent from each medical institution is stored, and is a receipt computer processing system (electronic receipt creation guide created by the Social Insurance Medical Fee Payment Fund approved by the Ministry of Health, Labor and Welfare). ) Based on the format.

  In this format, the record identification of the request hospital information = IR, the record identification of the receipt common information = RE, the record identification of the insurance information = HO, the record identification of the drug information = IY, and the record identification of the medical practice information = SI. Each information is stored.

  As shown in FIG. 4, the database of the record type = IR of the standard receipt computer information DB 106 includes, as items, identification of the receipt computer (IR) request hospital information “IR-KUBUN”, examination paying institution (fixed to “1”) “ IR-SINSA ”, prefecture code“ IR-KENCOOD ”, score table classification (fixed to“ 1 ”)“ IR-TEN ”, medical institution number (same as insured medical institution number)“ IR-HPNO ” Is done.

  Furthermore, spare “IR-YOBI”, medical institution name (displayed in Chinese characters) “IR-HPNAME”, billing date (eg, July 2010 = 42207) “IR-SEIKYUYM”, multi-volume identification (medium is (First item = 00, second item = 01) Information on “IR-MARTI” and the telephone number “IR-TEL” of the medical institution is stored.

  As an example of data in the database of the record type = IR of the standard receipt computer information DB 106, as shown in FIG. 4, “IR-KUBUN” is IR, “IR-SINSA” is 1, “IR-KENCOOD” is 13, “IR-TEN” is 1, “IR-HPNO” is 131345, “IR-YOBI” is Δ △, “IR-HPNAME” is Tokyo XX Information Hospital, “IR-SEIKYUYM” is 42304, “IR-MARUTI” is 00, “IR-TEL” is information such as 03-1234-1234.

  In addition, as shown in FIG. 5, the database of record type = RE in the standard receipt computer information DB 106 includes, as items, an identifier (RE) receipt common information “RE-KUBUN”, a receipt number (the upper part of the stored RE data). Ascending order serial number) “RE-RENO”, information of the receipt type (for example, company insurance individual in-patients = 1111) and “RE-RESYUBETU” are stored.

  Furthermore, the date of medical care (eg, July 2010: 42207) “RE-SINYM”, the name of the patient displayed in Chinese characters “RE-PNAME”, the gender of the patient (eg, male = 1, female = 2) Information of “RE-SEX”, the date of birth of the patient (eg, when born on November 15, 1973 = 3481115) “RE-BIRTH”, and other information “RE-SONOTA” are stored.

  As an example of data in the database of the record type = RE of the standard receipt computer information DB 106, as shown in FIG. 5, “RE-KUBUN” is RE, “RE-RENO” is 1, “RE-RESYUBETU” is 1111, “ “RE-SINYM” is 42303, “RE-PNAME” is xx Taro, “RE-SEX” is 1, “RE-BIRTH” is 3250110, and the like.

  Further, as shown in FIG. 6, the database of record type = HO in the standard receipt computer information DB 106 includes, as items, identification of receipt computer (HO) insurance information “HO-KUBUN”, the insured number of the insured. The insurer number “HO-HONO”, the insured person symbol “HO-HIKIGOU”, the insured person number “HO-HINO”, and other information “HO-SONOTA” are stored.

  As an example of data in the database of the record type = HO of the standard receipt computer information DB 106, as shown in FIG. 6, “HO-KUBUN” is HO, “HO-HONO” is 06130010, “HO-HIKIGOU” is OO Tama , “HO-HINO” is information such as 1234567.

  In addition, as shown in FIG. 7, the database of record type = IY in the standard receipt computer information DB 106 includes, as items, identification of receipt computer (IY) medicine information “IY-KUBUN”, medical treatment category (example , Medication action = 20, injection action = 30) Information of “IY-SINKUBUN” is stored.

  Furthermore, a burden classification (eg, insurance = 1) “IY-HUTANKUBUN”, which is a classification of which insurance will cover the corresponding action, a medical practice code (a 9-digit payment fund code) that is a receipt standard code -SINCOOD ", the usage amount of the medical practice code" IY-SUURYOU ", and other information" IY-SONOTA "are stored.

  As an example of the data in the database of the record type = IY of the standard receipt computer information DB 106, as shown in FIG. Information such as “IY-SINCOOD” is 613920056 and “IY-SUURYOU” is 3.

  Further, as shown in FIG. 8, the database of record type = SI in the standard receipt computer information DB 106 includes, as items, identification of receipt computer (SI) medical practice information “SI-KUBUN”, clinical practice classification (medical practice classification ( Example, inspection action = 60, image action = 70) Information of “SI-SINKUBUN” is stored.

  Furthermore, a burden classification (eg, insurance = 1) “SI-HUTANKUBUN”, which is a classification of which insurance will bear the corresponding action, a medical practice code (a 9-digit payment fund code) that is a receipt standard code -SINCOOD ", the usage amount of the medical practice code" SI-SUURYOU ", and other information" SI-SONOTA "are stored.

  As an example of data in the database of the record type = SI of the standard receipt computer information DB 106, as shown in FIG. 8, “SI-KUBUN” is SI, “SI-SINKUBUN” is 60, “SI-HUTANKUBUN” is 1, Information such as “SI-SINCOOD” is 160039110, and “SI-SURUYOU” is 1.

  The insured medical care information storage DB 109 is a database that stores medical care information carried out at each medical institution for each insured. As shown in FIG. Insured person number “HP-HIPNO”, medical date (eg, July 2010 = 201007: AD conversion) “HP-SNYM”, medical institution number (same as insured medical institution number) ) "HP-HPNO", information of the receipt type (eg, company insurance single in-patient person = 1111) and "HP-RESYUBETU" are stored.

  Furthermore, the billing date (eg, July 2010 = 201007: AD conversion) “HP-SEIKYUYUM”, repetitive serial number “HP-TUUBAN”, receipt computer identification (IY) or (SI) “HP-KUBUN”, Medical treatment classification (for example, medication action = 20, injection action = 30, inspection action = 60, image action = 70) “HP-SINKUBUN”, clinical code of receipt standard code (9-digit numeric value) Information of “payment fund code” “HP-SINCOOD” and the usage amount “HP-SUURYO” of the medical practice code is stored.

  As an example of data in the insured medical care information storage DB 109, as shown in FIG. 9, “HP-HIPNO” is 0123567, “HP-SINYM” is 201103, “HP-HPNO” is 131345, and “HP-RESYUBETU” is 1111, “HP-SEIKYUYM” is 201104, “HP-TUUBAN” is 00001, “HP-KUBUN” is IY, “HP-SINKUBUN” is 20, “HP-SINCOOD” is 613920056, “HP-SUURYOU” is 00003, etc. Information.

  The work area DB 115 is a database temporarily used in the processing in the insured medical information management system. As shown in FIG. 10, the medical institution number “W−” that encodes the medical institution as an item. Data of “HPNO”, medical treatment date (eg, July 2010 = 42207) “W-SINYM”, receipt type (eg, company-in-house single inpatient = 1111) “W-RESYUBETU” is stored.

  Furthermore, the date of billing (eg, July 2010 = 42207) “W-SEIKYUYUM”, the gender of the patient (eg, male = 1, female = 2) “W-SEX”, the date of birth of the patient (eg, Born on November 15, 1973 = 3481115) "W-BIRTH", patient name in Chinese characters "W-PNAME", insured certificate symbol "W-HIKIGOU", insured certificate number " W-HINO "data is stored.

  As an example of data in the work area DB 115, as shown in FIG. 10, “W-HPNO” is 0123567, “W-SINYM” is 42304, “W-RESYUBETU” is 1111, “W-SEIKYUYM” is 42304, “ "W-SEX" is 1, "W-BIRTH" is 3250110, "W-PNAME" is xx Taro, "W-HIKIGOOU" is OO Tama, and "W-HINO" is 1234567.

<Operation of information management system>
First, an outline of the operation of the information management system will be described.

  In the present embodiment, the following processing is performed based on an online receipt, which is an online medical remuneration statement, invoiced to the insurer by each medical institution.

  (1) The medical date and medical institution number are stored in the insured person DB 107 using the insured person ID / number, name, gender, and date of birth as a name identification key.

  (2) The medical institution information and the common receipt information of the standard receipt computer information are collected into one record in the insured medical information storage DB 109, and record identification information = RE and standard receipt computer information (drug / medical record) record identification information. = IY, SI are stored.

  (3) Insured persons with the same medical care date and different medical institution numbers in the insured person DB 107 are extracted and output as a multiple medical institution consultation confirmation table.

  (4) Based on the insured medical information storage DB 109, the insured medical information storage DB record identification information of the insured multiple medical institution examinee checks whether there is the same medical practice / pharmaceutical code from IY, SI. If there is, the process (5) is performed.

  (5) A medical institution in which the first three digits of the zip code of the insured person in the insured person DB 107 and the first three digits of the zip code in the medical institution DB 108 are the same is extracted, and a recommended medical institution list is created and output.

  Next, the operation of the information management system according to the embodiment of the present invention will be described with reference to FIGS. 11 to 17 are flowcharts showing the operation of the information management system according to the embodiment of the present invention. FIG. 11 shows the overall operation, FIG. 12 shows the operation of the receipt request information editing process, and FIG. 13 shows the medical institution information. 14 shows the operation of the insured person information determination process, FIG. 15 shows the operation of the medical treatment information determination process, FIG. 16 shows the operation of the name identification process, and FIG. 17 shows the operation of the recommended medical institution list creation process. Yes.

  18 to 20 are diagrams showing examples of forms output during the operation of the information management system according to the embodiment of the present invention. FIG. 18 is an insured-no-error list, and FIG. FIG. 20 shows a recommended medical institution list.

  As shown in FIG. 11, the overall operation of the information management system is as follows. First, a receipt request information editing process by the receipt request information editing processing unit 103 (step S201), a name identification process by the name identification processing unit 104 (step S202), and a recommended medical institution. A recommended medical institution list creation process (step S203) by the list creation processing unit 105 is executed.

  The receipt request information editing process in step S201 receives the receipt request information stored in the standard receipt computer information DBs 111 and 114 of the medical institutions 110 and 113, and receives the medical institution information, the insured person (patient) information, the insured person. This is a process of editing medical information such as used chemicals / inspection test information and storing it in the insured person DB 107.

  When editing, check whether there is the same information as the insured DB 107 using the date of birth / gender / name / insured symbol / number of the insured (patient) in the receipt request information as a key. The insured person number in the insurer DB 107 is acquired and stored in the insured person medical information storage DB 109.

  Since the medicine and medical practice information in the receipt request information are variable for each insured person, a sequence number is assigned and stored as one record.

  The name identification process in step S202 is a process of outputting a plurality of medical institution consultation confirmation tables when the medical date and medical institution number are different using the insured person number in the insured person DB 107 as a key.

  Also, the recommended medical institution list creation process in step S203 is performed when the medical institution code is the same and the medical institution number is different using the insured person number and the medical date in the insured medical information storage DB 109 as a key. Processing to output a list.

  Next, the details of the receipt claim information editing process (step S201) shown in FIG. 11 will be described.

  In the receipt billing information editing process (step S201), as shown in FIG. 12, first, the standard receipt computing information is read from the standard receipt computing information DB 106 (step S301), and it is determined whether or not the record is finished (step S302). If the record ends in step S302, the process ends.

  If it is not the end of the record in step S302, it is determined whether the receipt computer identification of the record read in step S301 is IR-KUBUN = IR (step S303), and the receipt computer identification is performed in step S303. When IR-KUBUN = IR, a medical institution information determination process (step S304) which is a process of the service period information determination unit is performed.

  If the receipt computer identification is not IR-KUBUN = IR in step S303, it is determined whether the receipt computer identification of the record read in step S301 is RE-KUBUN = RE or HO-KUBUN = HO ( In step S305), if the receipt computer identification is RE-KUBUN = RE or HO-KUBUN = HO in step S305, the insured person information determination process (step S306), which is the process of the user information determination unit, is executed. .

  Also, if the receipt computer identification is not RE-KUBUN = RE or HO-KUBUN = HO in step S305, whether the receipt computer identification of the record read in step S301 is IY-KUBUN = IY or SI-KUBUN = SI. In step S307, if the receipt computer identification is IY-KUBUN = IY or SI-KUBUN = SI, the medical practice information determination process (step S308) is performed by the service information determination unit. ).

  If the receipt computer identification is not IY-KUBUN = IY or SI-KUBUN = SI in step S307, the process returns to step S301.

  When the processing in the medical institution information determination process (step S304), the insured information determination process (step S306), or the medical practice information determination process (step S308) is completed, the process returns to step S301.

  Next, details of the medical institution information determination process (step S304) shown in FIG. 12 will be described.

  In the medical institution information determination process (step S304), as shown in FIG. 13, first, the medical institution number and the billing date are saved in the work area DB 115 (step S401), and the medical institution DB 108 is stored using the medical institution number as a key. Read (step S402).

  Then, it is determined whether or not there is a record with the corresponding key in the medical institution DB 108 (step S403). If there is a record with the corresponding key in step S403, the medical institution DB 108 is updated (medical institution name, telephone number, zip code). , Overwriting the address name) (step S404).

  If there is no record of the corresponding key in step S403, it is added to the medical institution DB 108 (adding the name of the medical institution, telephone number, postal code, and address name using the medical institution number as a key) (step S405).

  Next, details of the insured person information determination process (step S306) shown in FIG. 12 will be described.

  In the insured person information determination process (step S306), as shown in FIG. 14, first, in the work area DB 115, the medical date, receipt type, billing date, date of birth, gender, name, insured symbol / number Is saved (step S501).

  Then, the repetitive serial number counter for storing insured medical information is initialized to '1' (step S502), and the insured person DB 107 is read using the date of birth, gender, name, insured symbol / number as a key (step S503). ).

  Then, it is determined whether or not there is a record with the corresponding key in the insured person DB 107 (step S504). If there is a record with the corresponding key in step S504, the insured person DB 107 is updated (work to the insured person DB 107). The medical care date and medical institution number in the area DB 115 are added (step S505).

  If there is no record with the corresponding key in step S504, a no-insured error list as shown in FIG. 18 is created and output (step S506).

  It can be confirmed that there is a possibility that the insured person information does not correspond to the insured person error list.

  Next, details of the medical practice information determination process (step S308) shown in FIG. 12 will be described.

  In the medical practice information determination process (step S308), as shown in FIG. 15, first, the insured number, medical date, medical institution number, receipt type, billing of the work area DB 115 saved in step S501 shown in FIG. The medical treatment classification, the medical practice code, and the usage amount of the year and month and the receipt computer identification IY / SI are set in the output area of the insured medical care information storage DB 109 (step S601).

  Then, the data set in the output area of the insured medical information storage DB 109 in step S601 is added to the insured medical information storage DB 109 (step S602), and “1” is added to the repeated number counter for storing insured medical information. Are added (step S603).

  Next, details of the name identification process (step S202) shown in FIG. 11 will be described.

  In the name identification process (step S202), as shown in FIG. 16, first, the insured person number in the insured person DB 107 is read as a key (step S701), and it is determined whether or not the record ends (step S702), and step S702. If the record ends, the process ends.

  If the record does not end in step S702, the repetition date of the medical institution's DB 107 and the medical institution number is saved in the temporary work area DB 115 to determine whether the medical institution number is the same and the medical institution number is different. By performing the search (MAX 100 times), it is determined whether or not the medical year and medical institution number are different (step S703).

  In the case of the same in step S703, since a plurality of medical institutions have not been visited, the process returns to step S701.

  If different in step S703, a multiple medical institution consultation confirmation table output editing process is performed (step S704), and a multiple medical institution consultation confirmation table as shown in FIG. 19 is created and output (step S705).

  With this multi-medical institution consultation confirmation table, the insurer can confirm that the insured has consulted with multiple medical institutions in the same month.

  Next, details of the recommended medical institution list creation process (step S203) shown in FIG. 11 will be described.

  In the recommended medical institution list creation process (step S203), as shown in FIG. 17, first, the insured medical information storage DB 109 is read using the insured person number and the medical date as a key (step S801), and whether or not the record ends. Is determined (step S802), and if the record ends in step S802, the process ends.

  If the record is not finished in step S802, the medical practice code and medical institution number setting processing for setting the medical practice code and the medical institution number in the work area DB 115 is performed (step S803).

  Then, it is determined whether or not the medical practice code is the same (step S804). If the medical practice code is not the same in step S804, the medical practice code temporarily stored in the work area DB 115 is searched and the codes are not the same. In this case, the medical treatment code additionally stored in the work area DB 115 and the medical institution number additional set processing are performed (step S805), and the process returns to step S801.

  If the medical practice code is the same in step S804, it is determined whether the medical institution number is the same (step S806). In step S806, it is determined whether the medical practice code is the same and the medical institution number is the same in step S804. If the medical institution number is not the same, there is the same medical practice in different medical institutions in the same month. Become.

  If the medical institution numbers are the same in step S806, there is no same medical practice in different medical institutions, and the process returns to step S801.

  If the medical institution number is not the same in step S806, a multiple medical institution consultation confirmation table output editing process is performed for setting the insured person information in the insured person medical information storage DB 109 in the output area (step S807).

  Then, the medical institution DB 108 is read using the insured person's address code as a key (step S808), and a medical institution close to the insured person's address is searched.

  Then, as shown in FIG. 20, a list of recommended medical institutions in which the insured number, name, date of birth, medical date, medical institution name, and recommended medical institution name are output (step S809). The process returns to step S801.

  Based on this list of recommended medical institutions, if an insured person visited multiple medical institutions in the same month and performed the same medical practice, a medical institution close to the insured's address is searched and output as a recommended medical institution Therefore, the recommended medical institution is notified to the insured person, and it is possible to prevent duplicate medical treatments such as duplicate medication and examination, and to prevent an increase in medical expenses.

  In the present embodiment, the insured medical information management system has been described as an example of the information management system. However, the present invention is not limited to this, and the user can use a plurality of users in a certain period such as one month. The present invention can also be applied to systems and devices that manage information such as service contents and cost burden when receiving services at locations.

  In that case, the contents of each database are different, but it receives information such as user information, service contents and cost burden sent from multiple service providers used by the user, The name, gender, and date of birth are used as a name identification key, and the service content is checked for duplication. If there is a duplicate service or cost burden for a certain period, a recommended service provider that is close to the user's address will be introduced. Become.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiment. However, the present invention is not limited to the embodiment, and various modifications can be made without departing from the scope of the invention. Needless to say.

  DESCRIPTION OF SYMBOLS 101 ... Server installed on the insurer side, 102 ... Insured medical care information management system, 103 ... Receipt request information editing processing unit, 104 ... Name identification processing unit, 105 ... Recommended medical institution list creation processing unit, 106, 111, 114 ... Standard receipt computer information DB, 107 ... Insured person DB, 108 ... Medical institution DB, 109 ... Insured person medical information storage DB, 110 ... Medical institution A, 113 ... Medical institution B, 112 ... Network, 115 ... Work Area DB.

Claims (3)

Received and received the information on the user, the date of use when the user used the service providing organization, and information on the service transmitted from a plurality of service providing organizations that provide services to the user An information editing processing unit for storing information in a database;
Based on the information stored in the database, it was confirmed whether the user was provided with the service by using the different service providing organizations for a certain period of time, and the different service providing organizations were used. A name identification processing unit that outputs information of a plurality of the service providing organizations used by the user,
Based on the information stored in the database, the user confirms whether the user has been provided with the same service by using the different service provider organizations for a certain period of time. A recommended service providing organization creation processing unit that outputs information of the service providing organization nearest to the user;
An information management system with In the information management system according to claim 1,
The information editing processing unit determines service period information transmitted from a plurality of the service providing organizations, and stores the information in the database.
Determining user information transmitted from a plurality of the service providing organizations, and storing the user information in the database; and
A service information determination unit for determining information on the service used by the user transmitted from a plurality of the service providing organizations, and storing the information in the database;
An information management system. In the information management system according to claim 2,
The service provider is a medical institution;
The provision of the service is provision of a medical practice for the user;
The information related to the service is an information management system, which is information on a medical fee remuneration statement when the user uses the medical institution.

Images