JP2015049759A - Program, information processing method, and information processing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide program and others which can properly perform synchronization of a plurality of databases when a user modifies data of one of the databases.SOLUTION: Between a first database and a second database generated on the basis of data of the first database, when a computer 1 receives modification to the data of the first database, the computer 1 generates an intermediate first database including the modified data. The computer 1 generates an intermediate second database on the basis of data of the intermediate first database, and updates the first database on the basis of the data of the intermediate first database. The computer 1 updates the second database on the basis of data of the intermediate second database.

Description

  The present invention relates to a program for causing a computer to execute various processes, an information processing method, and an information processing apparatus.

  2. Description of the Related Art Conventionally, there has been proposed a medical office processing device that performs a calculation process for medical remuneration points (see, for example, Patent Document 1).

JP 2007-47848 A

  However, the conventional technique has a problem in that when data contents are corrected, appropriate processing cannot be performed.

  In one aspect, an object of the present invention is to provide a program or the like that can appropriately synchronize a plurality of databases when correction is performed.

  When the program disclosed in the present application receives correction of the data of the first database from the first database and the second database generated based on the data of the first database, the program includes intermediate data including the corrected data. A first database is generated, an intermediate second database is generated based on the data of the intermediate first database, the first database is updated based on the data of the intermediate first database, and the data of the intermediate second database Based on the above, a process for updating the second database is executed.

  In one aspect, it is possible to properly synchronize a plurality of databases.

It is explanatory drawing which shows the outline | summary of an information processing system. It is a block diagram which shows the hardware group of a personal computer. It is a block diagram which shows the hardware group of a computer. It is explanatory drawing which shows the image of a medical chart input screen. It is explanatory drawing which shows the record layout of 1st chart DB. It is explanatory drawing which shows the record layout of 2nd chart DB. It is explanatory drawing which shows the image of a disease name input screen. It is explanatory drawing which shows the record layout of disease name DB. It is an accounting display screen. It is explanatory drawing which shows the record layout of accounting data DB. It is explanatory drawing which shows the record layout of receipt DB. It is explanatory drawing which shows the record layout of inspection DB. It is explanatory drawing which shows the record layout of edit error DB. It is explanatory drawing which shows the image of a receipt display screen. It is explanatory drawing which shows the record layout of intermediate disease name DB. It is explanatory drawing which shows the record layout of intermediate | middle receipt DB. It is explanatory drawing which shows the record layout of intermediate | middle edit error DB. It is a flowchart which shows the production | generation process procedure of each DB. It is a flowchart which shows the production | generation process procedure of each DB. It is a flowchart which shows the procedure of the production | generation process of DB. It is a flowchart which shows the procedure of the production | generation process of DB. It is a flowchart which shows the procedure of the production | generation process of DB. 12 is an explanatory diagram showing an image of a receipt display screen according to Embodiment 3. FIG. It is a flowchart which shows the procedure of a grayout process. It is a functional block diagram which shows operation | movement of the computer of the form mentioned above. FIG. 10 is a block diagram illustrating a hardware group of a computer according to a fourth embodiment.

Embodiment 1
Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is an explanatory diagram showing an outline of an information processing system. The information processing system includes an information processing apparatus 1, a personal computer 2, and the like. The information processing apparatus 1 and the personal computer 2 are connected via a communication network N such as the Internet. The information processing apparatus 1 is, for example, a server computer or a personal computer. Hereinafter, the information processing apparatus 1 will be described as being replaced with the computer 1. The personal computer 2 is a device used in a facility such as a hospital, a company, a university, or a store.

  In the present embodiment, an example of handling information input accompanying a medical practice in a hospital will be described. However, the present invention is not limited to this. For example, business accounting data or personnel data may be handled. In addition to using the personal computer 2, a mobile phone, a PDA (Personal Digital Assistant), or the like may be used. In this embodiment, an example is shown in which various data are input by the personal computer 2 and various software processes are performed by the computer 1. However, the present invention is not limited to this. The personal computer 2 may perform all processing at once. Details will be described below.

  FIG. 2 is a block diagram showing a hardware group of the personal computer 2. The personal computer 2 includes a central processing unit (CPU) 21 as a control unit, a random access memory (RAM) 22, an input unit 23, a display unit 24, a storage unit 25, a clock unit 28, a communication unit 26, and the like. The CPU 21 is connected to each part of the hardware via the bus 27. CPU21 controls each part of hardware according to control program 25P memorized by storage part 25. The RAM 22 is, for example, SRAM (Static RAM), DRAM (Dynamic RAM), flash memory, or the like. The RAM 22 also functions as a storage unit, and temporarily stores various data generated when the CPU 21 executes various programs.

  The input unit 23 is an input device such as a mouse or keyboard, a mouse or a touch panel, and outputs received operation information to the CPU 21. The display unit 24 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the CPU 21. The communication unit 26 is a communication module, and transmits and receives information to and from the computer 1 via the communication network N.

  The storage unit 25 is a hard disk or a large-capacity memory, and stores the control program 25P described above. The clock unit 28 outputs date / time information to the CPU 21.

  FIG. 3 is a block diagram showing a hardware group of the computer 1. The computer 1 includes a CPU 11 as a control unit, a RAM 12, an input unit 13, a display unit 14, a clock unit 18, a storage unit 15, a communication unit 16, and the like. The CPU 11 is connected to each part of the hardware via the bus 17. The CPU 11 controls each part of the hardware according to the control program 15P stored in the storage unit 15. The RAM 12 is, for example, SRAM, DRAM, flash memory or the like. The RAM 12 also functions as a storage unit, and temporarily stores various data generated when the CPU 11 executes various programs.

  The input unit 13 is an input device such as a mouse or a keyboard, a mouse or a touch panel, and outputs received operation information to the CPU 11. The display unit 14 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the CPU 11. The communication unit 16 is a communication module, and transmits and receives information to and from the personal computer 2 via the communication network N.

  The storage unit 15 is a hard disk or a large-capacity memory, and includes a first medical record database (hereinafter referred to as DB) 151, a second medical record DB 152, a disease name DB 153, an accounting data DB 154, a receipt DB 155, and the like in addition to the control program 15P described above. In addition, the storage unit 15 stores an editing error DB 156, an inspection DB 157, an intermediate first medical record DB 251, an intermediate second medical record DB 252, an intermediate disease name DB 253, an intermediate accounting data DB 254, an intermediate receipt DB 255, an intermediate editing error DB 256, and the like. Yes. In the present embodiment, an example in which various DBs are stored in the storage unit 15 of the computer 1 is described, but the present invention is not limited to this. For example, the various DBs described above may be appropriately stored in a database server (not shown) connected via the communication network N. In this case, the CPU 11 accesses the database server as necessary, and writes and reads data.

  FIG. 4 is an explanatory diagram showing an image of a chart input screen. A chart input screen is displayed on the display unit 24 of the personal computer 2. A user who is a medical person including a doctor, a nurse, or a hospital staff inputs information on the medical chart from the input unit 23. In the example of FIG. 4, the patient A's August 6 chart is displayed on the left and the September 13 chart is displayed on the right. The user inputs subjective findings and objective findings from the input unit 23. In the example of FIG. 4, “with appetite, fever on September 10th, with some vomiting” is entered in the “S” column indicating the subjective findings as subjective findings. As an objective finding, “O” indicating an objective finding is entered as “attenuation of respiratory sound in the right middle lung field region, appearance of ra sound in deep breathing on chest auscultation”.

  Subsequently, the user inputs treatment and prescription from the input unit 23. In the example of FIG. 4, “internal use, 2 tablets of A tablet 200 mg, 5 days after dinner” is input. The CPU 21 transmits the chart data input from the input unit 23 to the computer 1 via the communication unit 26. The CPU 11 of the computer 1 receives medical chart data via the communication unit 16. The CPU 11 stores the chart data in the first chart DB 151 and the second chart DB 152.

  FIG. 5 is an explanatory diagram showing a record layout of the first medical record DB 151. The first medical record DB 151 includes a patient number field, a consultation date field, a medical record number field, a finding classification field, a finding number field, a data field, a doctor name field, an update date / time field, and the like. A unique patient number for identifying a patient is stored in the patient number field. The date of visit by the patient is stored in the visit date field. The chart number field stores a unique chart number for identifying a chart. In the finding classification field, either S indicating a subjective finding or O indicating an objective finding is stored. In the example of FIG. 5, two subjective findings and two objective findings are stored.

  In the observation number field, a number for identifying a subjective finding or an objective finding is stored. Findings are stored in the data field. For example, “appetite, fever on September 10” is stored with the finding classification “S” and the finding number “1”. The doctor name is stored in the doctor name field. The doctor name is input together with the medical record data input from the input unit 23 of the personal computer 2. The entered doctor name is transmitted to the computer 1 together with the chart data. The date and time when the chart was updated is stored in the update date and time field. This date and time is the date and time output by the clock unit 28 of the personal computer 2 and is transmitted to the computer 1 together with the chart data. The date and time when the chart data transmitted from the personal computer 2 is received by the computer 1 may be used as the update date and time. In this case, the CPU 11 stores the date and time output from the clock unit 18 in the first medical record DB 151. In the example of FIG. 5, the update date of the data of the chart number “0001” is September 13, 2010, 20: 6: 59.

  FIG. 6 is an explanatory diagram showing a record layout of the second medical record DB 152. The second medical record DB 152 includes a patient number field, a visit date field, an order number field, a medical record number field, a drug number field, a drug detail number field, a code field, a display name field, a quantity field, and a frequency field. The order number field stores a unique order number for creating prescription order and accounting data. The agent number field stores the agent number for specifying the agent to be prescribed, and the agent specification number field stores the agent specification number for specifying a more detailed agent in association with the agent number. .

  In the code field, a code for specifying medicine and how to drink is stored. In the display name field, information such as medicine and how to drink is stored. In the quantity field, the quantity for prescribing the medicine is stored, and in the number field, the number of prescriptions is stored. In the example of FIG. 6, “A tablet 200 mg” is associated with the drug number “001”, the drug specification number “001”, and the code “15375”, the quantity is stored as “2”, and the number of times is stored as “5”. ing. When receiving the chart data, the CPU 11 stores the data in the second chart DB 152 based on the inputted medicine name, number of times, quantity, and the like. In the present embodiment, the first medical record DB 151 and the second medical record DB 152 have been described separately for ease of explanation, but these may be combined into one.

  FIG. 7 is an explanatory diagram showing an image of a disease name input screen. The user inputs a disease name, a start date, and an end date from the input unit 23. The start date is the day when the illness starts and the end date is the day when the illness is cured. In the example of FIG. 7, disease names “acute tracheitis” and “suspected bronchopneumonia” are stored. The start date is entered as August 5, 2010, and the end date is entered as August 31, 2010. When the disease name data is input from the input unit 23, the CPU 21 transmits the disease name data to the computer 1 via the communication unit 26. The CPU 11 of the computer 1 stores the received disease name data in the disease name DB 153.

  FIG. 8 is an explanatory diagram showing a record layout of the disease name DB 153. The disease name DB 153 includes a patient number field, a disease name serial number field, a disease name code field, a disease name field, a start date field, an end date field, an outcome field, and the like. In the disease name sequence number field, a unique disease name sequence number for sequentially specifying the disease name in association with the patient number is stored. The disease name code field stores a unique disease name code associated with the disease name. The disease name is stored in the disease name field. In the start date field, the day when the illness is developed is stored, and in the end date field, the day when the illness is cured is stored. The medical condition is stored in the outcome field. Specifically, “healing” is stored when completely cured, and “under treatment” is stored when being treated.

  FIG. 9 is an accounting display screen, and FIG. 10 is an explanatory diagram showing a record layout of the accounting data DB 154. The CPU 11 generates accounting data based on the stored contents of the first medical record DB 151 and the second medical record DB 152. The accounting data DB 154 includes a patient number field, an accounting date field, a drug information field, a drug detail field, a score field, a frequency field, an order number field, an update date field, and the like. The accounting date field stores a date when generating accounting data. In the agent information field, agent information for specifying each billing content of the accounting data is stored.

  A number for specifically specifying the prescription and treatment on which the claim is based is stored in the drug specification field. For example, for the drug information “001”, a code “15375.02” indicating two A tablets 200 mg is stored in the column of the drug specification 001. Further, “912” indicating how to drink “after morning dinner” is stored in the column of the drug description 002. Regarding the drug information “002”, the code “28250.03” indicating 15 mg of B tablet in the drug specification 001 and 3 tablets in the drug specification “001” is stored in the drug specification “001”, and the code “15 mg indicating C tablet in the drug specification 002” 34324.03 "is stored.

  The CPU 11 stores agent information “003” to “007” in the accounting data DB 154 according to a known accounting data generation program. The drug information “003” stores a code “012” for specifying “internal / uncontrolled dispensing fee (outpatient)”, and the drug information “004” stores a code “001” for specifying “dispensing technology basic fee”. Is remembered. In the drug information “005”, a code “005” specifying “outpatient prescription fee (6 types or less)” is stored. The agent information “006” stores a code “034” for specifying “revisit fee”, and the agent information “007” stores a code “041” for specifying “external management addition”. . The CPU 11 generates data for the drug information “003” to “007” based on the number of medicines to be prescribed, the contents of the medical examination, the internal medicine or surgery, the date of the previous medical examination, and the like, and stores the generated data in the accounting data DB 154. To do.

  In the score field, the score given based on the prescription and the treatment content is stored. For example, in the case of “A tablet 200 mg 2 tablets” and “After breakfast and dinner”, 18 points are stored in the accounting data DB 154. In addition, “revisit fee” is stored as 69 points. In the number field, the number of prescriptions or the number of treatments is stored. “A tablet 200 mg 2 tablets” and “after breakfast and dinner” are stored as 5 times, and “review fee” is stored as 1 time.

  FIG. 11 is an explanatory diagram showing a record layout of the receipt DB 155. The CPU 11 generates a receipt DB 155 based on the above-described first medical record DB 151, second medical record DB 152, disease name DB 153, and accounting data DB 154. Receipt data is data that is required every month to charge for expenses based on medical practice. The receipt DB 155 includes a billing date field, a consultation date, a patient number field, a medical department field, a record identification field, a record number field, a data field, a creation date field, an update date field, and the like. In the billing date field, the date for billing for the receipt is stored. The date of medical care is stored in the medical care date field. The example of FIG. 11 shows an example in which a claim based on a medical practice in September 2010 is requested in October 2010.

  A unique number for identifying a department is stored in the department field. In the example of FIG. 11, “01” indicating the internal medicine is stored. Identification information for identifying data stored in the data field is stored in the record type field. For example, “RE” indicates that the information is essential when recording at the beginning of the receipt unit data, and “HO” indicates that the information is recorded in the case of a medical insurance receipt. “SI” is medical practice record information, and “IY” is pharmaceutical information. In addition to the record identification described above, there are “SY”, “TO”, and the like. “SY” is information on the name of the injury and illness, and “TO” is information on the specific equipment.

  In the record number field, a number for specifying each data of the receipt DB 155 is stored. Each data item of the receipt is stored in the data field. For example, the record number “1” stores basic information for each patient, such as the patient name. Record number “2” stores data relating to insurance. In the record number “3”, data relating to a medical practice such as a reexamination fee is stored. In addition, in the record number “6”, data related to the prescribed medicine such as A tablet is stored. The date of creation of the receipt is stored in the creation date field. The date of update of the receipt DB 155 is stored in the update date field. The CPU 11 generates a receipt DB 155 based on the storage contents of the first medical record DB 151, the second medical record DB 152, the disease name DB 153, and the accounting data DB 154.

  FIG. 12 is an explanatory diagram showing a record layout of the inspection DB 157. The inspection DB 157 includes an item number field, an error code field, an error content field, an error cause field, and the like. In the error code field, a unique error code for specifying an error in receipt is stored in association with the item number in the item number field. In the error content field, error content is stored in association with the error code. The cause of the error is stored in the error cause field. After generating a receipt based on the receipt DB 155, the CPU 11 determines whether there is an error in the receipt based on the inspection DB 157.

  If the CPU 11 determines that an error exists, the CPU 11 outputs the error content. For example, in the present embodiment, as shown in FIG. 8, there is an error that there is no September 2010 disease name despite the September 2010 receipt request. CPU11 reads an error code and the error content, when the record of a sickness name does not exist in a receipt. The CPU 11 stores the error content in the editing error DB 156. FIG. 13 is an explanatory diagram showing a record layout of the editing error DB 156. As shown in FIG. The edit error DB 156 includes a billing date field, a medical treatment date field, a patient number field, an error code field, an error content field, an update date field, and the like.

  The CPU 11 stores the error code and error content in the editing error DB 156 as shown in FIG. The CPU 11 also refers to the date and time output from the clock unit 18 and stores the update date in the update date field. In addition, the CPU 11 refers to the inspection DB 157 and determines that an error has occurred when an external character is included in the patient name of the receipt. The CPU 11 also refers to the check DB 157 and determines that an error has occurred even when a medical practice dedicated to hospitalization is stored in the medical practice, even though the medical treatment is other than hospitalization. The CPU 11 outputs the read error code and error content to the personal computer 2.

  FIG. 14 is an explanatory diagram showing an image of a receipt display screen. On the receipt display screen, a screen simulating an actual receipt is displayed on the right half. The disease name is displayed on the upper left, the medical record is displayed on the lower left, and the accounting data is displayed near the center. The CPU 21 of the personal computer 2 displays the received error content near the center. In the example of FIG. 14, “Injury name record is not recorded” is displayed. The user again moves to the disease name input screen shown in FIG. 7, and inputs the disease name, start date, and end date.

  FIG. 15 is an explanatory diagram showing a record layout of the intermediate disease name DB 253. The user inputs a disease name and a start date from the input unit 23. If the patient has not healed, the end date may not be input. In the example of FIG. 15, the start date “September 13, 2010” and the disease name “acute bronchitis” are input. The CPU 21 transmits the start date and the disease name, which are the input corrected disease name data, to the computer 1. When the CPU 11 of the computer 1 receives the corrected disease name data after generating the receipt, the CPU 11 generates the intermediate disease name DB 253. Specifically, the CPU 11 expands the storage contents of the disease name DB 153 into the intermediate disease name DB 253. Further, the CPU 11 stores the received corrected disease name data in the intermediate disease name DB 253.

  The record layout of the intermediate disease name DB 253 is substantially the same as the disease name DB 153. The third stage data, which is corrected disease name data, is added. The CPU 11 refers to the patient number and stores a new number in the disease name serial number field. The CPU 11 stores the internal disease name of the corrected disease name data in the disease name field. The CPU 11 stores the start date of the corrected disease name data in the start date field. When the end date exists in the corrected disease name data, the CPU 11 stores the end date in the end date field. When the end date exists in the corrected disease name data, the CPU 11 stores “cure” in the outcome field. When the end date does not exist in the corrected disease name data, the CPU 11 leaves it blank, or stores the information “under treatment” in the outcome field. Moreover, although a new record is added in this embodiment, the form which corrects the original record may be sufficient. For example, the end date related to the first and second records in FIG. 15 may be corrected to “20100917” indicating September 17, 2010, and the intermediate disease name DB 253 may be generated.

  When the CPU 11 generates the intermediate disease name DB 253 and receives an output request for other patient data from the personal computer 2, the CPU 11 performs generation processing of the intermediate receipt DB 255 and the intermediate editing error DB 256. The CPU 11 first reads the receipt DB 155 and develops it in the intermediate receipt DB 255. Next, the CPU 11 updates the content of the intermediate receipt DB 255 based on the corrected record of the intermediate disease name DB 253. FIG. 16 is an explanatory diagram showing a record layout of the intermediate receipt DB 255. In the example of FIG. 16, the third row record is added. The billing date is October 2010, the examination date is September 2010, the patient number is 0001, the department is 01, and the record identification is SY. Record number 3 is newly assigned, and a numerical value indicating acute bronchitis is stored as data. Although the creation date remains unchanged, the CPU 11 stores the date output from the clock unit 18 in the update date field.

  Thereafter, the CPU 11 generates an intermediate editing error DB 256. FIG. 17 is an explanatory diagram showing a record layout of the intermediate editing error DB 256. The CPU 11 refers to the stored content of the editing error DB 156 and deletes the record of the resolved error. In the example of FIG. 17, the record of the error “Injury name record is not recorded.” Indicated by error code L2554 is deleted. When the CPU 11 receives information indicating the end of the receipt check job from the personal computer 2, the CPU 11 performs DB update processing.

  The CPU 11 reads the intermediate disease name DB 253, overwrites the read data on the disease name DB 153, and performs update processing. Similarly, the CPU 11 reads the intermediate reception DB 255, overwrites the read data on the reception DB 155, and performs update processing. The CPU 11 reads the intermediate editing error DB 256, overwrites the read data on the editing error DB 156, and performs update processing.

  Various software processes in the hardware group described above will be described with reference to flowcharts. 18 and 19 are flowcharts showing the procedure for generating each DB. After detecting the error, the CPU 11 performs the following processing. The CPU 11 stores the error code and error content in the editing error DB 156 (step S181). The CPU 11 transmits an error code and error content to the personal computer 2 (step S182). The CPU 21 of the personal computer 2 displays the error content on the receipt display screen based on the error code and error content received on the display unit 24 (step S183).

  CPU21 receives correction disease name data from the input part 23 (step S184). Specifically, information regarding the disease name and start date, and if necessary, the end date and outcome is received from the input unit 23. The CPU 21 transmits the received corrected disease name data and patient number to the computer 1 (step S185). The CPU 11 of the computer 1 receives the corrected disease name data and the patient number (step S186). CPU11 reads the memory content of disease name DB153, and copies it to intermediate disease name DB253 (step S187).

  The CPU 11 stores the received corrected disease name data in the intermediate disease name DB 253 (step S188). Specifically, the CPU 11 generates a new disease name serial number, and inputs the received patient number, disease name, start date, end date, outcome, and the like into the generated new record. The CPU 11 reads the disease name code corresponding to the disease name from the storage unit 15 and stores it in the disease name code field. Thereafter, it is assumed that the user makes a display request for another patient in order to edit another patient from the input unit 23. CPU21 outputs the display request of another patient to the computer 1, when the display request of another patient is received from the input part 23 (step S189). The CPU 11 of the computer 1 receives another patient display request (step S191).

  The CPU 11 reads the content stored in the receipt DB 155 and copies it to the intermediate receipt DB 255 (step S192). CPU11 memorize | stores the information regarding correction disease name data in intermediate | middle receipt DB255 (step S193). Specifically, the CPU 11 refers to the storage unit 15 and stores information on the department, the billing date, and the examination date corresponding to the received patient number. In addition, the disease name data and the disease name identification record “SY” are stored in the intermediate receipt DB 255. The CPU 11 refers to the date and time output from the clock unit 18 and corrects the update date to a new date and time.

  The CPU 11 reads the stored contents of the editing error DB 156 and copies it to the intermediate editing error DB 256 (step S194). The CPU 11 deletes information regarding the corrected disease name data that has been corrected from the intermediate editing error DB 256 (step S195). The CPU 21 of the personal computer 2 receives a receipt check job end request from the input unit 23. The CPU 21 transmits to the computer 1 an end request for the receipt check service received from the input unit 23 (step S196). The CPU 11 of the computer 1 receives the receipt check job end request (step S197).

  The CPU 11 reads the stored contents of the intermediate disease name DB 253, triggered by the reception of the termination request, and overwrites the stored contents in the disease name DB 153 (step S198). The CPU 11 reads the storage content of the intermediate reception DB 255 and stores the storage content in the reception DB 155 (step S199). The CPU 11 reads the storage content of the intermediate editing error DB 256 and overwrites the editing content DB 156 with the stored content (step S1910). Thereby, even when the disease name DB 153 is corrected, it is possible to generate final receipt data while synchronizing with other affected DBs.

Embodiment 2
The second embodiment relates to a mode in which the first medical record DB 151 or the second medical record DB 152 is corrected. In the present embodiment, an example will be described in which there is an error in the content input to the second medical record DB 152, and the user inputs corrected data (hereinafter referred to as corrected medical record data) from the input unit 23. 20 to 22 are flowcharts showing the procedure of DB generation processing. After detecting the error, the CPU 11 performs the following processing. The CPU 11 stores the error code and error content in the editing error DB 156 (step S201). The CPU 11 transmits an error code and error content to the personal computer 2 (step S202). The CPU 21 of the personal computer 2 displays the error content on the receipt display screen based on the error code and the error content received on the display unit 24 (step S203).

  CPU21 receives correction medical chart data from the input part 23 (step S204). The CPU 21 transmits the received corrected medical record data and patient number to the computer 1 (step S205). The CPU 11 of the computer 1 receives the corrected medical record data and the patient number (step S206). The CPU 11 reads the stored contents of the second medical record DB 152 and copies it to the intermediate second medical record DB 252 (step S207).

  The CPU 11 stores the received corrected chart data in the intermediate second chart DB 252 (step S208). When the medical record information is changed, the DB related to accounting is also affected, and the following processing is performed. The CPU 11 reads the stored contents of the accounting data DB 154. The CPU 11 copies the stored contents of the read accounting data DB 154 to the intermediate accounting data DB 254 (step S209). CPU11 produces | generates the correction accounting data corrected by correction medical chart data (step S211). The CPU 11 stores the generated corrected accounting data in the intermediate accounting data DB 254 (step S212). For example, when information related to prescription of a new drug is added, information such as a drug description, score, number of times, update date and time is added.

  Thereafter, it is assumed that the user makes a display request for another patient in order to edit another patient from the input unit 23. CPU21 outputs the display request of another patient to the computer 1, when the display request of another patient is received from the input part 23 (step S213). The CPU 11 of the computer 1 receives another patient display request (step S214).

  The CPU 11 reads the stored content of the receipt DB 155 and copies it to the intermediate receipt DB 255 (step S215). CPU11 memorize | stores the information relevant to correction medical chart data and correction accounting data in intermediate | middle receipt DB255 (step S216). Specifically, when a prescription drug is added, the CPU 11 associates information such as the record identification “IY”, the diagnosis department, the data of the drug to be added, the update date, etc. with the billing date, the medical date, and the patient number. And stored in the intermediate receipt DB 255.

  The CPU 11 reads the stored contents of the edit error DB 156 and copies it to the intermediate edit error DB 256 (step S217). The CPU 11 deletes information related to the corrected medical chart data that has been corrected from the intermediate editing error DB 256 (step S218). The CPU 21 of the personal computer 2 receives a receipt check job end request from the input unit 23. The CPU 21 transmits to the computer 1 an end request for the receipt check service received from the input unit 23 (step S219). The CPU 11 of the computer 1 receives a receipt check job end request (step S221).

  The CPU 11 reads the stored content of the intermediate second medical record DB 252 with the reception of the end request as a trigger, and overwrites the stored content in the second medical record DB 152 (step S222). The CPU 11 reads the stored contents of the intermediate accounting data DB 254 and overwrites the accounting data DB 154 (step S223). The CPU 11 reads the stored contents of the intermediate receipt DB 255 and overwrites the received contents on the receipt DB 155 (step S224). The CPU 11 reads the stored content of the intermediate editing error DB 256 and overwrites the stored content on the editing error DB 156 (step S225). As a result, even when the second medical record DB 152 is modified, final receipt data can be generated while synchronizing with other affected DBs.

  The second embodiment is as described above, and the other parts are the same as those of the first embodiment. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 3
The third embodiment relates to a mode for changing the display mode of data other than the month to be received on the reception display screen. FIG. 23 is an explanatory diagram showing an image of a receipt display screen according to the third embodiment. The CPU 11 refers to the receipt DB 155, the accounting data DB 154, the first medical record DB 151, and the second medical record DB 152 in the above-described embodiment, and reads the medical record data, the accounting data, and the receipt data of the month to be received and the months that follow it. . The CPU 11 attaches display information so that the display form of the data belonging to the month and the data belonging to the succeeding month among the read medical record data, accounting data, and receipt data is different and outputs it to the personal computer 2. .

  In the example of FIG. 23, August 2010 is selected as the reception target month. The CPU 21 of the personal computer 2 refers to the display information and displays the medical record data, accounting data, and receipt data for July 2010 in a form different from the medical record data, accounting data, and receipt data for August 2010. In this embodiment, a grayout process is performed in which black with high transmittance is superimposed on data for July. Hereinafter, an example in which grayout processing is performed will be described, but the present invention is not limited to this.

  For example, image processing such as enclosing the chart data, accounting data, and receipt data for the month (August) with a red frame so as to stand out conversely may be performed. In addition, the fonts of the monthly chart data and accounting data may be reduced. In the present embodiment, an example in which the computer 1 adds grayout process information will be described. However, the present invention is not limited to this. The CPU 21 on the personal computer 2 side may refer to the selected month and perform grayout processing on data other than the selected month. In the present embodiment, description of disease name data for each month is omitted, but disease name data for months that are not selected may be grayed out. In the example shown in FIG. 23, the previous month data is grayed out. However, the next month data may be grayed out.

  FIG. 24 is a flowchart showing the procedure of grayout processing. On the receipt display screen, the user inputs the month desired to be displayed via the input unit 23. The CPU 21 transmits the month information input from the input unit 23 to the computer 1. The CPU 11 of the computer 1 accepts selection of a month to be displayed via the communication unit 16 (step S241). The CPU 11 refers to the reception DB 155, the first medical record DB 151, the second medical record DB 152, and the disease name DB 153, and reads the receipt data, disease name data, and accounting data for the month and the previous month to be displayed (step S242). The CPU 11 adds a command to perform grayout processing to the previous month's data (step S243).

  The CPU 11 transmits the receipt data, disease name data, and accounting data of the month and the previous month to be displayed to the personal computer 2 (step S244). Similarly, the CPU 11 transmits a grayout processing command (step S245). The CPU 21 of the personal computer 2 receives the month and previous month receipt data, disease name data and accounting data to be displayed (step S246). The CPU 21 receives the grayout processing command (step S247). The CPU 21 displays the month receipt data, disease name data, and accounting data to be displayed on the display unit 24 (step S248). The CPU 21 grays out the previous month's receipt data, disease name data, and accounting data and displays them on the display unit 24 (step S249). Thereby, the user can easily visually recognize the information of the month to be received.

  The third embodiment is as described above, and the others are the same as in the first and second embodiments. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 4
FIG. 25 is a functional block diagram showing the operation of the computer 1 of the above-described form. When the CPU 11 executes the control program 15P, the computer 1 operates as follows. When the intermediate first database generation unit 31 receives a correction to the data of the first database among the first database and the second database generated based on the data of the first database, the intermediate first database including the corrected data 1 database is generated. The intermediate second database generation unit 32 generates an intermediate second database based on the data of the intermediate first database. The first database update unit 33 updates the first database based on the data of the intermediate first database. The second database update unit 34 updates the second database based on the data of the intermediate second database.

  FIG. 26 is a block diagram illustrating a hardware group of the computer 1 according to the fourth embodiment. A program for operating the computer 1 reads a portable recording medium 1A such as a CD-ROM, a DVD (Digital Versatile Disc) disk, a memory card, or a USB (Universal Serial Bus) memory into a reading unit 10A such as a disk drive. It may be stored in the storage unit 15. Further, a semiconductor memory 1B such as a flash memory storing the program may be mounted in the computer 1. Further, the program can be downloaded from another server computer (not shown) connected via a communication network N such as the Internet. The contents will be described below.

  The computer 1 shown in FIG. 26 reads a program for executing the above-described various software processes from the portable recording medium 1A or the semiconductor memory 1B or downloads it from another server computer (not shown) via the communication network N. To do. The program is installed as the control program 15P, loaded into the RAM 12, and executed. Thereby, it functions as the computer 1 described above.

The fourth embodiment is as described above, and the others are the same as those of the first embodiment. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.
The above first to fourth embodiments are applicable to a business system of a medical institution, for example. “Receipt data”, “Accounting data”, “Disease name data”, and “Electronic medical record data” can be registered and updated by different business programs and users who are engaged in different business at medical institutions. is there. An error may be detected not for a business program used by a user who corrects an error in business but for data registered or updated by another business program. For example, if it is determined that there is an error in the electronic medical record data as a result of the error check of the receipt, the user of the reception work starts the business program that processes the electronic medical record and corrects the data that is determined to have an error. To do.
Since the registration and update of data are exclusively processed, the medical record data cannot be registered or updated by the user of the reception service at the same time that the doctor registers or updates the data. Therefore, by providing an intermediate DB as described in the first to fourth embodiments above, it is possible for the user of the reception service to register and update. In contrast to electronic medical record data, doctors mainly target the information for the current month, whereas receipts target information from the previous month. Different.

  With respect to the embodiments including the above first to fourth embodiments, the following additional notes are disclosed.

(Appendix 1)
On the computer,
Among the first database and the second database generated based on the data of the first database, when the correction to the data of the first database is accepted, an intermediate first database including the corrected data is generated,
Generating an intermediate second database based on the data of the intermediate first database;
Updating the first database based on the data of the intermediate first database;
A program for executing a process of updating the second database based on the data of the intermediate second database.

(Appendix 2)
The first database is a medical record database in a medical institution, a disease name database, and an accounting database generated based on the data in the medical record database,
The program according to claim 1, wherein the second database is a receipt database generated based on each data of a medical record database, a disease name database, and an accounting database.

(Appendix 3)
Accept correction data for disease name database data,
Based on the received correction data and the disease name database, an intermediate disease name database is generated,
Create an intermediate receipt database based on the intermediate disease name database,
The program according to claim 2, wherein the disease name database and the receipt database are updated based on the intermediate disease name database and the intermediate receipt database.

(Appendix 4)
Receive correction data for the data in the medical record database,
Based on the received correction data and the medical record database, an intermediate medical record database is generated,
An intermediate accounting database is generated based on the intermediate medical record database,
An intermediate receipt database is generated based on the intermediate medical record database and the intermediate accounting database,
The program according to claim 2 or 3, wherein the medical record database, the accounting database, and the receipt database are updated based on the intermediate medical record database, the intermediate accounting database, and the intermediate receipt database.

(Appendix 5)
The medical record database, accounting database and receipt database store data in association with the month,
Read out the received month and the data including the month before and after the month from the medical record database, accounting database and receipt database,
5. The read data is output so that the data read for the preceding and succeeding months is displayed in a different display form from the data read for the accepted month. Program.

(Appendix 6)
In an information processing method using an information processing device,
Among the first database and the second database generated based on the data of the first database, when the correction to the data of the first database is accepted, an intermediate first database including the corrected data is generated,
Generating an intermediate second database based on the data of the intermediate first database;
Updating the first database based on the data of the intermediate first database;
An information processing method for updating the second database based on data in the intermediate second database.

(Appendix 7)
Of the first database and the second database generated based on the data of the first database, the intermediate first database that generates the intermediate first database including the corrected data when the correction of the data of the first database is accepted. An intermediate second database generation unit that generates an intermediate second database based on the data of the generation unit and the intermediate first database;
A first database updating unit for updating the first database based on the data of the intermediate first database;
An information processing apparatus comprising: a second database update unit configured to update the second database based on data of the intermediate second database.

DESCRIPTION OF SYMBOLS 1 Computer 1A Portable recording medium 1B Semiconductor memory 2 Personal computer 10A Reading part 11 CPU
12 RAM
13 Input unit 14 Display unit 15 Storage unit 15P Control program 16 Communication unit 18 Clock unit 21 CPU
22 RAM
23 Input unit 24 Display unit 25 Storage unit 25P Control program 26 Communication unit 28 Clock unit 31 Intermediate first database generation unit 32 Intermediate second database generation unit 33 First database update unit 34 Second database update unit 151 First medical record DB
152 Second Medical Record DB
153 Disease name DB
154 Accounting Data DB
155 Receipt DB
156 Edit error DB
157 Inspection DB
251 Intermediate First Chart DB
252 Intermediate Second Chart DB
253 Intermediate disease name DB
254 Interim accounting data DB
255 Intermediate Receipt DB
256 Intermediate editing error DB
N communication network

Claims (5)

On the computer,
Among the first database and the second database generated based on the data of the first database, when the correction to the data of the first database is accepted, an intermediate first database including the corrected data is generated,
Generating an intermediate second database based on the data of the intermediate first database;
Updating the first database based on the data of the intermediate first database;
A program for executing a process of updating the second database based on the data of the intermediate second database. The first database is a medical record database in a medical institution, a disease name database, and an accounting database generated based on the data in the medical record database,
The program according to claim 1, wherein the second database is a receipt database generated based on each data of a medical record database, a disease name database, and an accounting database. Accept correction data for disease name database data,
Based on the received correction data and the disease name database, an intermediate disease name database is generated,
Create an intermediate receipt database based on the intermediate disease name database,
The program according to claim 2, wherein the disease name database and the receipt database are updated based on the intermediate disease name database and the intermediate receipt database. In an information processing method using an information processing device,
Among the first database and the second database generated based on the data of the first database, when the correction to the data of the first database is accepted, an intermediate first database including the corrected data is generated,
Generating an intermediate second database based on the data of the intermediate first database;
Updating the first database based on the data of the intermediate first database;
An information processing method for updating the second database based on data in the intermediate second database. Of the first database and the second database generated based on the data of the first database, the intermediate first database that generates the intermediate first database including the corrected data when the correction of the data of the first database is accepted. An intermediate second database generation unit that generates an intermediate second database based on the data of the generation unit and the intermediate first database;
A first database updating unit for updating the first database based on the data of the intermediate first database;
An information processing apparatus comprising: a second database update unit configured to update the second database based on data of the intermediate second database.

Images