JPH1115885A - Count table master managing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To unnecessitate man-hour and structure accompanying the management of user information by judging the possibility of update through the use of data before update so as to make update data of the kinds of the number of users the same update data of all the users. SOLUTION: Update data is provided with 'data before update at a mother master 102' and 'data after update at the mother master 102'. As the result, whether a record is intentionally changed by a user is judged by comparing 'data before update at the mother master 102' and 'data on the side of a user master 122' with each other. If both data are the same value as the result of comparing, the record is not intentionally changed by the customer, the data is updated to 'data after update at the mother master 102'. On the other hand, if both data are mutually different values, as the record is intentionally changed by the customer, whether to leave 'data on the side of a user master 122' or to update to 'data after update at the mother master 102' is judged by the customer.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION A medical office system is a system whose main business is to issue a bill to a patient who has undergone medical treatment and to issue a medical fee statement (recept) to each insurance organization every month. At this time, information such as the score of the medical practice and the drug price of the medicine used in the system is stored in the user master. The user master means that the provider of the medical office system provides each customer with a mother master, which is a model of information such as points and drug prices, and specifies specific items in a specific record for the mother master or a copy of the mother master. A master that has been changed according to the user's intention.

[0002] Mother masters / user masters are subject to large-scale additions / modifications due to annual medical expenses revisions and the like. In addition to such large-scale additions / modifications, additions / modifications are often made in small but public notices, etc. In all of them, it is necessary to quickly and accurately reflect the addition / correction processing to the mother master / user master.

The present invention provides a medical office system in a process of adding, modifying, and deleting a mother master, which is a model of information such as points and drug prices required for the medical office system, and reflecting the information on a user master. Is a score table master management system for the purpose of greatly reducing the work of the provider of the score table.

[0004]

2. Description of the Related Art To collectively update records in a user master, a provider of a medical office system managing a mother master can update each item of each record for each customer. Manages information that is not allowed. Three types of flags are provided for the non-updatable information, and each has the following meaning.

[0005] 1) A case where the contents of the user master may be changed regardless of whether or not there is a change on the mother master 2) A case where there is no change on the mother master and the user master is changed 3 In the case where there is a change on the mother master side and the user master side has been changed, and by providing information indicating that the update is not possible as a fixed flag in the update data,
Even when each customer intentionally changes the content of a specific item in a specific record, batch update using an update file is realized. This method is described in JP-A-5-81098.

[0006] Further, additions and corrections that are frequently performed by announcements in the official gazette and the like are small in scale, so that update and update data are not collectively updated, and information on additions and corrections is merely communicated to each customer.

[0007]

In order to collectively update records in the user master with update data, the provider of the medical office system updates each item of each record for each customer. Manages information that is not allowed.

[0008] For this reason, the update data has different types of users, and it is difficult to manage the update data for 50 users and 100 users, and the management man-hour becomes large. Furthermore, it is necessary to ensure the management system.

Most of the mother master, including points and drug prices, is composed of officially defined items.
It is basically impossible for each customer to make a change intentionally. However, there are exceptional cases where a customer intentionally changes a specific item of a specific record.

[0010] As described above, since the records in the user master are updated collectively by the update data, the load of the provider of the medical office system managing the mother master is large. In order to reduce the load, means for updating records in the user master collectively without managing information that cannot be updated for each customer is required. By doing so, the update data of the number of users can be the same update data for all the users, and the man-hour and system for managing user information are not required.

[0011]

Means for Solving the Problems To solve the above problems, the update data includes "data before update in the mother master" and "data after update in the mother master".
Was held. As a result, it is possible to determine whether or not the data has been intentionally changed by the customer by comparing the “data before updating in the mother master” and the “data on the user master side”.

"Data before update in mother master"
If "data on the user master side" and "data on the user master side" are the same value, the record is not a record intentionally changed by the customer, and is updated to "data updated on the mother master".

"Data before update in mother master"
If the value of "user master side" is different from that of "user master side", it is a record intentionally changed by the customer, so leave "user master side data" as it is or update it to "updated data in mother master" It is up to the customer to decide.
However, even in the entire user master, the number of records intentionally changed is small, the probability that the record is included in the update data is even lower, and the number of records determined by the customer is small. In addition, the management of the record intentionally changed by the customer can be simplified by managing the record by the customer.

[0014] By creating a material indicating the contents of addition, modification and deletion based on the updated data, the time required for creating a material for communicating the information of addition, modification and deletion can be reduced. Can be.

[0015]

FIG. 1 is a system configuration diagram showing an example of an embodiment of the present invention.

Reference numeral 101 denotes an apparatus provided with means for displaying the contents of a mother master managed by a provider of a medical office system. Reference numeral 102 denotes a mother master managed by a provider of the medical office system. Reference numeral 103 denotes a group of additional data for adding a record to the mother master / user master. Reference numeral 104 denotes a group of correction data for performing record correction on the mother master / user master. Reference numeral 105 denotes a group of deletion data for performing record deletion for the mother master / user master. Reference numeral 106 denotes addition / modification / deletion data (update data) generation, update of the mother master / user master with the update data, and addition / modification / deletion based on the update data.
This is a business program for printing deletion information. 107
Is a material indicating additional contents to be printed based on the additional data. Reference numeral 108 denotes a material indicating the contents of the correction printed based on the correction data. Reference numeral 109 denotes a material indicating the content of the deletion printed based on the deletion data. In this way, by creating a document indicating the details of addition, modification, and deletion based on the updated data, it is possible to reduce the time required for creating a document for communicating information on addition, modification, and deletion. Thus, the contact with the customer can be further expedited. Reference numeral 110 denotes a printer for printing the additional information 107, the correction information 108, and the deletion information 109.

Reference numeral 111 denotes a communication line.

Reference numeral 121 denotes an apparatus provided with means for displaying the contents of a user master used by each customer. 12
2 is a user master used by each customer. 123
Is a business program for updating the mother master / user master with addition / modification / deletion data (update data) and printing addition / modification / deletion information based on the updated data. Reference numeral 124 denotes a material indicating additional contents to be printed based on the additional data 103. 125 is the correction data 10
4 is a document showing the contents of correction printed on the basis of No. 4. 126
Is a material indicating the content of deletion to be printed based on the deletion data 105. 127 is the additional information 124 / modification information 12
5. A printer for printing the deletion information 126.

FIG. 2 is a diagram showing a transition of file updating according to an example of the embodiment of the present invention.

Reference numeral 201 denotes a mother master 102 managed by a provider of the medical office system. The management number 202 is a number uniquely assigned in the mother master 201. A data portion 203 is a data portion including a price, a name, and the like for the management number 202.

Reference numeral 211 denotes correction data generated by the provider of the medical office system designating the management number of the record to be corrected, the contents after correction, and the correction number in the apparatus 101 because three corrections of the mother master occurred. 104. Since the modification number 212 has a characteristic that the modification is frequently performed by the notification in the official gazette, the same modification number is set to the modification group at the same time in order to identify the modification time. Therefore, the same correction number is one correction unit. In the correction data 211, the correction number 212
Describes a case where only “001” exists. 213
Is the latest data portion that has been correctly updated for the mother master. The pre-correction data section 214 is the data section immediately before updating the mother master.

Reference numeral 221 denotes the latest mother master that has been correctly corrected in the mother master 201 by data whose correction serial number is "001".

FIG. 3 is a diagram showing a transition of file updating according to an example of the embodiment of the present invention.

Reference numeral 301 denotes a user master 122. Further, the user master 301 describes a case where the user himself has extracted and created all the records of the mother masters 102 and 201. Further, the user master 301 describes a case where the name of the specific record is intentionally changed by the user himself (see 302 and 303).

Reference numeral 311 denotes a user master 30
When the correction is made using the data whose correction number is “001”, it is judged that it is not necessary to leave an individual name for the intentionally changed item 302 in operation, and the correction is permitted. It is the latest user master that has been updated by designating that it is necessary to keep individual names for the items 303 that have been designated and intentionally changed, and designating that they cannot be modified. The instruction of non-modifiability may be a means for prompting the non-modifiable instruction from the device 121 during the correction with the correction data and making a determination based on the return value, and any instruction method may be used.

FIG. 4 is a flowchart showing a process of correcting a user master by using the correction data according to the present invention.
Update means (steps 404, 406, 407, 40
8) is a means necessary for implementing the present invention. Correction data 2
In the case where the user master 301 is corrected by the three cases 11, corrections with the management number “000001” of the correction data 211 are 1-1) and 1-2), and corrections with the management number “000002” are 2-1) to 2). -3), the correction by the management number "000003" will be described in 3-1) to 3-3).

1-1) The first record (correction number “001”, management number “000001”) from the correction data 211
..) (step 401). At this time, if the correction data is at the end of the file, the correction processing ends (step 402). Since the referenced record is the modification number “001” to be modified, the record having the same management number is referenced from the user master 301 (step 40).
3,404). At this time, if the record having the same management number cannot be referred to, the record is excluded from the correction (step 40).
5).

1-2) User Master Data Section 304
And the pre-update data portion 215 of the correction data are all the same, so that the post-update data portion of the correction data 211 is corrected to be the same as the post-update data portion, that is, corrected to “data after update in the mother master” (step 405 406, 40
7).

2-1) Next, from the correction data 211, 2
Record No. (modification number "001", management number "00000"
2 "...) (Step 401). Since the referenced record is the correction number" 001 "to be corrected,
The record having the same management number is referred from the user master 301 (steps 403 and 404).

2-2) "2 Name" 302 of User Master
Is unmatched with the item of “2 name” 218 in the correction data, so “2 name” 302 is intentionally changed (steps 406 and 408).

2-3) "2 Names" 3 Changed Intentionally
02, the device 121 prompts an instruction that the correction is not possible,
When receiving an instruction to allow modification, the control number "00" in the user master
The record having "0002" is corrected in the same manner as the updated data portion of the correction data 211, that is, is corrected to "updated data in the mother master" (steps 407 and 40).
8).

3-1) Next, from the correction data 211, 3
Record No. (modification number "001", management number "00000"
3 "...) (Step 401). Since the referenced record is the correction number" 001 "to be corrected,
Referring to the management number from the user master (step 40)
3,404).

3-2) "2 Name" 303 of User Master
Is unmatched with the item of “2 name” 219 of the correction data, so “2 name” 303 is intentionally changed (steps 406 and 408).

3-3) "2 Names" 3 Changed Intentionally
03, the device 121 prompts an instruction that the correction is not possible,
If you receive an instruction that cannot be modified, the user master's control number "
The record having "000003" is not corrected, that is, "data on the user master side" remains as it is. (Step 4
07,408).

Thus, in the score table master management system of the present invention, the update data of the number of users is
The update data can be the same for all users, and no man-hour and system for managing user information is required.

[0036]

As described above, according to the present invention, when the records in the user master are updated collectively by the update data, the records in the user master can be updated without managing the information which cannot be changed for each customer. Updates can be performed collectively, and the update data of the number of users can be made the same update data for all users, eliminating the need for man-hours and a system for managing user information.

Further, by creating a material indicating the contents of addition / modification / deletion based on the updated data, addition / modification / deletion is performed.
By shortening the time required for preparing the material for communicating the information of the deletion, it is possible to further speed up the contact with the customer.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of an embodiment of the present invention.

FIG. 2 is a diagram illustrating a file configuration when a file is updated according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating a file configuration at the time of updating a file according to an embodiment of the present invention.

FIG. 4 is a flowchart of file updating according to an embodiment of the present invention.

[Explanation of symbols]

101: "Score table master management system" of the management source, 1
02,201,221 ... Mother master, 103-10
5,211 ... updated data, 107 to 109, 124 to 1
26: Material indicating the update contents, 121: "Score table master management system" on the user side, 122, 301, 3
11: user master, 213: data before update in the mother master, 214: data after update in the mother master, 301 to 308: processing steps.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Yoshihiro Kitani 1-6-27 Shinsuna, Koto-ku, Tokyo Public Information Division, Hitachi, Ltd.

Claims (2)

[Claims] 1. A medical office system comprising at least a master file storing information on points of medical practice and drug prices of medicines and update data for updating the master file. A score table master management system having two types of updated data and determining whether update is possible or not using data before update. 2. A score table master management system according to claim 1, wherein a material indicating the contents of the update is created based on the update data.