JP2012003552A - Accounting management device, accounting management method and accounting management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To tell estimated waiting time before accounting is performed to a patient who has utilized a medical institution.SOLUTION: When there is an application of accounting, an accounting management device 100 acquires accounting required time when the patient has received an examination in the same medical care department from an accounting reception DB150 for a revisiting patient already in an accounting waiting state. Also, for a new patient already in the accounting waiting state, the accounting management device 100 calculates the accounting required time for which the average accounting required time corresponding to the age of the patient is adjusted corresponding to the type of the medical care department and an insurance. Then, by totaling each accounting required time acquired for the revisiting patient and each accounting required time calculated to the new patient, the accounting management device 100 calculates the estimated waiting time before the accounting of the patient who has applied for the accounting just now is calculated.

Description

  The present invention relates to an accounting management device, an accounting management method, and an accounting management program.

  In medical institutions such as hospitals and clinics, a technique has been proposed for allowing a user to guess the waiting time until a medical examination is performed. For these technologies, for example, the approximate waiting time is calculated based on the technology that makes it possible to know the number of people who received before you, and the average usage time per person and the number of people currently in the waiting room. Technology exists.

JP 2008-242853 A

  By the way, as a scene where a waiting time occurs in a patient who uses a medical institution, for example, there is a waiting time until a payment for paying a consultation fee in addition to a waiting time until a medical examination is performed. Thus, for example, the patient is restricted not only in the waiting time until the examination but also in the waiting time until the accounting.

  A patient using a medical institution is charged as a consultation fee or the like according to the content of the medical practice performed on the patient. The medical institution's accountant creates and confirms a voucher that includes points and details according to the medical practice. Then, after the voucher is created and confirmed by the accounting staff, the patient is accounted for.

  In addition, the time required for a medical institution's accountant to create and check a slip varies greatly depending on the contents of the medical practice. Thus, depending on the content of the medical practice performed on the patient, it may be considered that a certain amount of time is required for creating and confirming the slip. For this reason, even if there is only one patient waiting for the transaction, there is a waiting time until the patient is accounted for.

  As described above, the time required for a medical institution's accountant to create and confirm a voucher varies greatly depending on the content of the medical practice, but the above-mentioned conventional technology considers the time required to create and check a voucher. The waiting time at the time of accounting cannot be calculated accurately.

  The disclosed technique has been made in view of the above, and is an accounting management apparatus, accounting management method, and accounting that can teach an estimated waiting time until accounting is performed for a patient using a medical institution The purpose is to provide a management program.

  The accounting management device disclosed in the present application includes, in one aspect, an accounting reception DB and an estimation unit. The accounting reception DB includes patient identification information for identifying a plurality of patients, attribute information regarding the patient identified by the patient identification information, and accounting time required for creating an accounting slip distributed to the patient identified by the patient identification information Are stored in association with each other. When the estimation unit receives an application for accounting including the patient identification information of any of the plurality of patients, the estimation unit applies for the accounting and the accounting slip is not created. Get attribute information of patient waiting. Further, the estimation unit refers to the accounting reception DB, acquires the accounting required time associated with the attribute information related to the acquired attribute information, and uses each of the acquired accounting required time to Estimate the waiting time for.

  According to one aspect of the accounting management device, accounting management method, and accounting management program disclosed in the present application, it is possible to teach an estimated waiting time until accounting is performed on a patient using a medical institution.

FIG. 1 is a functional block diagram illustrating the configuration of the accounting management apparatus according to the first embodiment. FIG. 2 is a diagram illustrating an example of definition information that defines data stored in the transaction reception DB according to the first embodiment. FIG. 3 is a diagram illustrating an example of data stored in the transaction reception DB according to the first embodiment. FIG. 4 is a diagram illustrating an example of definition information that defines data stored in the patient DB according to the first embodiment. FIG. 5 is a diagram illustrating an example of data stored in the patient DB according to the first embodiment. FIG. 6 is a diagram illustrating an example of definition information that defines data stored in the insurance DB according to the first embodiment. FIG. 7 is a diagram illustrating an example of data stored in the insurance DB according to the first embodiment. FIG. 8 is a diagram illustrating an example of definition information for defining data to be written in the average accounting required time table according to the first embodiment. FIG. 9 is a diagram illustrating an example of data stored in the average transaction required time table according to the first embodiment. FIG. 10 is a diagram illustrating an example of definition information for defining data to be written in the adjustment coefficient table for each public insurance according to the first embodiment. FIG. 11 is a diagram illustrating an example of data stored in the adjustment coefficient table by public insurance according to the first embodiment. FIG. 12 is a diagram illustrating an example of definition information for defining data to be written in the clinical department adjustment coefficient table according to the first embodiment. FIG. 13 is a diagram illustrating an example of data stored in the clinical department adjustment coefficient table according to the first embodiment. FIG. 14 is a diagram illustrating the flow of the accounting reception work process according to the first embodiment. FIG. 15 is a diagram illustrating a flow of the accounting reception work process according to the first embodiment. FIG. 16 is a diagram illustrating a flow of accounting operation processing according to the first embodiment. FIG. 17 is a diagram illustrating a flow of the accounting reception work process according to the second embodiment. FIG. 18 is a diagram illustrating a flow of the accounting reception work process according to the second embodiment. FIG. 19 is a diagram illustrating an example of a computer that executes an accounting management program.

  Hereinafter, an embodiment of an accounting management device, an accounting management method, and an accounting management program disclosed in the present application will be described in detail with reference to the drawings. In addition, the technique which this application discloses is not limited by the Example mentioned later as one Embodiment of the accounting management apparatus, accounting management method, and accounting management program which this application discloses. In addition, the embodiments can be appropriately combined within a range in which processing contents are not contradictory.

[Configuration of Accounting Management Device (Example 1)]
FIG. 1 is a functional block diagram illustrating the configuration of the accounting management apparatus according to the first embodiment. As shown in FIG. 1, the accounting management apparatus 100 includes an input unit 110, an output unit 120, a patient DB (Data Base) 130, an insurance DB (Data Base) 140, and an accounting reception DB (Data Base) 150. The accounting reception service execution unit 160 and the accounting service execution unit 170 are included.

  The input unit 110, for example, inputs information on a patient who has applied for accounting at the accounting window after the examination. For example, a person in charge of accounting refers to a medical record or the like of a patient who has applied for accounting via the input unit 110 and inputs a patient ID assigned to the patient. The input unit 110 includes input devices such as a keyboard, a mouse, and a touch pad, for example.

  The output unit 120 outputs and displays an estimated waiting time until the accounting calculated by the accounting reception task execution unit 160 described later. An output device such as a monitor or a display is included. When the input unit 110 includes a mouse, the pointing device function can be realized in cooperation with the monitor included in the output unit 120. In addition, when the input unit 110 has another input device such as a touch pad, the pointing device function can be realized as in the case of the mouse. The patient DB 130 is a storage unit that stores information related to patients. The insurance DB 140 is a storage unit that stores information related to insurance that a patient joins. The transaction reception DB 150 is a storage unit that stores information related to the transaction performed by the patient.

  FIG. 2 is a diagram illustrating an example of definition information that defines data stored in the transaction reception DB according to the first embodiment. The definition information shown in FIG. 2 has an item name, the number of digits, and remarks.

  For example, as shown in FIG. 2, the item name “record classification”, the number of digits “9 (01)”, and the remarks “1: for the current day 2: for the day before (the past)” are described as the definition information. . For example, as shown in FIG. 2, the item name “patient ID” and the number of digits “9 (10)” are described as the definition information. For example, as shown in FIG. 2, the item name “clinical department code” and the number of digits “X (02)” are described as the definition information. For example, as shown in FIG. 2, the item name “primary insurer number” and the number of digits “9 (08)” are described as the definition information.

  For example, as shown in FIG. 2, the item name “public expense 1 insurer number” and the number of digits “9 (08)” are described as the definition information. Also, for example, as shown in FIG. 2, the item name “public expense 2 insurer number” and the number of digits “9 (08)” are described as the definition information. Also, for example, as shown in FIG. 2, the item name “public expense 3 insurer number” and the number of digits “9 (08)” are described as the definition information. Also, for example, as shown in FIG. 2, the item name “public expense 4 insurer number” and the number of digits “9 (08)” are described as the definition information.

  Also, for example, as shown in FIG. 2, as shown in FIG. 2, as definition information, item name “age flag”, number of digits “9 (01)”, remarks “1: under 3 years old 2: over 3 years old "Under 6 years 0: Except 1 and 2" is described. Also, for example, as shown in FIG. 2, the item name “update date”, the number of digits “9 (08)”, and the remarks “yyyyMMdd” are described as the definition information. For example, as shown in FIG. 2, the item name “accounting start time”, the number of digits “9 (08)”, and the remarks “HHmmssss. Updated from accounting operations” are described as the definition information. For example, as shown in FIG. 2, the item name “accounting end time”, the number of digits “9 (08)”, and the remarks “HHmmssss. Updated from accounting operations” are described as the definition information. For example, as shown in FIG. 2, the item name “accounting time”, the number of digits “9 (08)”, and the remarks “HHmmssss. Updated from accounting service” are described as definition information.

  FIG. 3 is a diagram illustrating an example of data stored in the transaction reception DB according to the first embodiment. As shown in FIG. 3, the accounting reception DB 150 stores data relating to record classification, patient ID, and clinical department code in a state of being associated with each other. Furthermore, as shown in FIG. 3, in addition to these data, the accounting reception DB 150 includes a main insurance insurer number, a public expense 1 insurer number, a public expense 2 insurer number, a public expense 3 insurer number, and a public expense 4 insurer. Each data relating to the number is stored in an associated state. Further, as shown in FIG. 3, in addition to these data, the accounting reception DB 150 stores data relating to the age flag, the update date, the accounting start time, the accounting end time, and the accounting required time in association with each other. Is done.

  For example, as shown in FIG. 3, the first line of the transaction acceptance DB 150 is stored in a state in which record classification: “1”, patient ID: “0000000010”, and department code: “01” are associated with each other. . Further, as shown in FIG. 3, in addition to these data, the accounting reception DB 150 stores the main insurance insurer number: “06000000” and the public expense 1 insurer number “51000000” in association with each other. . Further, as shown in FIG. 3, in addition to these data, the accounting reception DB 150 includes an age flag: “0”, an update date: “20100513”, an accounting start time: “10011023”, and an accounting end time “10060023”. , Accounting required time: “49000” is stored in an associated state.

  The data on the first line of the transaction reception DB 150 indicates the transaction reception data for the current day because the record classification is “1”. Further, since the clinical department code is “01”, it indicates that the patient has received a medical department corresponding to the clinical department code: “01”. Moreover, since the record exists in the items of the main insurance insurer number and the public expense 1 insurer number, it indicates that this patient can receive the application of the main insurance and the public expense 1 insurance. Further, since the age flag is “0”, this indicates that the patient does not fall under 3 years old, 3 years old or older and under 6 years old. In addition, since records exist in the items of accounting start time, accounting end time, and accounting required time, this patient indicates that accounting has been completed.

  Also, for example, as shown in FIG. 3, the seventh line of the transaction acceptance DB 150 stores the record classification: “2”, patient ID: “0000000010”, and clinical department code: “01” in association with each other. Is done. Further, as shown in FIG. 3, in addition to these data, the seventh line of the accounting reception DB 150 is stored in a state in which the main insurance insurer number: “06000000” is associated. Furthermore, as shown in FIG. 3, in addition to these data, the 7th line of the accounting reception DB 150 includes an age flag: “0”, an update date: “20100512”, an accounting start time: “10051023”, and an accounting end. The time “10120023” and the required transaction time: “69000” are stored in association with each other.

  The data on the seventh line of the transaction acceptance DB 150 indicates that the record classification is “2”, so that it is the transaction acceptance data for the previous day (the past). Further, since the clinical department code is “01”, it indicates that the patient has received a medical department corresponding to the clinical department code: “01”. Moreover, since the record exists in the item of the main insurance insurer number, it indicates that this patient can receive the main insurance. Further, since the age flag is “0”, this indicates that the patient does not fall under 3 years old, 3 years old or older and under 6 years old. In addition, since records exist in the items of accounting start time, accounting end time, and accounting required time, this patient indicates that accounting has been completed.

  FIG. 4 is a diagram illustrating an example of definition information that defines data stored in the patient DB according to the first embodiment. The definition information shown in FIG. 4 has an item name, the number of digits, and remarks.

  For example, as shown in FIG. 4, the item name “patient ID” and the number of digits “9 (10)” are described as the definition information. For example, as shown in FIG. 4, the item name “Japanese name” and the number of digits “X (20)” are described as the definition information. Also, for example, as shown in FIG. 4, the item name “sex”, the number of digits “9 (01)”, and the remarks “1: male 2: female” are described as the definition information. Also, for example, as shown in FIG. 4, the item name “date of birth”, the number of digits “9 (08)”, and the remarks “yyyyMMdd” are described as the definition information.

  FIG. 5 is a diagram illustrating an example of data stored in the patient DB according to the first embodiment. As shown in FIG. 5, the patient DB 130 stores each data related to the patient ID, Japanese name, sex, and date of birth in association with each other.

  For example, as shown in FIG. 5, patient ID: “0000000010”, Japanese name: “Ichiro Yamada”, gender: “1”, date of birth: “19600306” are associated with the first line of the patient DB 130. Stored in the stored state.

  FIG. 6 is a diagram illustrating an example of definition information that defines data stored in the insurance DB according to the first embodiment. The definition information shown in FIG. 6 has an item name, the number of digits, and remarks.

  For example, as shown in FIG. 6, the item name “patient ID” and the number of digits “9 (10)” are described as the definition information. For example, as shown in FIG. 6, the item name “primary insurer number” and the number of digits “9 (08)” are described as the definition information. For example, as shown in FIG. 6, the item name “main insurance symbol number” and the number of digits “X (40)” are described as the definition information.

  For example, as shown in FIG. 6, the item name “public expense 1 insurer number” and the number of digits “9 (08)” are described as the definition information. For example, as shown in FIG. 6, the item name “public expense 1 symbol number” and the number of digits “X (40)” are described as the definition information. For example, as shown in FIG. 6, the item name “public expense 2 insurer number” and the number of digits “9 (08)” are described as the definition information. For example, as shown in FIG. 6, the item name “public expense 2 symbol number” and the number of digits “X (40)” are described as the definition information.

  For example, as shown in FIG. 6, the item name “public expense 3 insurer number” and the number of digits “9 (08)” are described as the definition information. Also, for example, as shown in FIG. 6, the item name “Public Expense 3 Symbol Number” and the number of digits “X (40)” are described as the definition information. For example, as shown in FIG. 6, the item name “public expense 4 insurer number” and the number of digits “9 (08)” are described as the definition information. For example, as shown in FIG. 6, the item name “public expense 4 symbol number” and the number of digits “X (40)” are described as the definition information.

  FIG. 7 is a diagram illustrating an example of data stored in the insurance DB according to the first embodiment. As shown in FIG. 7, the insurance DB 150 stores a patient ID, a main insurance insurer number, a public expense 1 insurer number, a public expense 1 symbol number, a public expense 2 insurer number, and a public expense 2 symbol number in association with each other. Is done.

  As shown in FIG. 7, the first line of the insurance DB 150 includes, for example, patient ID: “0000000010”, primary insurance insurer number: “06000000”, public expense 1 insurer number: “Oh ah ah”, public expense 1 symbol number : “111111” is stored in an associated state. In the case of a patient who can receive a plurality of public expense insurance, the public expense insurer number and the public expense symbol number corresponding to the number of the public expense insurance are stored in each item.

  The patient DB 130, the insurance DB 140, and the accounting reception DB 150 can be realized by a personal computer or a server. For example, a DBMS (Data Base Management System) is provided so that various data stored in the patient DB 130, the insurance DB 140, and the accounting reception DB 150 can be shared by a plurality of accounting management apparatuses 100. May be managed.

  Returning to FIG. 1, the transaction acceptance service execution unit 160 executes processing associated with reception of the transaction application from the patient. For example, as illustrated in FIG. 1, the accounting reception task execution unit 160 includes an update unit 161, a determination unit 162, an acquisition unit 163, a calculation unit 164, and an estimation unit 165.

  The update unit 161 executes a patient basic information reading process, a transaction reception DB editing process, and an age flag editing process. When a patient ID or a department code is input from the accountant via the input unit 110, the updating unit 161 first executes a basic patient information reading process. For example, the update unit 161 reads the patient's birth date associated with the patient ID from the patient DB 130 and also reads the patient insurance information from the insurance DB 140.

  Next, the update unit 161 executes a transaction acceptance DB editing process. For example, the update unit 161 sets the record classification, patient ID, clinical department code, main insurance insurer number, public expenses 1 to 4 insurer number, and update date in the accounting reception DB 150. Subsequently, the update unit 161 executes an age flag editing process. For example, the update unit 161 calculates the age of the patient from the date of birth read from the patient DB 130, and sets an age flag corresponding to the calculated age in the accounting reception DB 150. For example, if the patient's age is less than 3 years old, “1” is set. If the patient's age is 3 to 6 years old, “2” is set. If the patient's age is less than 3 years old, 3 years old or more. If it does not correspond to both under 6 years old, that is, over 6 years old, “0” is set.

  When the determination unit 162 accepts an application for accounting from a certain patient, each patient who has applied for accounting before this patient and is already waiting for accounting is a reexamination patient or a new patient Determine whether. For example, the determination unit 162 reads one piece of data received on the current day from the transaction reception DB 150 based on the record classification, and determines whether the read data is unaccounted data. As a result of the determination, if the data is unaccounted data, the determination unit 162 stores the unaccounted data in the work memory and determines whether or not the reading of the data received on the day is completed. As a result of the determination, if the reading of the data for the reception on the day is not completed, the determination unit 162 again reads one piece of data for the reception on the day from the transaction reception DB 150 and executes the same processing as described above. .

  On the other hand, if the result of the determination indicates that the data for the current day has been read, the determination unit 162 reads one unaccounted data saved in the work memory, and the attribute matches. The data for before reception is retrieved from the accounting reception DB 150. For example, the attribute corresponds to a patient ID, a department code, insurance information, or the like. And the determination part 162 determines whether the data for the reception before that day with the same attribute were searched from the accounting reception DB150.

  As a result of the determination, when the corresponding data for the day before reception with matching attributes can be searched, the determination unit 162 determines that the patient associated with the unaccounted data read from the work memory is a reexamination patient. . The revisited patient means a patient who has revisited the same medical department that has been visited before within two months from the previous visit.

  On the other hand, as a result of the determination, if the corresponding data before the reception on the day with matching attributes cannot be searched, the determination unit 162 determines that the patient associated with the unaccounted data read from the work memory is a new one. Determined to be affected. A new patient means a patient who has visited the first department that has not been visited before, or a patient who has visited the same department that has been previously visited again after two months. To do.

  The acquisition unit 163 calculates the time required for accounting that can be restrained by a patient who has been revisited among the patients who have received an application for accounting and patients who are waiting for accounting including this patient. The reexamination patient accounting required time calculation process is executed. For example, the acquisition unit 163 identifies a record whose attributes match among the records before the reception on the day for the patient determined by the determination unit 162 to be a revisit patient. And the acquisition part 163 acquires the accounting required time of the specified record, and stores it in work memory.

  The calculation unit 164 calculates a required accounting time during which a patient who has applied for accounting can be restrained by a patient who has been determined to be a new patient among patients who have received an application for accounting and patients who are waiting for accounting including the patient. Execute processing to calculate accounting time. The calculation unit 164 previously holds an average accounting required time table, an adjustment coefficient table by public expense insurance, and a clinical department adjustment coefficient table used for calculating the accounting required time that can be restrained by a new patient who is already in an accounting waiting state.

  The average accounting time table stores average accounting time for each age flag. Moreover, the adjustment coefficient table classified by public expense insurance stores an insurance adjustment coefficient for adjusting the average accounting time in association with the public expense insurer number. The medical department adjustment coefficient table stores a medical department adjustment coefficient for adjusting the average accounting time in association with the medical department code.

  FIG. 8 is a diagram illustrating an example of definition information for defining data to be written in the average accounting required time table according to the first embodiment. For example, as shown in FIG. 8, as definition information, the item name “age flag”, the number of digits “9 (01)”, the remarks “1: less than 3 years old 2: more than 3 years but less than 6 years 0: other than 1 or 2 Is described. In addition, as shown in FIG. 8, the item name “average accounting time”, the number of digits “9 (03)”, and the remark “unit is minutes” are described as the definition information.

  FIG. 9 is a diagram illustrating an example of data stored in the average transaction required time table according to the first embodiment. As shown in FIG. 9, the age flag and the average accounting required time are stored in the average accounting required time table in association with each other. For example, in the first row of the adjustment coefficient table for each public insurance, the age flag: “0” and the average accounting required time: “010” are stored in association with each other. That is, the patient who is “under 3 years old” corresponding to the age flag “0” indicates that the time required for preparing the account is “10”. Depending on the age of the patient, the items to be described in the specification and the method for calculating the medical score may differ. Therefore, the calculation unit 164 can calculate the accounting creation time according to the age of the patient by referring to the average accounting required time table.

  FIG. 10 is a diagram illustrating an example of definition information for defining data to be written in the adjustment coefficient table for each public insurance according to the first embodiment. For example, as shown in FIG. 10, the item name “public insurer number” and the number of digits “9 (08)” are described as the definition information. Also, as shown in FIG. 10, the item name “adjustment coefficient”, the number of digits “9 (05)”, and the remark “input“ 10000 ”if“ 1.0000 ”” are described as the definition information. The “adjustment coefficient” in the adjustment coefficient table for public expenditure insurance is a coefficient for adjusting the average accounting time corresponding to the age of the patient according to the patient's insurance coverage.

  FIG. 11 is a diagram illustrating an example of data stored in the adjustment coefficient table by public insurance according to the first embodiment. As shown in FIG. 11, the public expense insurance adjustment coefficient table stores a public expense insurer number and an adjustment coefficient in association with each other. For example, in the first row of the adjustment coefficient table for each public insurance, the public insurance insurer number: “51000000” and the adjustment coefficient: “10001” are stored in association with each other. The method for calculating the medical treatment fee differs depending on the type of insurance for the patient, that is, the insurance applied to the patient. Therefore, the new patient accounting prescription time calculation unit 164 can calculate the accounting preparation time corresponding to the type of insurance applied to the patient by using the adjustment coefficient stored and entered in the adjustment coefficient table classified by public expenditure insurance. . That is, it is possible to set an arbitrary public expense insurer number and adjustment coefficient for each hospital in the adjustment coefficient table by public expense insurance.

  FIG. 12 is a diagram illustrating an example of definition information for defining data to be written in the clinical department adjustment coefficient table according to the first embodiment. For example, as shown in FIG. 12, the item name “clinical department code” and the number of digits “X (02)” are described as the definition information. As shown in FIG. 12, the item name “adjustment coefficient”, the number of digits “9 (05)”, and the remark “input“ 10000 ”if“ 1.0000 ”” are described as the definition information.

  FIG. 13 is a diagram illustrating an example of data stored in the clinical department adjustment coefficient table according to the first embodiment. As shown in FIG. 13, the clinical department code and the adjustment coefficient are stored in association with each other in the clinical department adjustment coefficient table. For example, in the first line of the adjustment coefficient table for each medical department, the medical department code: “01” and the adjustment coefficient: “10001” are stored in association with each other. The items to be described in the specification and the method for calculating the number of medical treatments may differ depending on the clinical departments that the patient consulted. Therefore, the calculation part 164 can calculate the accounting preparation time according to the difference of the medical examination department of the patient by using the adjustment coefficient memorize | stored in the adjustment coefficient table classified by medical department. In the medical department adjustment coefficient table, arbitrary medical departments and adjustment coefficients can be set for each hospital.

  Then, the calculation unit 164 calculates the required accounting time that can be restrained by a new patient that is already in the accounting waiting state. That is, the calculation unit 164 calculates the new patient average accounting required time editing process, the public expense insurance adjustment coefficient editing process, the clinical department adjustment coefficient editing process, and the new patient accounting required time for new patients that are waiting for the accounting. The calculation process is executed in order.

  First, the calculation unit 164 executes a new affliction average accounting required time editing process. For example, the calculation unit 164 acquires, from the average accounting required time table, the average accounting required time corresponding to the age flag of the patient determined by the determining unit 162 as a new patient.

  Next, the calculation unit 164 executes an adjustment coefficient editing process for each public insurance. For example, the calculation unit 164 acquires an adjustment coefficient corresponding to the public expense insurance number of the patient from the adjustment coefficient table for each public expense insurance for the patient determined to be a new affliction by the determination unit 162.

  Subsequently, the calculation unit 164 executes an adjustment coefficient editing process for each department. For example, the calculation unit 164 obtains an adjustment coefficient corresponding to the clinical department code of the patient from the clinical department adjustment coefficient table for the patient determined to be a new patient by the determination unit 162.

  And the calculation part 164 performs the new patient accounting required time calculation process. For example, the calculation unit 164 obtains the accounting required time by multiplying the average accounting required time by the adjustment coefficient corresponding to the public insurance number and the adjustment coefficient corresponding to the medical department code, and stores the required accounting time in the work memory.

  The estimation unit 165 calculates an estimated waiting time of a patient who has applied for accounting. For example, the estimation unit 165 determines whether or not the processing by the acquisition unit 163 or the calculation unit 164 has been completed for the unaccounted data received on the day.

  As a result of the determination, when the processing by the acquisition unit 163 or the calculation unit 164 is completed for the unaccounted data received on the day, the estimation unit 165 reads all the data of the required accounting time stored in the work memory. . Then, the estimation unit 165 adds together the data of the required transaction time read from the work memory, and outputs and displays the calculation result on the output unit 120 as the estimated waiting time. The estimated waiting time is taught, for example, verbally or by paper to a patient who has applied for accounting by an accountant.

  The work memory described above corresponds to, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory. In addition, the accounting acceptance service execution unit 160 includes an electronic circuit such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). Note that the accounting reception task execution unit 160 may use an application specific integrated circuit (ASIC) in place of the CPU or MPU.

  When the accounting reception work by the accounting reception service execution unit 160 ends, the accounting service execution unit 170 executes a billing amount calculation process for calculating a billing amount to be entered in the patient's accounting slip for the application for accounting. Subsequently, the accounting task execution unit 170 executes an accounting reception DB update process for recording the accounting time required for creating the accounting slip of the patient who has applied for accounting.

  The billing amount calculation process will be described. Then, the accounting operation execution unit 170 receives the patient's department code, primary insurance insurer number, public expense 1 insurer number, public expense 2 insurer number, public expense 3 insurer number, public expense 4 insurer number, A billing amount is calculated using data such as an age flag. Subsequently, the accounting task execution unit 170 creates an accounting slip in which the patient information and the billing amount are entered. The accounting task execution unit 170 acquires the start time of the billing amount calculation process as the accounting start time.

  The accounting reception DB update process will be described. When the billing amount calculation process ends, the accounting task execution unit 170 acquires the end time of the billing amount calculation process as the accounting end time. Then, the accounting business execution unit 170 calculates the accounting time by subtracting the accounting start time from the accounting end time. After calculating the required accounting time, the accounting task execution unit 170 records the accounting start time, the accounting end time, and the accounting required time in the accounting reception DB 150 in association with the patient ID of the patient who applied for accounting.

  The accounting required time recorded in the accounting reception DB 150 by the accounting reception DB update process executed by the accounting business execution unit 170 is used for, for example, calculation of the estimated waiting time by the above-described accounting reception business execution unit 160.

[Processing by Accounting Management Device (Example 1)]
The flow of processing by the accounting operation management apparatus according to the first embodiment will be described with reference to FIGS. In the following, a flow of processing when one accounting management device 100 is installed in a medical institution and the one accounting management device 100 executes accounting reception work processing and accounting business processing will be described. FIG. 14 and FIG. 15 are diagrams illustrating a flow of the accounting reception work process according to the first embodiment. FIG. 16 is a diagram illustrating a flow of accounting operation processing according to the first embodiment.

[Accounting transaction processing]
First, using FIG. 14 and FIG. 15, the flow of the accounting operation reception process by the above-described accounting reception operation execution unit 160 will be described.

  As shown in FIG. 14, the update unit 161 executes a basic patient information reading process when a patient ID or a clinical department code is input from the accounting staff via the input unit 110 (step S101, YES). Step S102). Note that the update unit 161 repeats the same determination with the determination result of step S101 as NO when there is no input of the patient ID, the department code, or the like from the accounting staff via the input unit 110.

  Next, the update unit 161 executes a transaction acceptance DB editing process (step S103), and executes an age flag editing process (step S104).

  Subsequently, as shown in FIG. 15, the determination unit 162 reads one piece of data received on the current day from the transaction reception DB 150 based on the record classification (step S <b> 105), and determines whether the read data is unaccounted data. It is determined whether or not (step S106). As a result of the determination, if the data is unaccounted data (step S106, YES), the determining unit 162 stores the unaccounted data in the work memory (step S107).

  Then, the determination unit 162 determines whether or not the reading of data for the reception on the day has been completed (step S108). As a result of the determination, if the reading of the data for the reception on the day is not completed (step S108, NO), the process returns to step S105 described above, and the processing up to step S107 is executed.

  Here, the description returns to step S106. As a result of the determination, when the data is not unaccounted data (step S106, NO), the determination unit 162 proceeds to the process of step S108 described above.

  Here, the description returns to step S108. As a result of the determination, when reading of the data for the reception on the day is completed (step S108, YES), the determination unit 162 acquires one piece of unaccounted data stored in step S107 (step S109). Then, the determination unit 162 searches the accounting reception DB 150 for the data before the reception on the day in which the attributes such as the patient ID and the department code match the unaccounted data acquired in step S109 (step S110). ).

  And the determination part 162 determines whether the data for the reception before that day with the same attribute were searched from accounting reception DB150 as a result of the search of step S110 mentioned above (step S111). When the corresponding data for the day before reception with matching attributes can be searched (step S111, YES), the determination unit 162 determines that the main of the unaccounted data acquired in step S109 is a reexamination patient. And according to the determination result by the determination part 162, the acquisition part 163 performs a reexamination patient accounting required time acquisition process (step S112). And the acquisition part 163 preserve | saves a process result (step S113).

  On the other hand, when the corresponding data before the reception on the day with matching attributes cannot be searched (step S111, NO), the determination unit 162 determines that the main of the unaccounted data acquired in step S109 is a new disease. To do. And according to the determination result by the determination part 162, the calculation part 164 performs the new affairs average accounting required time edit process and the adjustment coefficient edit process classified by public expense insurance in order (step S114, step S115). Subsequently, the calculation unit 164 sequentially executes the adjustment coefficient editing process for each department and the new patient accounting required time calculation process (steps S116 and S117). And the calculation part 164 preserve | saves the process result of the new patient accounting required time calculation process performed in step S117 similarly to step S113 mentioned above.

  Subsequently, the estimation unit 165 determines whether or not the processing by the acquisition unit 163 or the calculation unit 164 has been completed for the unaccounted data received on that day (step S118). As a result of the determination, when the processing by the acquisition unit 163 or the calculation unit 164 is not completed for the unaccounted data received on the current day (NO in step S118), the process returns to step S109 described above and the processing up to step S117 is performed. .

  As a result of the determination, when the processing by the acquisition unit 163 or the calculation unit 164 is completed for the unaccounted data received on the day (step S118, YES), the estimation unit 165 executes the following processing. That is, the estimation unit 165 executes a transaction waiting time calculation process (step S119).

  In steps S105 to S108 described above, the case where one piece of data received on the current day is read and processed is described. However, the present invention is not limited to this. May be performed.

[Accounting processing (Example 1)]
Next, the flow of accounting operation processing by the above-described accounting operation execution unit 170 will be described with reference to FIG. As shown in FIG. 16, when the accounting acceptance service by the accounting acceptance task execution unit 160 ends (YES in step S201), the accounting task execution unit 170 calculates a billing amount for the patient who applied for accounting (step S202). Execute. Then, following the billing amount calculation process, the accounting task execution unit 170 executes an accounting reception DB update process for recording the accounting time required to create the accounting slip for the patient who applied for accounting (step S203). . If the accounting reception operation has not ended, the accounting operation execution unit 170 repeats the same determination with “NO” as the determination result of step S201.

[Effects of Example 1]
As described above, the accounting management apparatus 100 determines that a re-examination patient has the same department for a patient who is determined to re-examine among patients who are waiting for an accounting including a patient who has applied for an accounting application. The required accounting time at the time of consultation is acquired from the accounting reception DB 150. In addition, the accounting management apparatus 100 first calculates an average accounting according to the age of the new patient for patients determined to be a new patient among patients waiting for accounting including the patient who has applied for accounting. Get the required time. Subsequently, the accounting management apparatus 100 calculates the accounting time by multiplying the acquired average accounting time by the adjustment coefficient according to the type of medical department and the insurance configuration. Then, the accounting management apparatus 100 sums up each accounting time acquired for the reexamination patient waiting for accounting and each accounting time calculated for the new patient waiting for accounting, thereby accounting for the patient who has applied for accounting. Calculate the estimated waiting time until For this reason, according to the first embodiment, it is possible to teach an estimated waiting time until accounting is performed for a patient using a medical institution.

  In the first embodiment described above, for example, for a patient who is determined to be a new patient among patients in a waiting state including a patient who has applied for a transaction, a case where the required transaction time is calculated by the following procedure is described. did. The procedure is to obtain an average accounting time according to the age of a new patient who is waiting for accounting. Subsequently, the required accounting time is calculated by multiplying the average required accounting time by an adjustment factor corresponding to the type of medical department and the insurance composition. However, the present invention is not limited to this. For example, a past accounting time for a patient whose attribute is similar to that of a new patient in an accounting waiting state may be acquired from the accounting reception DB 150 and used. Therefore, hereinafter, the flow of processing by the accounting management apparatus according to the second embodiment will be described with reference to FIGS. 17 and 18.

  The processes shown in steps S301 to S304 shown in FIG. 17 are the same as the processes in steps S101 to S104 shown in FIG. 14 described in the first embodiment.

  For example, as illustrated in FIG. 17, the update unit 161 executes a basic patient information reading process when a patient ID or a clinical department code is input from the accounting staff via the input unit 110 (step S301, YES). (Step S302). Note that the update unit 161 repeats the same determination with the determination result of step S101 as NO when there is no input of the patient ID, the department code, or the like from the accounting staff via the input unit 110. Next, the update unit 161 executes a transaction acceptance DB editing process (step S303), and then executes an age flag editing process (step S304).

  Further, the processing from step S305 to step S313 shown in FIG. 18, the processing of step S315 and step S316 are the same as the processing of step S105 to step S113 shown in FIG. 15 and the processing of step S118 and step S119 shown in FIG. Are the same. However, the process of step S314 illustrated in FIG. 18 is different from the processes of step S114 to step S117 illustrated in FIG. 15 described in the first embodiment.

  For example, as shown in FIG. 18, the determination unit 162 reads one piece of data for the current day reception from the transaction reception DB 150 based on the record classification (step S305), and whether or not the read data is unaccounted data. Is determined (step S306). As a result of the determination, if it is unaccounted data (step S306, YES), the determination unit 162 stores the unaccounted data in the work memory (step S307).

  Then, the determination unit 162 determines whether or not reading of data for the reception on the day is completed (step S308). As a result of the determination, if the reading of the data for the reception on the day is not completed (step S308, NO), the process returns to step S305 described above, and the process up to step S307 is executed.

  Here, the description returns to step S306. As a result of the determination, when the data is not unaccounted data (step S306, NO), the determination unit 162 proceeds to the process of step S308 described above.

  Here, the description returns to step S308. As a result of the determination, when reading of the data for the reception on the day is completed (step S308, YES), the determination unit 162 acquires one unaccounted data saved in step S307 (step S309). Then, the determination unit 162 searches the accounting reception DB 150 for the data before reception on the day in which the unaccounted data acquired in step S109 and the attributes such as the patient ID and the department code match, that is, past data (step S310). ).

  Then, as a result of the search in step S310 described above, the determination unit 162 determines whether or not data for the day before reception that matches the attributes has been searched from the transaction reception DB 150 (step S311). When the corresponding data for the day before reception with matching attributes can be searched (step S311, YES), the determination unit 162 determines that the main of the unaccounted data acquired in step S309 is the reexamination patient. And according to the determination result by the determination part 162, the acquisition part 163 performs a reexamination patient accounting required time acquisition process (step S312). And the acquisition part 163 preserve | saves a process result in work memory (step S313).

  On the other hand, when the corresponding data before the reception on the day with matching attributes cannot be searched (step S311, NO), the determination unit 162 determines that the main of the unaccounted data acquired in step S109 is a new disease. judge. And according to the determination result by the determination part 162, the calculation part 164 performs the process of step S314 different from the process of step S114 of FIG. 15 demonstrated in Example 1-step S117.

  That is, when accepting an application for accounting from a certain patient, the calculating unit 164 executes the average accounting required time calculation process for the previous day for a new patient waiting for accounting including this patient (step S314). For example, the calculation unit 164 obtains, for each new patient that is waiting for accounting, the past accounting time for a patient having attribute information similar to the attribute information of the new patient from the accounting reception DB 150, and requires accounting. Calculate time. The attribute information is information including at least one piece of information related to the age of the patient, the medical department received by the patient, and the type of insurance applied to the patient.

  For example, the calculation unit 164 calculates, from the accounting reception DB 150, the accounting time required for the reception on the previous day for other patients of the same age group with the same clinical department code and insurance configuration for each new patient that is waiting for accounting. Get all. For example, the calculation unit 164 assumes that the clinical department code of a new patient waiting for a certain accounting is “01”, the insurance composition is “main insurance, public expense 1 insurance”, and the age is “25 years old”. In this case, the calculation unit 164 has a diagnosis code of “01”, an insurance composition of “main insurance, public expense 1 insurance”, and an age of “20 to 29 years old” for the new patient waiting for payment. All the accounting time required for the previous day regarding the patient is acquired from the accounting reception DB 150.

  And the calculation part 164 calculates | requires the accounting required time by calculating | requiring the average of the accounting required time acquired from accounting reception DB150 for every new patient. For example, for a new patient whose clinical department code is “01”, insurance composition is “primary insurance, public expense 1 insurance”, and age is “25 years old”, the clinical department code and insurance composition are the same and the same age group It is assumed that ten accounting times for the previous day regarding other patients are acquired from the accounting reception DB 150. In this case, the calculation unit 164 calculates the required accounting time by obtaining an average of the ten required accounting times.

  And the calculation part 164 preserve | saves the process result performed in step S314 similarly to step S313 mentioned above.

  Subsequently, the estimation unit 165 performs the process of step S315 in the same manner as step S118 of FIG. 15 described in the first embodiment. That is, the estimation unit 165 determines whether or not the processing by the acquisition unit 163 or the calculation unit 164 has been completed for the unaccounted data received on the day (step S315). As a result of the determination, if the processing by the acquisition unit 163 or the calculation unit 164 is not completed for the unaccounted data for the reception on the day (step S315, NO), the process returns to the above-described step S309 and the processing up to step S314 is performed. .

  As a result of the determination, when the processing by the acquisition unit 163 or the calculation unit 164 has been completed for the unaccounted data received on the day (step S315, YES), the estimation unit 165 executes the process of step S316. That is, similarly to step S119 of FIG. 15 described in the first embodiment, the estimation unit 165 executes an accounting waiting time calculation process (step S316).

  In the first embodiment described above, for example, the required accounting time that can be restrained by a patient who is determined to be a new patient among the patients who are waiting for accounting including the patient who has applied for accounting at the accounting window of a medical institution is calculated. In some cases, prior data is required. For example, in the first embodiment, it is necessary to previously store an average accounting required time table, an adjustment coefficient table by public insurance, a medical department adjustment coefficient table, and the like. On the other hand, in the second embodiment, the past required transaction time for a patient whose attribute is similar to that of a new patient that is waiting for the transaction is acquired from the transaction reception DB 150 and used. That is, in the second embodiment, it is not necessary to previously hold the average accounting required time table, the adjustment coefficient table by public expense insurance, the clinical department adjustment coefficient table, etc. described in the first embodiment. For this reason, according to the second embodiment, it is possible to calculate the estimated waiting time until the patient who came to apply for accounting is accounted for at a medical institution or the like using existing data in the accounting reception DB 150.

  In the second embodiment, for each new patient that is waiting for accounting, attributes such as the department code and insurance composition are the same, and the accounting required time for the previous day regarding other patients of the same age group is accepted for accounting. Although the case where all are acquired from DB150 was demonstrated, it is not limited to this. For example, a predetermined number or one time required for the previous day reception regarding other patients of the same age group with the same attributes such as the department code and insurance composition may be acquired from the transaction reception DB 150. . In the case where a predetermined number of required accounting times are acquired from the accounting reception DB 150, the required accounting time is obtained by obtaining an average of these required accounting times. On the other hand, when only one accounting time is acquired from the accounting reception DB 150, the acquired accounting time is used as it is.

  In addition, for each new patient that is in a waiting state for accounting, for example, all the accounting time required for the previous day reception regarding other patients having the same attributes such as the department code and insurance composition and the same age from the accounting reception DB 150, A predetermined number or only one may be acquired. In addition, if the attributes such as the department code and insurance composition are the same, and there is no accounting time for the previous day regarding other patients of the same age, the accounting time that satisfies the following conditions is acquired. May be. For example, for each new patient that is in a state of waiting for accounting, all the required accounting times for the previous day regarding other patients with the closest age may be acquired by a predetermined number or only one. Further, for example, not only the accounting time required for the previous day reception but also all the required accounting time may be acquired from all records stored in the accounting reception DB 150.

  In the above-described embodiment, a case has been described in which, when there are a plurality of patients waiting for a transaction, the estimated waiting time until the patient who came to apply for the transaction is accounted for is calculated. However, the present invention is not limited to this, even if there is no patient waiting for accounting for which an accounting application has not been made and an accounting application has been made before the patient who has applied for accounting. An estimated waiting time can also be calculated for patients who have applied for accounting. For example, if the patient who has applied for accounting is a reexamination patient, the past accounting time required when this patient has received the same department is obtained from the accounting reception DB 150 as the estimated waiting time. On the other hand, if the patient who applied for the accounting is a new patient, the estimated waiting time is calculated using the average accounting required time table, the adjustment coefficient table for each public insurance, and the clinical department adjustment coefficient table. Alternatively, when a patient who has applied for accounting is a new patient, the estimated waiting time is calculated by acquiring accounting required time corresponding to a patient having attribute information similar to the patient's attribute information from the accounting reception DB 150. .

  Hereinafter, other embodiments of the accounting management device, accounting management method, and accounting management program disclosed in the present application will be described.

(1) Omission of patient determination in waiting state for accounting In the above-described first and second embodiments, the case where the estimated waiting time until the accounting for the patient who came to apply for accounting is calculated according to the following procedure has been described. First, it is determined whether each patient waiting for accounting including a patient who has applied for accounting corresponds to a revisited patient or a new patient. Subsequently, the accounting time is calculated for each of the revisited patient who is waiting for the accounting and the new patient who is waiting for the accounting. Then, using each accounting time required for the reexamination patient who is waiting for accounting and each accounting time required for the new patient who is waiting for accounting, the patient who came to apply for accounting is accounted for. Calculate the estimated waiting time until However, the present invention is not limited to this, and when a patient comes to apply for accounting, it is estimated by obtaining the past accounting time of a patient who is associated with the patient and the attribute that is waiting for accounting including this patient. The waiting time may be calculated.

  For example, for each patient in a state of waiting for accounting, including a patient who has applied for accounting, all past accounting required times of patients with matching attributes are acquired from the accounting reception DB 150. Then, the average waiting time for each patient is calculated by calculating the average accounting time obtained for each patient and adding the average accounting time obtained for each patient. Is calculated. In this way, it is possible to easily calculate the estimated waiting time until the patient who has entered the transaction application is accounted for, compared to the first and second embodiments described above. Note that patients whose attributes are related to patients who are waiting for payment are those who are waiting for payment, including those who have applied for payment, such as patients whose age, medical department, and insurance composition are similar. Applicable.

(2) Calculation of Estimated Wait Time According to Number of Accountants In addition, in Example 1 described above, for example, as shown in FIGS. 14 to 16, one account management device 100 is installed in a medical institution, The case where the single accounting management apparatus 100 executes the accounting reception job process and the accounting job process has been described. Here, for example, when a plurality of accounting management devices 100 are installed in a medical institution or the like, and there are a plurality of accounting staffs who perform accounting reception business processing and accounting business processing, estimation according to the number of accounting staffs Calculate the waiting time. For example, the estimated waiting time is calculated by dividing the estimated waiting time calculated by the method of Example 1, Example 2 or (1) described above by the number of accountants. In this way, an estimated waiting time corresponding to the number of accountants can be taught to patients who have applied for accounting.

  Note that the accountant who performs the accounting operation after the account acceptance operation performed by another accountant inputs the patient ID assigned to the patient with reference to the patient's chart and the like. The accounting business execution unit 170 acquires various data associated with the patient ID input by the accounting staff from the accounting reception DB 150. For example, the accounting operation execution unit 170 uses the patient ID of the patient who has applied for accounting as a key, the department code, the main insurance insurer number, the public expense 1 insurer number, the public expense 2 insurer number, the public expense 3 insurer number, Data such as public expenses 4 insurer number and age flag is acquired. Then, as in the first embodiment described above, the accounting operation execution unit 170 uses the data such as the insurance information such as the medical department code of the patient who has applied for accounting, the main insurance insurer number, and data such as the age flag, and the like. Create an accounting slip that is calculated and filled in with the amount charged.

(3) Apparatus Configuration The configuration of the accounting management apparatus 100 shown in FIG. 1 is functionally conceptual and does not necessarily need to be physically configured as illustrated. For example, the accounting reception task execution unit 160 and the accounting task execution unit 170 of the accounting management apparatus 100 shown in FIG. 1 may be integrated functionally or physically. As described above, all or part of the accounting management apparatus can be configured to be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions.

(4) Accounting Management Method As described below, the accounting management method applicable to the accounting management apparatus 100 is realized by the embodiment described above.

  For example, when there is an application for accounting from a patient, the accounting reception information is stored for the accounting required time of the patient having attribute information related to the attribute information of each patient for each accounting waiting patient including the patient. The accounting required time acquisition step acquired from the department is included. The accounting reception information storage unit stores attribute information related to the patient including patient identification information for uniquely identifying the patient, and accounting time required for creating an accounting slip to be distributed to the patient. Furthermore, an accounting management method including a waiting time calculating step of calculating an estimated waiting time of a patient who has applied for accounting is realized using each accounting required time acquired in the accounting required time acquiring step.

(5) Account Management Program Various processes executed by the account management apparatus 100 described above can also be realized by executing a program prepared in advance by an electronic device such as a personal computer. For various processes executed by the accounting management apparatus 100, see, for example, FIGS. 14 to 16, FIG. 17, FIG.

  Therefore, in the following, an example of a computer that executes an accounting management program that realizes the same function as the processing executed by the accounting management apparatus 100 described above will be described with reference to FIG. FIG. 19 is a diagram illustrating an example of a computer that executes an accounting management program.

  As illustrated in FIG. 19, a computer 200 that realizes the same function as the process executed by the accounting management apparatus 100 includes a CPU (Central Processing Unit) 210 that executes various arithmetic processes. The computer 200 also includes an input device 220 and an output device 230 that receive data input from the user.

  The input device 220 corresponds to, for example, a keyboard or a mouse. The output device 230 corresponds to a monitor or a display. When the input device 220 includes a mouse, the pointing device function can be realized in cooperation with a monitor included in the output device 230. Also, when the input device 220 has another input device such as a touch pad, the pointing device function can be realized as in the case of the mouse.

  Further, as shown in FIG. 19, the computer 200 includes a medium reading device 240 that reads a program or the like from a storage medium, and a network interface device 250 that exchanges data with another computer via a network. Further, as shown in FIG. 19, the computer 200 includes a RAM (Random Access Memory) 260 that temporarily stores various types of information and a hard disk device 270. Each device 210 to 270 is connected to the bus 280.

  Instead of the CPU 210 described above, for example, an electronic circuit such as an MPU (Micro Processing Unit) or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array) can be used. Further, instead of the RAM 260, a semiconductor memory device such as a flash memory can be used.

  The hard disk device 270 stores a transaction management program 271 and transaction management data 272 that perform the same functions as the processing executed by the transaction management apparatus 100 described above. Note that the accounting management program 271 can be appropriately distributed and stored in a storage unit of another computer that is communicably connected via a network.

  Then, the CPU 210 reads the accounting management program 271 from the hard disk device 270 and develops it in the RAM 260, whereby the accounting management program 271 functions as an accounting management process 261 as shown in FIG. The accounting management process 261 expands various data such as the accounting management data 272 read from the hard disk device 270 in an area allocated to itself on the RAM 260 as appropriate, and executes various processes based on the expanded various data.

  The accounting management process 261 includes, for example, processing executed by the accounting reception task execution unit 160 and the accounting task execution unit 170 of the accounting management apparatus 100 shown in FIG.

  The accounting management program 271 is not necessarily stored in the hard disk device 270 from the beginning. For example, each program is stored in a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, and an IC card inserted into the computer 200. Then, the computer 200 may read and execute each program from these.

  Further, each program is stored in “another computer (or server)” connected to the computer 200 via a public line, the Internet, a LAN, a WAN, or the like. Then, the computer 200 may read and execute each program from these.

100 Accounting Management Device 110 Input Unit 120 Output Unit 130 Patient DB (Data Base)
140 Insurance DB (Data Base)
150 Accounting DB (Data Base)
160 Accounting reception business execution unit 161 Update unit 162 Determination unit 163 Acquisition unit 164 Calculation unit 165 Estimation unit 170 Accounting business execution unit 200 Computer 210 CPU
220 Input Device 230 Output Device 240 Medium Reading Device 250 Network Interface Device 260 RAM
261 Accounting management process 270 Hard disk device 271 Accounting management program 272 Accounting management data

Claims (8)

Associating patient identification information for identifying a plurality of patients, attribute information about the patient identified by the patient identification information, and accounting time required for creating an accounting slip distributed to the patient identified by the patient identification information The accounting reception DB to memorize,
The attribute of the patient waiting for accounting in which the application for accounting is applied and the accounting slip is not created when an application for accounting including the patient identification information of any one of the plurality of patients is accepted Acquiring information, referring to the accounting reception DB, acquiring the accounting time associated with the attribute information related to the acquired attribute information, and using each of the acquired accounting time, An accounting management apparatus comprising: an estimation unit that estimates waiting time related to a patient. A determination unit for determining whether each patient is a revisit patient or a new patient for each of the patients waiting for accounting;
When the determination unit determines that the patient waiting for payment is a revisit patient, the estimation unit refers to the transaction reception DB and corresponds to the patient identification information and the attribute information of the patient waiting for payment And when the determination unit determines that the patient waiting for payment is a new patient, it refers to the transaction reception DB and corresponds to the attribute information of the patient waiting for payment. 2. The accounting management apparatus according to claim 1, wherein said accounting required time is acquired, and said waiting time is estimated using each of said acquired accounting required times. A determination unit for determining whether each patient is a revisit patient or a new patient for each of the patients waiting for accounting;
When the determination unit determines that the patient waiting for payment is a revisit patient, the estimation unit refers to the transaction reception DB and corresponds to the patient identification information and the attribute information of the patient waiting for payment And when the determination unit determines that the waiting patient is a new patient, calculates the required accounting time according to the attribute information of the waiting patient, The accounting management apparatus according to claim 1, wherein the waiting time is estimated using the acquired accounting time and the calculated accounting time. The attribute information is information including at least one or more of age information and clinical department information of a patient indicated by the patient identification information and information on a type of insurance applied to the patient,
When the determination unit determines that the patient waiting for payment is a new patient, the estimation unit includes the age information, the clinical department information, and the insurance included in the attribute information of the patient waiting for payment The accounting management apparatus according to claim 3, wherein accounting required time corresponding to each of the types of information is calculated. When the number of patients waiting for the accounting includes a plurality of the patients,
The said estimation part acquires accounting required time about each of the said plurality of said waiting patients, and calculates the said waiting time using the value which totaled each acquired accounting required time. The accounting management device described.   The accounting management apparatus according to claim 5, wherein the estimating unit estimates the waiting time by dividing the summed value by the number of accounting personnel who create the accounting slip. An accounting management method applied to an accounting management apparatus for managing patient accounting,
When an application for accounting including patient identification information for identifying a plurality of patients is received, the patient identification information, attribute information about the patient identified by the patient identification information, and the patient identified by the patient identification information are distributed. Referring to the accounting reception DB that stores the accounting time required to create the accounting slip in association with each other, apply for the accounting, and acquire the attribute information of the patient waiting for accounting that has not been created And acquiring the accounting time associated with the attribute information related to the acquired attribute information, and using each of the acquired accounting time, a waiting time for any one of the plurality of patients is obtained. An accounting management method comprising a step of estimating. An accounting management program to be executed by a computer as an accounting management device for managing patient accounting,
In the computer,
When an application for accounting including patient identification information for identifying a plurality of patients is received, the patient identification information, attribute information about the patient identified by the patient identification information, and the patient identified by the patient identification information are distributed. Referring to the accounting reception DB that stores the accounting time required to create the accounting slip in association with each other, apply for the accounting, and acquire the attribute information of the patient waiting for accounting that has not been created And acquiring the accounting time associated with the attribute information related to the acquired attribute information, and using each of the acquired accounting time, a waiting time for any one of the plurality of patients is obtained. An accounting management program characterized by causing an estimation procedure to be executed.

Images