JP2022174362A - Accounts receivable management program, accounts receivable management method, and information processing apparatus - Google Patents

Abstract

To provide an accounts receivable management program, an accounts receivable management method, and an information processing apparatus that create an installment payment plan reasonable for a patient.SOLUTION: An information processing apparatus 101 acquires medical examination information 110 on a patient 102 who has accounts available. The information processing apparatus 101 specifies an outpatient visit schedule (outpatient visit interval) 120 for the patient 102 based on the acquired medical examination information 110. The information processing apparatus 101 determines whether an outpatient visit interval indicated by the specified outpatient visit schedule (outpatient visit interval) 120 meets a standard in which an outpatient visit interval is equal to or more than a first threshold (for example, 70 days or more) or equal to or less than a second threshold different from the first threshold (for example, 14 days or less). When the outpatient visit interval meets the standard of being equal to or more than the first threshold or equal to or less than the second threshold, the information processing apparatus 101 creates an installment payment plan 130 for periodically paying the accounts available in installments regardless of the outpatient visit interval of the patient 102 and outputs the created installment payment plan 130.SELECTED DRAWING: Figure 1

Description

The present invention relates to an uncollected money management program, an uncollected money management method, and an information processing apparatus.

In recent years, it has become clear that there is a considerable amount of uncollected medical expenses at medical institutions. Since an increase in unpaid bills affects the management of medical institutions, it is important to collect unpaid bills by giving appropriate reminders to unpaid patients.

As a related prior art, the storage contents of a master file that stores the procedure of medical care until the illness is cured and the required number of hospital visits for each injury and the storage contents of the master file that stores the patient's illness name and visit information There is a calculation of the patient's total number of visits and the number of remaining visits according to. In addition, using patient information including one or more of insurance burden-related information for multiple patients, medical information for multiple patients, and hospitalization information for multiple patients, and past performance information associated with the patient information There is a technique of generating a calculation model and applying the calculation model to patient information of a certain patient to output information on the risk of non-payment of medical fees for a certain patient.

JP-A-11-213069 JP 2019-091369 A

However, with the conventional technology, it is difficult to make a proper installment plan for the patient when an uncollected amount occurs. For example, when a person in charge of collection or the like proposes payment in installments to a patient who has accrued arrears, it takes a lot of man-hours to determine how the payment should be divided.

In one aspect, the present invention aims at creating a reasonable partial payment plan for a patient.

In one embodiment, medical care information of a patient for whom uncollected money has occurred is acquired, based on the acquired medical care information, the patient's hospital visit schedule is specified, and the hospital visit interval indicated by the specified hospital visit schedule is the first or a second threshold value different from the first threshold value, and if the criterion is satisfied, the uncollected amount regardless of the hospital visit interval An accrued money management program is provided for creating a plan for paying money in installments on a regular basis and outputting the created plan.

ADVANTAGE OF THE INVENTION According to one aspect of the present invention, there is an effect that a proper partial delivery plan can be created for the patient.

FIG. 1 is an explanatory diagram of an example of an uncollected money management method according to an embodiment. FIG. 2 is an explanatory diagram showing a system configuration example of the information processing system 200. As shown in FIG. FIG. 3 is a block diagram showing a hardware configuration example of the uncollected money management device 201. As shown in FIG. FIG. 4 is an explanatory diagram showing an example of the contents stored in the patient DB 220. As shown in FIG. FIG. 5 is an explanatory diagram showing an example of the contents stored in the billing DB 230. As shown in FIG. FIG. 6 is an explanatory diagram showing an example of the contents stored in the partial delivery DB 240. As shown in FIG. FIG. 7 is an explanatory diagram showing an example of the contents stored in the medical history DB 250. As shown in FIG. FIG. 8 is an explanatory diagram showing an example of an electronic medical record screen. FIG. 9 is an explanatory diagram showing an example of an uncollected money management screen. FIG. 10 is a block diagram showing a functional configuration example of the uncollected money management device 201. As shown in FIG. FIG. 11 is an explanatory diagram (Part 1) showing an example of the partial delivery setting screen. FIG. 12 is an explanatory diagram (Part 1) showing an example of the partial delivery management screen. FIG. 13 is an explanatory diagram (part 2) showing an example of the partial delivery setting screen. FIG. 14 is an explanatory diagram (part 2) showing an example of the partial delivery management screen. FIG. 15 is a flowchart showing an example of an uncollected money management processing procedure of the uncollected money management device 201 . FIG. 16 is a flowchart (Part 1) showing an example of a specific processing procedure of the divisional delivery possibility determination processing. FIG. 17 is a flowchart (part 2) showing an example of a specific processing procedure of the divisional delivery availability determination processing. FIG. 18 is a flow chart showing an example of a specific processing procedure of the partial delivery plan creation processing.

Exemplary embodiments of an uncollected money management program, an uncollected money management method, and an information processing apparatus according to the present invention will be described below in detail with reference to the drawings.

(Embodiment)
FIG. 1 is an explanatory diagram of an example of an uncollected money management method according to an embodiment. In FIG. 1, an information processing device 101 is a computer that creates a payment plan for a patient with uncollected money. A patient is a person who receives medical treatment or examination at a medical institution. Medical institutions are, for example, hospitals and clinics.

Accounts receivable is the amount of medical expenses paid by a patient that has not been paid by the due date (for example, the day of medical treatment or the deadline for payment after the date of medical treatment). Medical expenses include, for example, medical expenses, drug expenses, hospitalization expenses, examination expenses, and the like. The installment payment plan is a plan for paying (paying) the receivables in installments.

Here, the total amount of accounts receivable at a medical institution can become so large that it affects the management of the medical institution and cannot be ignored. On the other hand, many cases of uncollected medical expenses are small, and time-consuming dunning is inefficient. For this reason, it is important to collect uncollected medical expenses by appropriately reminding unpaid patients.

For example, as one of the dunning tasks, staff members of the medical department may negotiate with the patient to collect the uncollected money. At this time, if it is difficult for the person himself/herself to pay, it is conceivable to ask a family member or the like to pay the advance. However, if the person is the representative of the household and there is no one who can pay for it, there is no choice but to collect it from the person.

In addition, in the case of patients who are in financial difficulty, it is difficult to make a lump sum payment. end up In addition, by accepting payment when possible, there is less pressure on deadlines and less awareness of payment. Moreover, even if there is a payment deadline, there are many cases in which the payment is not collected due to a lack of planning.

In such a case, for example, unpaid medical expenses can be paid in installments according to the patient's hospital visit schedule, thereby reducing the burden on the patient and allowing the patient to make payments in a planned manner. However, if the patient is completely cured and does not visit the hospital during the installment payment period, there are many cases where subsequent payments are not made.

On the other hand, if the number of scheduled visits to the hospital is small, the amount of payment per visit will be large, and payment may be delayed. In this way, the method of division often differs from patient to patient, so it takes a lot of man-hours to manually create an installment plan that suits the patient, which increases the burden on the staff in charge of collection. be.

Therefore, in the present embodiment, an uncollected money management method for automatically creating a suitable partial payment plan for a patient in consideration of the hospital visit schedule of a patient who has incurred an uncollected money will be described. Here, a processing example of the information processing apparatus 101 will be described.

(1) The information processing apparatus 101 acquires medical information of a patient for whom an uncollected amount has occurred. The medical information is information related to the medical treatment of the patient, and includes information specifying, for example, the name of the patient's disease, the date of hospital visit for medical treatment of the injury or disease of the disease name, examination, etc., and the number of hospital visits.

In the example of FIG. 1, it is assumed that the medical information 110 of the patient 102 who has accrued arrears is obtained. The medical information 110 includes, for example, information identifying the disease name of the patient 102 .

(2) The information processing apparatus 101 identifies the patient's hospital visit schedule based on the acquired medical information. The hospital visit schedule is, for example, a hospital visit schedule until the patient's injury or illness is cured (completely cured). The visit schedule indicates, for example, the patient's visit interval. The hospital visit interval is, for example, the average hospital visit interval in the case of visiting the hospital until the patient's injury or disease is healed.

Here, in the case of the same injury (injury, disease), even different patients tend to have the same average number of hospital visits and average hospital visit period until the injury or disease is cured. For this reason, the information processing apparatus 101 identifies, for example, the average number of hospital visits and the average hospital visit period corresponding to the patient's disease name based on the acquired medical care information. Then, the information processing apparatus 101 may specify the patient's hospital visit schedule (hospital visit interval) by dividing the specified average hospital visit period by the average number of hospital visits.

In the example of FIG. 1, it is assumed that a hospital visit schedule (hospital visit interval) 120 of the patient 102 is specified based on the medical information 110 of the patient 102 . A hospital visit schedule (hospital visit interval) 120 indicates an average hospital visit interval when the patient 102 visits the hospital until the injury or disease is healed.

(3) The information processing apparatus 101 determines whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of a first threshold value or more or a second threshold value different from the first threshold value or less. determine whether or not The first threshold can be set arbitrarily, and is set to a value of about 70 days, for example. The second threshold can be set arbitrarily, and is set to a value of about 14 days, for example.

In the example of FIG. 1, the first threshold is "70 days" and the second threshold is "14 days". Also, it is assumed that the hospital visit interval indicated by the hospital visit schedule (hospital visit interval) 120 of the patient 102 satisfies the criteria of a first threshold value or more or a second threshold value or less.

(4) The information processing apparatus 101 creates an installment payment plan for periodically paying the uncollected money in installments regardless of the interval between hospital visits of the patient if the criterion of the first threshold or more or the second threshold or less is satisfied. do. Then, the information processing device 101 outputs the created partial delivery plan. The installment payment plan for paying the receivables in installments at regular intervals is, for example, a monthly installment payment plan. The monthly installment payment plan is a plan to pay a fixed amount (installment amount) on a fixed date (reference date) every month.

Here, if the interval between hospital visits is too long, there is a risk that the patient will become less conscious of the payment or forget to promise to pay. Therefore, in the example of FIG. 1, the information processing apparatus 101, for example, when the patient's 102 hospital visit interval is equal to or greater than the first threshold value (70 days), regardless of the patient's 102 hospital visit interval, Create plan 130 .

On the other hand, if the hospital visit interval is too short, the number of payments will increase, which will increase the burden on the patient 102 and increase the time and effort of staff such as receptionists and accounting staff. Therefore, in the example of FIG. 1, the information processing apparatus 101, for example, when the patient's 102 hospital visit interval is equal to or less than the second threshold value (14 days), regardless of the patient's 102 hospital visit interval, Create plan 130 .

In this way, according to the information processing apparatus 101, it is possible to create a proper installment plan for a patient who has accrued arrears. As a result, the person in charge of collection (for example, an employee of the medical affairs department) can propose a plan for installment payment of the uncollected money to a patient who has difficulty in making a lump sum payment. A well-planned and regular deadline can increase patient awareness of payment and lead to the collection of outstanding balances.

For example, if the interval between hospital visits is too long, there is a risk that the patient will become less conscious of payment or forget to promise to pay. For this reason, the information processing apparatus 101 creates a monthly installment payment plan 130 instead of a plan for paying the uncollected money in installments for each hospital visit, for example, when the hospital visit interval of the patient 102 is equal to or greater than the first threshold value.

On the other hand, if the hospital visit interval is too short, the number of payments will increase, which will increase the burden on the patient 102 and increase the time and effort of staff such as receptionists and accounting staff. Therefore, for example, when the patient's 102 outpatient schedule is equal to or less than the second threshold value, the information processing apparatus 101 creates a monthly installment payment plan 130 instead of a plan for paying uncollected money in installments for each hospital visit.

As a result, the collection staff proposes an installment payment plan that allows systematic payment of the uncollected amount so that the patient's awareness of the payment is not weakened and the burden on the patient, staff, etc. is not too large. can do. In addition, by making a plan to periodically pay uncollected payments such as monthly payments, it is possible to prevent unpaid payments even if the patient does not have the opportunity to visit the hospital due to complete recovery.

(System configuration example of information processing system 200)
Next, a system configuration example of an information processing system 200 including the information processing apparatus 101 shown in FIG. 1 will be described. Here, a case where the information processing apparatus 101 shown in FIG. 1 is applied to the uncollected money management apparatus 201 in the information processing system 200 will be described as an example. The information processing system 200 is applied, for example, to a computer system that manages accounts receivable at a medical institution.

FIG. 2 is an explanatory diagram showing a system configuration example of the information processing system 200. As shown in FIG. In FIG. 2 , an information processing system 200 includes an uncollected money management device 201 , an electronic medical record system 202 , a medical accounting system 203 and a plurality of shared terminals 204 . In the information processing system 200 , an uncollected money management device 201 , an electronic medical record system 202 , a medical accounting system 203 and a shared terminal 204 are connected via a wired or wireless network 210 . The network 210 is, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like.

Here, the uncollected money management device 201 has a patient DB (Database) 220, a billing DB 230, a partial payment DB 240, and a medical history DB 250, and creates a partial payment plan for a patient who has an uncollected money. The accounts receivable management device 201 is, for example, a server. The storage contents of various DBs 220, 230, 240, and 250 will be described later with reference to FIGS. 4 to 7. FIG.

The electronic medical record system 202 is a computer system that has an electronic medical record DB 260 and electronically records and stores medical records (medical records) recorded by medical personnel such as doctors and nurses. The electronic medical chart DB 260 records electronic medical chart information. The electronic medical record information is information obtained by digitizing a patient's medical record, and includes, for example, patient information, disease information, medical information, and the like.

The medical accounting system 203 is a computer system that has a medical accounting DB 270 and manages information related to accounting among medical affairs. The medical accounting DB 270 is information related to accounting affairs, and includes, for example, patient information, slip information such as medical expenses, and receipt information. The electronic chart system 202 and the medical accounting system 203 are realized by, for example, one or more servers.

Shared terminal 204 is a computer used by medical institution personnel. The medical institution personnel are, for example, medical affairs personnel, doctors, nurses, and the like. The shared terminal 204 is used, for example, for inputting electronic medical charts, billing medical bills, managing accounts receivable, and the like. The shared terminal 204 is, for example, a PC (Personal Computer), a tablet PC, a smart phone, or the like.

Note that although the uncollected money management device 201 is provided separately from the electronic medical chart system 202 and the like here, the present invention is not limited to this. For example, the uncollected money management device 201 may be realized by any one of the electronic chart system 202 , the medical accounting system 203 and the shared terminal 204 .

(Hardware configuration example of accounts receivable management device 201)
FIG. 3 is a block diagram showing a hardware configuration example of the uncollected money management device 201. As shown in FIG. 3, the uncollected money management device 201 includes a CPU (Central Processing Unit) 301, a memory 302, a disk drive 303, a disk 304, a communication I/F (Interface) 305, and a portable recording medium I/F 306. and a portable recording medium 307 . Also, each component is connected by a bus 300 .

Here, the CPU 301 controls the entire uncollected money management device 201 . The CPU 301 may have multiple cores. The memory 302 has, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash ROM, and the like. Specifically, for example, the flash ROM stores the OS program, the ROM stores the application program, and the RAM is used as a work area for the CPU 301 . A program stored in the memory 302 is loaded into the CPU 301 to cause the CPU 301 to execute coded processing.

The disk drive 303 controls data read/write with respect to the disk 304 under the control of the CPU 301 . The disk 304 stores data written under the control of the disk drive 303 . Examples of the disk 304 include a magnetic disk and an optical disk.

Communication I/F 305 is connected to network 210 through a communication line, and is connected to external computers (for example, electronic chart system 202, medical accounting system 203, shared terminal 204, etc. shown in FIG. 2) via network 210. . A communication I/F 305 serves as an interface between the network 210 and the inside of the apparatus, and controls input/output of data from an external computer. For the communication I/F 305, for example, a modem or a LAN adapter can be adopted.

A portable recording medium I/F 306 controls reading/writing of data from/to a portable recording medium 307 under the control of the CPU 301 . The portable recording medium 307 stores data written under control of the portable recording medium I/F 306 . Examples of the portable recording medium 307 include CD (Compact Disc)-ROM, DVD (Digital Versatile Disk), USB (Universal Serial Bus) memory, and the like.

Note that the uncollected money management device 201 may have, for example, an input device, a display, etc., in addition to the components described above. Further, the electronic medical record system 202, medical accounting system 203, and shared terminal 204 shown in FIG. However, shared terminal 204 has, for example, an input device, a display, etc., in addition to the components described above.

(Storage contents of various DBs 220, 230, 240, 250)
Next, the storage contents of various DBs 220, 230, 240 and 250 will be described with reference to FIGS. 4 to 7. FIG. Various DBs 220, 230, 240, and 250 are realized by storage devices such as the memory 302 and disk 304 shown in FIG. 3, for example.

FIG. 4 is an explanatory diagram showing an example of the contents stored in the patient DB 220. As shown in FIG. In FIG. 4, the patient DB 220 has fields of patient number, name, address, telephone number, household code, attention code and promise to pay. -1 to 400-3) are stored as records.

Here, the patient number is an identifier that uniquely identifies the patient. Name is the name of the patient. Address is the address of the patient. The phone number is the patient's phone number. A household code is an identifier that uniquely identifies a household to which a patient belongs. The attention code is an identifier for classifying a patient to whom attention should be paid when negotiating an uncollected amount.

A caution code with a value of 10 or more is set for a patient requiring attention. For example, a caution code of "0" indicates a normal patient. Attention code "10" indicates a patient requiring attention. Promise to pay is a flag indicating whether or not there is a promise to pay for unpaid bills. A promise to pay "0" indicates no promise to pay. A promise to pay "1" indicates that there is a promise to pay.

FIG. 5 is an explanatory diagram showing an example of the contents stored in the billing DB 230. As shown in FIG. 5, the billing DB 230 contains fields of patient number, date of issue, management number, delinquency code, billing amount, delinquency amount, reason for delinquency, disease name code, number of hospital visits, billing category, hospitalization/discharge flag, and number of hospital visits after discharge. have. By setting information in each field, billing information (for example, billing information 500-1 to 500-7) is stored as a record.

Here, the patient number is an identifier that uniquely identifies the patient. The date of issue is the date on which a slip (bill) for medical expenses or the like is issued. The management number is a number for managing slips such as medical expenses. The overdue code is a flag indicating whether or not medical expenses are overdue. A delinquency code of "0" indicates no delinquency. A delinquency code of "1" indicates delinquency. The amount billed is the amount billed for medical expenses and the like.

The overdue amount is the overdue amount of medical expenses and the like. The delay reason is an identifier indicating the reason for the delay. For example, a delay reason of "10" indicates insufficient funds. The reason for arrears "20" indicates financial hardship. Arrears reason "30" indicates a hospital charge split. Delinquency reason "90" indicates malicious intentional delinquency reason. A delay reason of "0" indicates no delay. A disease name code is an identifier that uniquely identifies a patient's disease name (name of injury or disease). The number of visits indicates the number of times the patient visited the hospital for treatment.

The billing classification indicates classification of medical expenses and the like. For example, billing category "0" indicates outpatient. A billing category of "1" indicates hospitalization. Billing category "9" indicates miscellaneous expenses. The admission/discharge flag indicates admission/discharge of the patient. For example, the hospitalization/discharge flag "1" indicates hospitalization. The admission/discharge flag "0" indicates discharge. Note that the hospitalization/discharge flag “blank” indicates that the patient is not hospitalized or discharged. The number of hospital visits after discharge indicates the number of times the patient visited the hospital for follow-up observation after discharge. The billing DB 230 is created based on the stored contents of the electronic chart DB 260 and the medical accounting DB 270, for example.

FIG. 6 is an explanatory diagram showing an example of the contents stored in the partial delivery DB 240. As shown in FIG. In FIG. 6, the installment payment DB 240 includes patient number, management number, plan number, overdue amount, first time, turn around, installment payment pattern, predicted remaining number of hospital visits, predicted remaining hospital visit period, number of collections, remaining number of times, collection amount, balance amount, It has fields of predicted hospital visit interval, payment reference date, n-th scheduled date (n: natural number) and n-th actual date. By setting information in each field, partial delivery information (for example, partial delivery information 600-1, 600-2) is stored as a record.

Here, the patient number is an identifier that uniquely identifies the patient. The management number is a number for managing slips (bills) such as medical expenses. A plan number is an identifier that identifies a patient's scheduling plan. The overdue amount is the overdue amount of medical expenses, etc. (unit: yen). The first payment indicates the initial payment amount when paying medical expenses in installments. The number of rounds indicates the amount of payment for the second and subsequent installments when paying medical expenses and the like in installments.

The installment pattern indicates a pattern for installment payment of uncollected money. The number of remaining times indicates the pattern of paying the uncollected money in installments for each hospital visit. Outpatient period (monthly payment) shows a pattern of paying the uncollected amount in monthly installments in the remaining outpatient period. The predicted number of remaining hospital visits indicates the prediction result of the number of remaining hospital visits until the patient's injury or disease is healed. The predicted remaining hospital visit period indicates the predicted result of the remaining hospital visit period until the patient's wound or disease is healed. The number of collections indicates the number of times medical expenses and the like have been collected.

The remaining number of times indicates the number of remaining payments. The collected amount indicates the sum of the amount collected out of the accounts receivable. The remaining amount indicates the amount of uncollected amount. The predicted visit interval indicates the predicted result of the patient's visit interval (unit: day). The payment reference date indicates the date of payment for periodic installments such as monthly payment. The n-th scheduled date indicates the n-th scheduled date of payment. The n-th actual date indicates the n-th payment actual date.

FIG. 7 is an explanatory diagram showing an example of the contents stored in the medical history DB 250. As shown in FIG. In FIG. 7, the medical history DB 250 includes a disease name code, disease name, disease classification, average number of hospital visits, average hospital visit period, average number of hospital visits before hospitalization, average hospital visit period before hospitalization, average number of days of hospitalization, average number of hospital visits after discharge, and average number of hospital visits after discharge. It has a hospital visit period field. By setting information in each field, medical history information (for example, medical history information 700-1 to 700-4) is stored as a record.

Here, the disease name code is an identifier that uniquely identifies the disease name of injury or disease. A disease name is a name of an injury or a disease. A disease classification is a classification of an injury or illness. The average number of hospital visits is the average number of hospital visits until the injury or illness is healed. The average length of hospital stay is the average length of hospital stay until the injury or illness is healed. The average number of hospital visits before hospitalization is the average number of hospital visits for examinations and the like before hospitalization.

The average hospital visit period before hospitalization is the average period of hospital visits for examinations and the like before hospitalization. Average hospital stay is the average number of days spent in hospital for medical care. The average number of hospital visits after discharge is the average number of hospital visits for follow-up observation after discharge. The average hospital visit period after discharge is the average period of hospital visits for follow-up observation after discharge. The medical history DB 250 is created based on the contents stored in the electronic chart DB 260, for example.

(Screen example of the electronic medical record screen)
Next, an example of an electronic chart screen displayed on the shared terminal 204 shown in FIG. 2 will be described. The electronic medical chart screen can be displayed by accessing the electronic medical chart system 202 shown in FIG. 2 from the shared terminal 204, for example.

FIG. 8 is an explanatory diagram showing an example of an electronic medical record screen. In FIG. 8, an electronic medical record screen 800 is an example of an operation screen that displays a medical record of patient P1 (Taro Fuji, male, 80 years old). The patient P1 indicates the patient with the patient number "P1". The electronic chart screen 800 includes menu information 801 , chart information 802 , order information 803 , and order auxiliary information 804 .

According to the electronic medical record screen 800, medical staff (doctors, nurses, etc.) can check the medical record of patient P1 (Taro Fuji, male, 80 years old). For example, the chart information 802 includes a disease name code, the date of the first visit, the number of hospital visits, and the like. As a result, the medical staff can check the history of consultations, such as the name of the disease, the date of first visit, and the number of hospital visits.

(Screen example of accounts receivable management screen)
Next, an example of an uncollected money management screen displayed on shared terminal 204 will be described. The accounts receivable management screen can be displayed by accessing the accounts receivable management apparatus 201 shown in FIG. 2 from the shared terminal 204, for example.

FIG. 9 is an explanatory diagram showing an example of an uncollected money management screen. In FIG. 9, an uncollected money management screen 900 is an example of an operation screen that displays information on a patient P1 (Taro Fuji, male, 80 years old) for whom uncollected money has occurred. The accounts receivable management screen 900 includes attribute information 901 , billing/collection information 902 , and negotiation history information 903 .

The attribute information 901 indicates attributes such as the patient's P1 address, telephone number, and attention code. Billing/storage information 902 indicates accounting information, billing information, etc. linked from the medical accounting system 203 . For example, the billing/collection information 902 includes a disease name code, household code, billing date, billing amount, uncollected amount, and the like. The negotiation history information 903 indicates the history of negotiations with the patient P1 regarding uncollected money.

According to the accounts receivable management screen 900, the user can confirm information about the accounts receivable of patient P1 (Taro Fuji, male, 80 years old). The user is, for example, a person in charge of collection (staff of the medical affairs department). For example, by referring to the billing/receipt information 902, the person in charge of collection can confirm when and how much medical expenses were billed for which injury or disease, and how much is currently uncollected.

When the installment setting button 904 is selected (pressed) by the user's input operation using an input device (not shown) on the accounts receivable management screen 900 , an installment setting request is transmitted from the shared terminal 204 to the accounts receivable management apparatus 201 . Here, the partial payment setting request is a request for setting the patient's partial payment plan. As a result, for example, a partial delivery setting screen 1100 as shown in FIG. 11, which will be described later, is displayed.

The partial payment setting request includes, for example, the patient number of patient P1 (Taro Fuji, male, 80 years old). The installment plan is a plan for paying (paying) the uncollected money in installments. The installment setting button 904 is pressed, for example, when the patient requests installment payment or proposes installment payment to the patient when negotiating with the patient regarding uncollected money.

(Example of functional configuration of uncollected money management device 201)
FIG. 10 is a block diagram showing a functional configuration example of the uncollected money management device 201. As shown in FIG. In FIG. 10 , uncollected money management apparatus 201 includes acquisition unit 1001 , identification unit 1002 , determination unit 1003 , creation unit 1004 , and output unit 1005 . Acquisition unit 1001 to output unit 1005 are functions of a control unit. or by the communication I/F 305, the function is realized. The processing results of each functional unit are stored in a storage device such as the memory 302 or disk 304, for example.

Acquisition unit 1001 acquires patient's uncollected information. The uncollected information is information about uncollected money, and includes, for example, information specifying the contents of slips (bills) such as unpaid medical expenses, past payment history, scheduled expiration date, and the like. In addition, the uncollected information may include, for example, the history of negotiations with the patient, the reason for the delay, and the like.

Specifically, for example, the acquisition unit 1001 acquires unpaid patient information from the medical accounting system 203 shown in FIG. Accordingly, the uncollected money management device 201 can display the uncollected money management screen 900 as shown in FIG. 9 in response to a display request from the shared terminal 204, for example.

In addition, the acquisition unit 1001 acquires the medical information of the patient for whom uncollected money has occurred. Medical information is information related to the medical treatment of a patient. For example, information specifying the name of the patient's disease, the date of the patient's first visit to the hospital for examination, etc., the date of the hospital visit, the number of hospital visits, etc. including. Specifically, for example, the acquisition unit 1001 acquires the medical information of a patient who has accrued arrears from the electronic medical record system 202 shown in FIG.

A patient with an uncollected amount may be designated by, for example, a collections person (staff of the medical affairs department), or may be identified by the medical accounting system 203 . More specifically, for example, the acquisition unit 1001 receives an installment payment setting request from the shared terminal 204 for a patient with an uncollected payment, based on the patient number included in the installment setting request, electronically The medical information of the patient is acquired from the chart system 202 . The partial payment setting request is transmitted from the shared terminal 204 to the uncollected money management apparatus 201, for example, when the installment payment setting button 904 is selected on the uncollected money management screen 900 shown in FIG.

The acquired medical care information of the patient is stored in the billing DB 230 shown in FIG. 5 in association with the acquired uncollected information of the patient, for example. As a result, new billing information is stored in the billing DB 230 as a record. The issue date, management number, delinquency code, billing amount, delinquency amount, and delinquency reason included in the billing information are identified, for example, from the patient's uncollected information. Also, the disease name code, number of outpatient visits, billing category, admission/discharge flag, and number of outpatient visits included in the billing information are specified from the patient's medical information, for example.

In the following description, the patient who has accrued money may be referred to as "patient P".

The identification unit 1002 identifies the hospital visit schedule of the patient P based on the acquired medical information. The hospital visit schedule is, for example, a hospital visit schedule until the patient P's injury or illness is cured (completely cured). The hospital visit schedule indicates, for example, the presence or absence of the patient P's hospital visit schedule, the hospital visit interval, the predicted remaining number of hospital visits, the predicted remaining hospital visit period, and the like.

The hospital visit interval is, for example, the average hospital visit interval when the patient P visits the hospital until the injury or disease is cured. It is the predicted remaining number of hospital visits, for example, the remaining average number of hospital visits until the patient P's injury or disease is healed. The predicted remaining period of hospital visits is, for example, the remaining average period of hospital visits in the case of visiting the hospital until the patient P's injury or disease is cured.

Specifically, for example, the identifying unit 1002 refers to the billing DB 230 (see FIG. 5) to identify the disease name code included in the billing information of the patient P. FIG. Next, the identifying unit 1002 refers to the medical history DB 250 shown in FIG. 7 to identify the average number of hospital visits and average hospital visit period corresponding to the identified disease name code. The identification unit 1002 also refers to the billing DB 230 to identify the number of hospital visits included in the billing information of the patient P. FIG.

Then, the specifying unit 1002 calculates the predicted remaining number of hospital visits of the patient P based on the specified average number of hospital visits and the number of hospital visits. Here, if the predicted remaining number of hospital visits is greater than 0, the identifying unit 1002 determines that the patient P is scheduled to visit the hospital, and calculates the hospital visit interval of the patient P based on the average number of hospital visits and the average period of hospital visits.

Alternatively, the identifying unit 1002 may calculate the predicted remaining period of hospital visits of the patient P, and determine that the patient P is scheduled to visit the hospital when the predicted remaining period of hospital visits is greater than zero. The predicted remaining hospital visit period may be calculated, for example, based on the average hospital visit period, the number of hospital visits, and the hospital visit interval, or may be calculated based on the average hospital visit period, the date of the first visit, and the current date.

Calculation examples of the patient P's hospital visit interval, the predicted number of remaining hospital visits, and the predicted remaining hospital visit period will be described later. In addition, when the average number of hospital visits and the average hospital visit period corresponding to the disease name code of patient P are not registered in the medical history DB 250, the specifying unit 1002 corresponds to another disease name code of the same disease classification as the disease name code of patient P. You may also specify the average number of visits and the average duration of visits.

Determining unit 1003 determines whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of a first threshold value Th1 or more or a second threshold value Th2 or less different from the first threshold value Th1. determine whether or not The first threshold Th1 can be arbitrarily set, and is set to a value of about 70 days, for example. The second threshold Th2 can be arbitrarily set, and is set to a value of about 14 days, for example.

When it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is satisfied, the preparation unit 1004 periodically pays the uncollected money in installments regardless of the hospital visit interval of the patient P. create a plan; The installment payment plan for paying the receivables in installments at regular intervals is, for example, a monthly installment payment plan.

The monthly installment payment plan is a plan to pay a fixed amount (installment amount) on a fixed date (reference date) every month. The reference date is set, for example, on the 1st or 25th of every month. However, if the reference date is a holiday, the creation unit 1004 may shift the reference date to a day before or after the holiday.

Also, the monthly payment interval can be set arbitrarily. For example, a monthly installment payment plan may be a plan to pay a fixed amount on a fixed date (such as an annuity payment date) every two months. The uncollected money (total uncollected amount) is specified from the overdue amount included in the billing information of the patient P, for example. When there are uncollected amounts for a plurality of slips of the patient P, the uncollected amount (total uncollected amount) is, for example, the sum total of the overdue amounts included in the patient P's billing information.

Here, if the interval between hospital visits is too long, there is a risk that the patient will become less conscious of the payment or forget to promise to pay. Therefore, for example, when the patient P's hospital visit interval is equal to or greater than the first threshold value Th1, the creation unit 1004 creates a monthly installment payment plan regardless of the patient P's hospital visit interval.

On the other hand, if the interval between hospital visits is too short, the number of payments will increase, and the burden on the patient P will increase, as well as the time and effort of staff such as receptionists and accounting staff. Therefore, for example, when the patient P's hospital visit interval is equal to or less than the second threshold value Th2, the creation unit 1004 creates a monthly installment payment plan regardless of the patient P's hospital visit interval.

More specifically, for example, when the criterion is satisfied, the creation unit 1004 calculates the remaining months of hospital visits based on the predicted remaining hospital visit period indicated by the patient P's scheduled hospital visits. The remaining number of hospital visits corresponds to the number of installments (number of payments). For example, the predicted remaining hospital visit period is assumed to be "320 days". In this case, the number of remaining hospital visit months is "11 months (≈10.5=320/(365/12))". Next, the preparation unit 1004 prepares a monthly installment payment plan by dividing the patient P's uncollected amount (total uncollected amount) by the remaining number of hospital visits. A specific example of the monthly installment payment plan will be described later with reference to FIGS. 13 and 14. FIG.

If the predicted remaining period of hospital visits is short, such as less than one month, it is difficult to create a monthly installment plan. Therefore, for example, when the predicted remaining hospital visit period is less than the preset period min, the creating unit 1004 may calculate the number of remaining installment payment months based on the preset installment payment period X. The period min can be arbitrarily set, and is set to a value of about 30 to 60 days, for example. The installment period X can be set arbitrarily, and is set to a value of about 180 days to 360 days, for example. Then, the creation unit 1004 may create a monthly installment payment plan by dividing the total uncollected amount of the patient P by the number of remaining installment payment months.

In addition, when it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is not satisfied, the creating unit 1004 calculates the uncollected amount for each hospital visit according to the hospital visit schedule of the patient P. Create an installment plan to deliver in installments. The installment payment plan for paying the uncollected money in installments for each visit to the hospital is a plan to pay a predetermined amount (amount of payment in installments) each time the patient P visits the hospital for medical treatment.

Specifically, for example, when the criterion is not satisfied, the creating unit 1004 divides the uncollected money (total uncollected amount) of the patient P by the predicted remaining number of hospital visits indicated by the hospital visit schedule of the patient P, thereby dividing the uncollected money. Create an installment payment plan to pay in installments for each hospital visit. The estimated number of remaining hospital visits corresponds to the number of installments. A specific example of a partial payment plan for paying the uncollected money in installments for each hospital visit will be described later with reference to FIGS. 11 and 12. FIG.

The created partial delivery plan is stored, for example, in the partial delivery DB 240 shown in FIG.

It should be noted that if the hospital visit period is too short, it may be difficult to create an installment plan. Also, if the period of outpatient visits is too long, the number of installments of monthly payments may increase, and the amount of one payment may become small. Therefore, when creating the installment payment plan for the patient P, the creation unit 1004 may determine whether or not the predicted remaining hospital visit period indicated by the patient's P visit schedule is within the first range. Then, if the predicted remaining period of hospital visits is outside the first range, the output unit 1005 may output warning information corresponding to the predicted remaining period of hospital visits. The first range can be arbitrarily set, and is set, for example, to a range of two weeks or more and less than two years.

In addition, when creating an installment payment plan for paying in installments for each hospital visit, if the number of hospital visits is too small, the amount of one payment may become high. Also, if the number of hospital visits is too large, the amount of one payment may be small. Therefore, when creating the installment payment plan for the patient P, the creating unit 1004 may determine whether or not the predicted remaining number of hospital visits indicated by the scheduled hospital visits for the patient P is within the second range. Then, when the predicted remaining number of hospital visits is outside the second range, the output unit 1005 may output warning information corresponding to the predicted remaining number of hospital visits. The second range can be arbitrarily set, and is set, for example, to a range of 2 times or more and less than 100 times.

In addition, when the predicted number of remaining hospital visits indicated by the patient P's scheduled visits is 0, or when the predicted remaining hospital visit period is 0, the identifying unit 1002 determines that the patient P does not have a hospital visit schedule. In this case, the creation unit 1004 may create a partial payment plan for periodically paying the uncollected money in installments regardless of the patient's P hospital visit interval.

Moreover, the patient P may be visiting the hospital for a plurality of diseases. In this case, the identification unit 1002 identifies, for example, the patient P's hospital visit interval, the predicted remaining number of hospital visits, and the predicted remaining hospital visit period for each of the plurality of injuries and diseases based on the patient's P medical information. Then, the identifying unit 1002 determines the hospital visit interval, the predicted remaining number of hospital visits, and the predicted remaining hospital visit period of the injury or disease for which at least one of the predicted remaining number of hospital visits and the predicted remaining hospital visit period is the largest among the plurality of injuries and diseases. It may be specified as a schedule.

The output unit 1005 outputs the created partial delivery plan. The output format of the output unit 1005 includes, for example, storage in a storage device such as the memory 302 and the disk 304, transmission to another computer (for example, the shared terminal 204 shown in FIG. 2) through the communication I/F 305, and not shown. display on a display, print output to a printer (not shown), and the like.

Specifically, for example, the output unit 1005 may refer to the partial payment DB 240 and transmit the created partial payment plan to the shared terminal 204 . As a result, an uncollected money management screen as shown in FIGS. 11 to 14 described later is displayed on the shared terminal 204. FIG.

In addition, the creation unit 1004 may determine whether or not the number of installments (for example, the number of remaining months of hospital visits, the predicted remaining number of hospital visits) in the created partial payment plan is within a predetermined range. The predetermined range can be arbitrarily set, and for example, a range such as 2 times or more and less than 20 times is set. If the number of partial deliveries in the partial delivery plan is outside a predetermined range, the output unit 1005 may output warning information corresponding to the number of partial deliveries when outputting the partial delivery plan.

For example, if the number of installments is too small, the amount of one payment may be high. Therefore, if the number of installments is less than two, the output unit 1005 may output a warning message prompting confirmation of whether the amount of one payment is too high. Also, if the number of installments is too large, the amount of one payment may be small, or the installment plan may become a very long-term plan. Therefore, when the number of installments is 20 or more, the output unit 1005 may output a warning message prompting confirmation of whether the amount of one payment is too small due to too many installments.

Further, the determination unit 1003 may determine whether or not the patient P can be paid in installments based on the patient P attribute information. The attribute information of the patient P is, for example, information representing characteristics of the patient P, and is, for example, a caution code included in the patient information shown in FIG. Specifically, for example, the determination unit 1003 may refer to the patient information of the patient P and determine that the installment payment is not possible for the patient P when the caution code is 10 or more. On the other hand, when the caution code is less than 10, the determination unit 1003 may determine that the patient P can be delivered in installments.

Further, the determination unit 1003 may determine whether or not the patient P can pay in installments based on the uncollected amount of the patient P (total uncollected amount). Specifically, for example, the determination unit 1003 may determine that the patient P cannot pay in installments when the uncollected amount of the patient P (total uncollected amount) is outside a predetermined range. On the other hand, if the uncollected amount (total uncollected amount) is within a predetermined range, the determining unit 1003 may determine that the patient P can be paid in installments. The predetermined range can be arbitrarily set, and for example, a range of 1,000 yen or more and less than 1 million yen is set.

The creating unit 1004 may decide not to create a partial payment plan for the patient P when it is determined that the patient P cannot be paid in installments. In this case, the output unit 1005 may output an error message indicating that the patient P cannot be paid in installments. The error message is, for example, a message to the effect that payment in installments is not possible due to the person requiring caution (caution code of 10 or more).

In addition, even when it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is satisfied, the creating unit 1004 creates an uncollected amount according to the hospital visit schedule of the patient P. It is also possible to create an installment payment plan to pay each hospital visit in installments. Then, the output unit 1005 outputs the installment payment plan for paying the uncollected amount in installments for each hospital visit even if it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is satisfied. may be output. At this time, the output unit 1005 may output a partial payment plan for paying the uncollected money in installments at regular intervals and a partial payment plan for paying the uncollected money in installments for each hospital visit.

In addition, even if it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is not satisfied, the creating unit 1004 determines whether the uncollected You may decide to create an installment payment plan for paying money in installments at regular intervals. Then, the output unit 1005, even if it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is not satisfied, outputs the installment plan for periodically paying the uncollected money. may be output. At this time, the output unit 1005 may output a partial payment plan for paying the uncollected money in installments for each hospital visit and a partial payment plan for periodically paying the uncollected money.

Specifically, for example, the creation unit 1004 creates a partial payment plan for periodically paying the uncollected amount regardless of the hospital visit interval indicated by the patient's P visit schedule, and installs the uncollected amount for each hospital visit according to the patient's P visit schedule. Create a schedule for delivery. Then, the output unit 1005 outputs the created installment plan for paying the uncollected money in installments at regular intervals and the created installment plan for paying the uncollected money in installments for each hospital visit, even if the criteria are satisfied. In addition, the output unit 1005 outputs the created installment plan for paying the uncollected money in installments for each hospital visit and the created installment plan for periodically paying the uncollected money even if the criteria are not met.

In addition, when the patient P has a family member who is visiting the hospital, the creating unit 1004 may create a divided payment plan for the patient P based on the family's visiting schedule. The patient's P family can be identified from the patient's P household code, for example. For example, it can be determined that patients with the same household code are family members.

Specifically, for example, the creating unit 1004 refers to the patient information of the patient P and identifies the household code of the patient P. FIG. Next, the creating unit 1004 refers to the patient DB 220 to identify other patients having the same household code as the patient P. Then, the identifying unit 1002 identifies the hospital visit schedule of the other patient (patient P's family) based on the medical information of the other patient (patient's P's family).

The determination unit 1003 determines whether the hospital visit interval indicated by the specified hospital visit schedule of the other patient (patient P's family member) satisfies the criterion of a first threshold value Th1 or more or a second threshold value Th2 or less. determine whether or not When it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is satisfied, the creating unit 1004 creates the An installment payment plan for periodically paying the uncollected money of the patient P is created.

In addition, when it is determined that the criterion of the first threshold value Th1 or more or the second threshold value Th2 or less is not satisfied, the creation unit 1004 determines whether another patient (patient P's family) is scheduled to visit the hospital. Accordingly, a payment plan for paying the uncollected money of the patient P in installments for each hospital visit is created. In this case, the person in charge of collection negotiates with other patients (patient P's family) to collect the patient P's uncollected money.

Note that the functional units of the uncollected money management device 201 described above may be realized by a plurality of computers (for example, the uncollected money management device 201 and the shared terminal 204) in the information processing system 200. FIG.

(Calculation example of patient P's hospital visit interval, etc.)
Here, a calculation example of the patient P's hospital visit interval, the predicted number of remaining hospital visits, and the predicted remaining hospital visit period will be described. Here, the calculation timing of the patient P's hospital visit interval, the predicted number of remaining hospital visits, and the predicted remaining hospital visit period is assumed to be the accounting time when the patient P visits the hospital this time. In addition, the number of hospital visits for this time will be included in the number of remaining hospital visits.

First, assume that the billing classification is "0 (outpatient)". The patient P is assumed to be patient "P1 (name: Taro Fuji)".

In this case, the identification unit 1002, for example, refers to the billing DB 230 and identifies the disease name code "10" and the number of hospital visits "3" included in the billing information 500-3 of the patient P1. Next, the specifying unit 1002, for example, refers to the medical history DB 250 to specify the average number of hospital visits "5 times" and the average hospital visit period "160 days" corresponding to the disease name code "10" of the patient P1. Then, the identifying unit 1002 calculates the predicted remaining number of hospital visits for the patient P1, for example, using the following formula (1).

Predicted number of remaining hospital visits = average number of hospital visits - (number of hospital visits - 1) (1)

Here, the predicted number of remaining hospital visits for patient P1 is "3 times (=5-(3-1))".

Further, the specifying unit 1002 calculates the hospital visit interval of the patient P1, for example, using the following formula (2).

Hospital visit interval = average hospital visit period / (average number of hospital visits - 1) (2)

Here, the hospital visit interval for the patient P1 is "40 days (=160/(5-1))".

In addition, the identifying unit 1002 calculates the predicted remaining hospital visit period of the patient P1, for example, using the following formula (3).

Predicted remaining hospital visit period = average hospital visit period - hospital visit interval x (number of hospital visits - 1) (3)

Here, the predicted remaining hospital visit period for patient P1 is "80 days (=160−{40×(3−1)})".

Next, assume that the billing classification is "1 (hospitalization)". Also, the patient P is assumed to be a patient "P3 (name: Hanako Fuji)".

In this case, the identifying unit 1002, for example, refers to the billing DB 230 and identifies the disease name code "30" and the number of hospital visits after discharge "0" included in the billing information 500-7 of the patient P3. Next, the specifying unit 1002, for example, refers to the medical history DB 250 to specify the average number of hospital visits after discharge "4 times" and the average period of hospital visits after discharge "320 days" corresponding to the disease name code "30" of the patient P3. do. Then, the specifying unit 1002 calculates the predicted remaining number of hospital visits of the patient P3, for example, using the following formula (4).

Predicted number of remaining hospital visits = average number of hospital visits after discharge - (number of hospital visits after discharge - 1) (4)

Here, the predicted number of remaining hospital visits for the patient P3 is "5 times (=4-(0-1))".

Further, the specifying unit 1002 calculates the hospital visit interval of the patient P3 using, for example, the following formula (5).

Hospital visit interval = average hospital visit period after discharge / average number of hospital visits after discharge (5)

Here, the hospital visit interval for the patient P3 is "80 days (=320/4)".

In addition, the identifying unit 1002 calculates the predicted remaining hospital visit period of the patient P3, for example, using the following formula (6).

Predicted remaining hospital visit period = average hospital visit period after discharge - hospital visit interval x number of hospital visits after discharge (6)

Here, the predicted remaining hospital visit period for patient P3 is "320 days (=320-(80×0))".

(Screen example of accounts receivable management screen)
Next, screen examples of the accounts receivable management screen displayed on the shared terminal 204 will be described with reference to FIGS. 11 to 14. FIG.

FIG. 11 is an explanatory diagram (Part 1) showing an example of the partial delivery setting screen. In FIG. 11, an installment payment setting screen 1100 is an example of an accounts receivable management screen that displays an installment payment plan (prediction of the number of hospital visits) for the patient P1 (name: Taro Fuji) who has accrued an account. be. Here, it is assumed that the installment payment is started from the accounting time when the patient P1 visits the hospital this time.

The installment setting screen 1100 displays, for example, an initial payment amount of "16,940 yen", a recurring payment amount of "16,940 yen", the number of payments of "3", and a total accrued amount of "50,820 yen". . The initial payment amount and the round payment amount are calculated by dividing the total accrued amount "50,820 yen" by the number of payments "3". Note that the remainder of the division (fraction) may be incorporated into the initial payment amount, for example.

According to the installment setting screen 1100, it is possible to propose an installment plan for paying patient P1's uncollected money in installments for each hospital visit. On the partial payment setting screen 1100, when the user selects the number of hospital visits prediction button 1101 through an input operation using an input device (not shown), for example, a partial payment management screen 1200 as shown in FIG. 12 is displayed. On the installment management screen 1200, the details of the installment plan for paying patient P1's uncollected money in installments for each hospital visit can be confirmed.

In addition, when a doctor visit period prediction (monthly payment) button 1102 is selected on the installment payment setting screen 1100, an installment payment plan for monthly payment can be displayed. In addition, when the family name identification button 1103 is selected on the installment payment setting screen 1100, the screen changes to a screen (not shown) displaying the family situation of the patient P1. In this case, the accounts receivable management device 201 may create and output the installment payment plan for the patient P1 based on the family's hospital visit schedule, if there is a family member who is visiting the hospital.

Various warning messages are displayed in the message box 1110 . Warning messages include, for example, "Caution (noncompliance)", "Caution (out of range of times)", "Caution (out of range of amount)", "No name identification 0", "No name identification 1", and the like. "Caution (non-compliance)" indicates a past non-compliance caution. "Caution (out of count range)" indicates that the number of installments is out of the threshold. "Caution (Out of Amount Range)" indicates that the amount of accounts receivable (total amount of accounts receivable) is outside the threshold. "No name identification 0" indicates no family information. "No name identification 1" indicates no family during outpatient visits.

When changing a partial payment plan that has already been set, for example, the current partial payment plan is displayed in "current partial payment settings", and the changed partial payment plan is displayed in "current medical expenses added".

FIG. 12 is an explanatory diagram (Part 1) showing an example of the partial delivery management screen. In FIG. 12, an uncollected payment management screen 1200 is an uncollected money management screen that displays the contents of a partial payment plan (prediction of number of hospital visits) for paying an uncollected payment in installments for each hospital visit for patient P1 (name: Taro Fuji) who has an uncollected payment. An example.

The installment management screen 1200 displays, for example, the installment setting date, the number of installments, the initial amount, and the round-trip amount. In addition, the installment payment management screen 1200 displays the payment forecast date and payment amount for each installment of the uncollected amount for each hospital visit. The estimated payment date is set based on the installment payment set date (the current day), based on the average hospital visit interval and the number of installment payments when the patient P1 visits the hospital until the injury or illness (disease code: 10) is cured. The average hospital visit interval is, for example, the hospital visit interval (for example, 40 days) indicated by the patient's P1 visit schedule. Further, the average hospital visit interval may be calculated from the predicted remaining number of hospital visits and the predicted remaining hospital visit period of the patient P1. The number of installments is set based on the predicted number of remaining hospital visits.

Here, the first payment forecast date "2021.3.31" and the scheduled payment amount "16,940", the second payment forecast date "2021.5.10" and the scheduled payment amount "16,940", 3 The estimated payment date "2021.6.19" and the scheduled payment amount "16,940" are displayed. In addition, when each payment is actually made, the actual payment date and the actual payment amount are displayed.

According to the installment management screen 1200, for example, the person in charge of collection (staff of the medical affairs section) confirms the details of the installment plan for paying patient P1's uncollected amount in installments for each hospital visit, while confirming the details of the uncollected amount with patient P1. can be negotiated.

In addition, on the partial payment management screen 1200, the collection staff may be able to change the number of partial deliveries, the estimated payment date, the scheduled payment amount, etc., according to the request of the patient P1. For example, on the installment payment management screen 1200, when the user changes the initial amount and selects the recalculate button 1201, the recurring amount is updated based on the changed initial amount.

Further, when the return button 1202 is selected by the user's input operation on the partial delivery management screen 1200, the partial delivery setting screen 1100 shown in FIG. 11 is displayed. Various warning messages are displayed in the message box 1210 .

In addition, on the partial delivery management screen 1200, the partial delivery plan for the patient P1 can be confirmed by selecting the enter button 1203 by the user's input operation. When the partial payment plan for the patient P1 is confirmed, the contents stored in the partial payment DB 240 shown in FIG. 6 (for example, the partial payment information 600-1) are updated according to the details.

FIG. 13 is an explanatory diagram (part 2) showing an example of the partial delivery setting screen. In FIG. 13, an installment setting screen 1300 displays an installment plan (prediction of hospital visit period (monthly payment)) for periodically (monthly) installments of an uncollected amount for a patient P3 (name: Hanako Fuji) who has an uncollected amount. It is an example of a money management screen. Here, it is assumed that the installment payment is started from the accounting time when the patient P3 visits the hospital this time. Also, the monthly payment interval is set to "1 month" and the monthly payment reference date is set to "1 day".

The installment setting screen 1300 displays, for example, the initial payment amount of "64,380 yen", the round payment amount of "64,377 yen", the number of payments of "11", and the total uncollected amount of "708,150 yen". . The initial payment amount and the round payment amount are calculated by dividing the total accrued amount "708,150 yen" by the number of payments "11". The remainder of the split (fraction) is incorporated into the initial payment.

According to the installment setting screen 1300, it is possible to propose an installment plan for monthly installments of the uncollected money of the patient P3. On the installment payment setting screen 1300, when the hospital visit period prediction (monthly payment) button 1302 is selected by the user's input operation, for example, an installment payment management screen 1400 as shown in FIG. 14 is displayed. On the installment management screen 1400, it is possible to check the details of the installment plan for monthly installments of the uncollected money of the patient P3.

In addition, on the installment payment setting screen 1300, when a hospital visit number prediction button 1301 is selected, an installment payment plan for paying patient P3's uncollected money in installments for each hospital visit can be displayed. Further, when the family name identification button 1303 is selected on the installment payment setting screen 1300, the screen changes to a screen (not shown) displaying the family situation of the patient P3. In this case, the accounts receivable management device 201 may create and output the installment payment plan for the patient P3 based on the family's hospital visit schedule, if there is a family member who is visiting the hospital.

Various warning messages are displayed in the message box 1310 . Warning messages include, for example, "Caution (noncompliance)", "Caution (out of range of times)", "Caution (out of range of amount)", "No name identification 0", "No name identification 1", and the like.

FIG. 14 is an explanatory diagram (part 2) showing an example of the partial delivery management screen. In FIG. 14, an installment management screen 1400 displays the details of an installment plan (prediction of hospital visit period (monthly payment)) for monthly installments of an uncollected amount for patient P3 (name: Hanako Fuji) who has an uncollected amount. It is an example of a management screen.

The installment management screen 1400 displays, for example, installment setting date, interval (month), number of installments, initial amount, round-trip amount, and payment reference date. The installment payment setting date corresponds to the payment start date. In addition, the installment management screen 1400 displays the estimated payment date and the expected amount of payment for each installment of the uncollected amount on a monthly basis. The estimated payment date is based on the payment start date (current day), and is set based on the remaining number of months of hospital visits according to the estimated remaining hospital visit period in the case of patient P3 going to the hospital until the injury or illness (disease code: 30) is cured. be.

According to the installment management screen 1400, for example, the person in charge of collection (staff of the medical affairs section) confirms the detailed content of the installment plan for paying the uncollected amount of patient P3 in installments on a monthly basis. can be negotiated.

On the partial payment management screen 1400, the person in charge of collection can change the number of partial deliveries, the payment forecast date, the scheduled payment amount, etc., according to the request of the patient P3. Here, it is assumed that the payment reference date is changed to "26th" at the request of the patient and the recalculation button 1401 is selected.

In this case, the second and subsequent payment forecast dates are set based on the changed payment reference date. As a result, for example, the first payment forecast date "2021.3.31" and the scheduled payment amount "64,380", the second payment forecast date "2021.4.26" and the scheduled payment amount "64,377" , the third payment forecast date "2021.5.26" and the scheduled payment amount "64,377", the fourth payment forecast date "2021.6.26" and the scheduled payment amount "64,377", the fifth The estimated payment date “2021.7.26” and the scheduled payment amount “64,377” are displayed.

Further, when the return button 1402 is selected by the user's input operation on the partial delivery management screen 1400, the partial delivery setting screen 1300 shown in FIG. 13 is displayed. Various warning messages are displayed in the message box 1410 .

In addition, on the partial delivery management screen 1400, when the enter button 1403 is selected by the user's input operation, the partial delivery plan for the patient P3 can be confirmed. When the partial payment plan for patient P3 is confirmed, the contents stored in the partial payment DB 240 shown in FIG. 6 (for example, the partial payment information 600-2) are updated according to the details.

(Accounts Receivable Management Processing Procedure of Accounts Receivable Management Device 201)
Next, an uncollected money management processing procedure of the uncollected money management device 201 will be described with reference to FIG. 15 .

FIG. 15 is a flowchart showing an example of an uncollected money management processing procedure of the uncollected money management device 201 . In the flowchart of FIG. 15, first, the uncollected money management device 201 determines whether or not a partial payment setting request has been received from the shared terminal 204 (step S1501). Here, the uncollected money management apparatus 201 waits for receiving a partial payment setting request from the shared terminal 204 (step S1501: No).

Then, when the uncollected money management apparatus 201 receives a partial payment setting request from the shared terminal 204 (step S1501: Yes), it executes a partial payment possibility determination process (step S1502). The installment availability determination process is a process for determining whether payment in installments is available for the patient P for whom an uncollected amount has occurred. A specific processing procedure of the installment availability determination processing will be described later with reference to FIGS. 16 and 17. FIG.

Next, the uncollected money management apparatus 201 executes a partial payment plan creation process (step S1503). The divisional payment plan creation process is a process of creating a divisional payment plan for the patient P who has an uncollected amount. A specific processing procedure of the distribution plan creation processing will be described later with reference to FIG. 18 .

Then, the uncollected money management device 201 outputs the prepared installment payment plan for the patient P (step S1504), and ends the series of processing according to this flowchart. As a result, it is possible to output an installment plan for paying the uncollected money in installments for the patient P for whom the uncollected money is generated.

16 and 17, a specific processing procedure of the divisional delivery availability determination processing in step S1502 will be described.

16 and 17 are flowcharts showing an example of a specific processing procedure of the divisional delivery possibility determination processing. In the flowchart of FIG. 16, first, the uncollected money management device 201 determines whether or not the patient P's uncollected amount is outside the threshold range (step S1601). The uncollected amount of the patient P is calculated, for example, by aggregating the overdue amount of the billing information corresponding to the patient number included in the installment payment setting request. The threshold range is set to, for example, a range of 1,000 yen or more and less than 1 million yen.

Here, if the uncollected amount is out of the threshold range (step S1601: Yes), the uncollected amount management device 201 outputs an installment payment impossibility (maximum amount) message (step S1602), and executes a series of processing according to this flowchart. finish. The installment impossibility (maximum amount) message is an error message to the effect that installment payment is not possible because the uncollected amount is too small or too large. The installment impossibility (maximum amount) message is output, for example, to the message box 905 of the accounts receivable management screen 900 as shown in FIG. As a result, it is possible to prevent the partial payment plan from being proposed to the patient P whose uncollected amount is too small or too large.

On the other hand, if the uncollected amount is within the threshold range (step S1601: No), the uncollected money management device 201 determines whether the patient P's caution code is greater than 10 (step S1603). The attention code of the patient P is specified, for example, from patient information corresponding to the patient number included in the installment setting request.

Here, if the caution code is greater than 10 (step S1603: Yes), the accounts receivable management device 201 outputs a non-payment (management) message (step S1604), and ends the series of processing according to this flowchart. The non-partitionable (management) message is an error message to the effect that the participatory payment is not possible due to the person requiring attention. The non-payment (management) message is output, for example, to the message box 905 of the accounts receivable management screen 900 as shown in FIG. As a result, it is possible to prevent the partial payment plan from being proposed to the patient P who maliciously causes arrears.

On the other hand, if the caution code is 10 or less (step S1603: No), the uncollected money management device 201 determines whether or not the installment payment performance of the patient P is 20% or less (step S1605). The installment payment record of the patient P is identified, for example, from billing information corresponding to the patient number included in the installment payment setting request. More specifically, for example, the accounts receivable management device 201 refers to the billing DB 230 and, out of the total number of pieces of billing information corresponding to the patient number included in the installment payment setting request, billing information with a delinquent amount of 0 yen (delayed amount). By calculating the ratio of the number of code: 0), the installment payment performance of the patient P can be obtained.

Here, if the installment payment record is 20% or less (step S1605: Yes), the accounts receivable management device 201 outputs a warning (nonfulfillment) message (step S1606). Caution (non-compliance) messages are warning messages that call attention to high delinquency rates. The caution (non-compliance) message is output, for example, to the message box 905 of the accounts receivable management screen 900 as shown in FIG. As a result, attention can be urged when proposing the installment plan to the patient P who frequently fails to fulfill promises to pay.

Next, the uncollected money management device 201 determines whether or not a confirmation operation has been performed for the attention (non-compliance) message (step S1607). A confirmation operation for a caution (non-compliance) message is performed, for example, by selecting a confirmation button 906 on the uncollected money management screen 900 as shown in FIG.

Here, the uncollected money management device 201 waits for a confirmation operation for the attention (nonfulfillment) message (step S1607: No). Then, if a confirmation operation has been performed for the caution (nonfulfillment) message (step S1607: Yes), the uncollected money management apparatus 201 proceeds to step S1608.

Also, in step S1605, if the installment payment record is greater than 20% (step S1605: No), the uncollected money management device 201 refers to the billing DB 230 and refers to the billing information corresponding to the patient number included in the installment setting request. Among them, billing information for which uncollected money is generated is acquired (step S1608).

Next, the uncollected money management device 201 refers to the medical history DB 250, specifies the hospital visit schedule of the patient P based on the acquired billing information (step S1609), and proceeds to step S1701 shown in FIG. Specifically, for example, the uncollected money management device 201 calculates, as the patient's P visit schedule, the patient's P visit interval, the predicted number of remaining hospital visits, and the predicted remaining hospital visit period.

In the flowchart of FIG. 17, the uncollected money management device 201 first determines whether or not the predicted remaining number of hospital visits indicated by the hospital visit schedule of the patient P is outside the threshold range (step S1701). The threshold range is set, for example, to a range of 2 times or more and less than 100 times.

Here, if the predicted remaining number of hospital visits is out of the threshold range (step S1701: Yes), the uncollected money management device 201 outputs a warning (out of number of visits range) message (step S1702). The caution (out of frequency range) message is a warning message that calls attention to the predicted number of remaining hospital visits that is too small or too large. The caution (number of times out of range) message is output, for example, to the message box 905 of the uncollected money management screen 900 as shown in FIG. As a result, attention can be urged when proposing a partial payment plan to the patient P whose number of predicted remaining hospital visits is too small or too large.

Next, the uncollected money management device 201 determines whether or not a confirmation operation has been performed for the caution (out of range of number of times) message (step S1703). The confirmation operation for caution (out of range of times) is performed by selecting the confirmation button 906 on the uncollected money management screen 900 as shown in FIG. 9, for example.

Here, the uncollected money management device 201 waits for confirmation operation for the caution (out of number range) message (step S1703: No). Then, if a confirmation operation has been performed for the attention (out of frequency range) message (step S1703: Yes), the uncollected money management apparatus 201 proceeds to step S1704.

In step S1701, if the predicted remaining number of hospital visits is within the threshold range (step S1701: No), the uncollected money management device 201 determines that the predicted remaining hospital visit period indicated by the patient P's scheduled hospital visits is outside the threshold range. It is determined whether or not there is (step S1704). The threshold range is set to a range such as two weeks or more and less than two years, for example.

Here, if the estimated remaining hospital visit period is outside the threshold range (step S1704: Yes), the uncollected money management device 201 outputs a warning (out of period range) message (step S1705). The caution (out of period range) message is a warning message that calls attention because the predicted remaining hospital visit period is short or long. The caution (period out of range) message is output, for example, to the message box 905 of the accounts receivable management screen 900 as shown in FIG. As a result, attention can be urged when proposing a partial payment plan to the patient P for whom the estimated remaining period of hospital visits is too short or too long.

Next, the uncollected money management device 201 determines whether or not a confirmation operation has been performed with respect to the caution (out of period range) message (step S1706). The confirmation operation for caution (outside the period range) is performed by selecting the confirmation button 906 on the uncollected money management screen 900 as shown in FIG. 9, for example.

Here, the uncollected money management apparatus 201 waits for confirmation operation for the caution (out of period range) message (step S1706: No). Then, if a confirmation operation has been performed on the attention (outside the period range) message (step S1706: Yes), the uncollected money management apparatus 201 returns to the step that called the installment payment possibility determination process.

Also, in step S1704, if the predicted remaining period of hospital visits is within the threshold range (step S1704: No), the uncollected money management device 201 returns to the step that called the partial payment possibility determination process.

Next, using FIG. 18, a specific processing procedure of the partial delivery plan creation processing in step S1503 will be described.

FIG. 18 is a flow chart showing an example of a specific processing procedure of the partial delivery plan creation processing. In the flowchart of FIG. 18, first, the uncollected money management device 201 determines whether or not the hospital visit interval indicated by the hospital visit schedule of the specified patient P is outside the threshold range (step S1801). The threshold range corresponds to, for example, a range greater than the second threshold Th2 and less than the first threshold Th1.

Here, if the hospital visit interval is within the threshold range (step S1801: No), the uncollected money management device 201 divides the uncollected money (total uncollected amount) of the patient P by the predicted remaining number of hospital visits, and divides the payment amount (in installments). amount) is calculated (step S1802). Then, if there is a remainder (fraction) of the division, the uncollected money management device 201 applies the remainder to the initial payment amount (step S1803).

Next, the accounts receivable management device 201 identifies the scheduled payment date based on the interval of hospital visits of the patient P and the predicted remaining number of hospital visits, with the installment payment set date (for example, the current day) as a reference (step S1804). Then, based on the calculated payment amount and the specified scheduled payment date, the accounts receivable management device 201 creates an installment plan for paying the accounts receivable in installments for each hospital visit (step S1805), and calls the installment plan creation process. return to the previous step.

In addition, in step S1801, if the hospital visit interval is outside the threshold range (step S1801: Yes), the uncollected money management device 201 calculates the remaining number of months of hospital visits based on the predicted remaining hospital visit period indicated by the hospital visit schedule of the patient P. Calculate (step S1806). Next, the uncollected money management apparatus 201 divides the uncollected money (total uncollected amount) of the patient P by the remaining number of months of hospital visits to calculate the payment amount (dividual payment amount) (step S1807).

Then, if there is a remainder (fraction) of the division, the uncollected money management device 201 applies the remainder to the initial payment amount (step S1808). Next, the accounts receivable management device 201 specifies the scheduled payment date based on the payment reference date (eg, one day) and the remaining number of months of hospital visits, using the installment payment set date (eg, the current day) as a reference (step S1809). ).

Based on the calculated payment amount and the specified scheduled payment date, the accounts receivable management device 201 creates a monthly installment payment plan for the accounts receivable (step S1810), and calls the installment plan creation process. return to the previous step. Thereby, according to the hospital visit interval of the patient P, the installment payment plan which pays uncollected money in installments can be created.

As described above, according to the accounts receivable management apparatus 201 according to the embodiment, the medical information of the patient P for whom the accounts receivable are generated is acquired, and the hospital visit schedule of the patient P is specified based on the acquired medical information. , it is possible to determine whether or not the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of a first threshold value Th1 or more or a second threshold value Th2 or less. The hospital visit schedule of the patient P is, for example, a hospital visit schedule until the patient P's illness (injury or illness) is cured. Then, according to the accounts receivable management device 201, when the criteria are met, it is possible to create a partial payment plan for periodically paying accounts receivable regardless of the hospital visit interval, and to output the created partial payment plan. Specifically, for example, the uncollected money management device 201 divides the uncollected money into the number of months of remaining hospital visits based on the predicted remaining hospital visit period indicated by the scheduled hospital visit of the patient P, or the number of months of remaining installment payments based on a preset minute delivery period. Create an installment payment plan to pay the receivables in installments at regular intervals.

Thereby, the uncollected money management apparatus 201 can create a suitable partial payment plan for the patient P. FIG. For example, if the interval between hospital visits is too long, there is a risk that the patient will become less conscious of payment or forget to promise to pay. Therefore, for example, when the hospital visit interval indicated by the hospital visit schedule of the patient P is equal to or greater than the first threshold value Th1, the uncollected money management device 201 does not plan to pay the uncollected money in installments for each hospital visit, but a monthly payment plan. can stand. On the other hand, if the interval between hospital visits is too short, the number of payments will increase, and the burden on the patient P will increase, as well as the time and effort of staff such as receptionists and accounting staff. For this reason, for example, when the visit interval indicated by the hospital visit schedule of the patient P is equal to or less than the second threshold value Th2, the uncollected money management device 201 does not plan to pay the uncollected money in installments for each hospital visit, but a monthly payment plan. can stand.

In addition, according to the uncollected money management device 201, when the criteria are not met, a partial payment plan for paying the uncollected money in installments for each hospital visit can be created according to the hospital visit schedule of the patient P, and the created partial payment plan can be output. . Specifically, for example, the uncollected money management device 201 divides the uncollected money by the predicted remaining number of hospital visits indicated by the hospital visit schedule of the patient P, thereby creating a divided payment plan for paying the uncollected money in installments for each hospital visit.

As a result, the uncollected money management device 201 can make a plan to pay the uncollected money in installments for each hospital visit if the interval between hospital visits is neither too long nor too short. According to this installment payment plan, the patient P can pay the uncollected amount at the time of hospital visit, so that the trouble of visiting a medical institution separately for payment can be saved.

Further, according to the uncollected money management device 201, based on the attribute information (for example, attention code) of the patient P, it is determined whether installment payment is possible for the patient P, and when it is determined that the patient P cannot be paid in installments, A message to the effect that partial payment is impossible for patient P can be output without creating a partial payment plan for partial payment.

As a result, the uncollected money management apparatus 201 can prevent proposing a partial payment plan to a patient P who is not in financial difficulty and who causes malicious uncollected payments.

Further, according to the uncollected money management device 201, it is determined whether or not the predicted remaining hospital visit period indicated by the hospital visit schedule of the patient P is within the first range, and if the predicted remaining hospital visit period is outside the first range, It is possible to output warning information according to the predicted remaining period of hospital visits.

As a result, when the uncollected money management device 201 creates an installment payment plan for the patient P, if the remaining hospital visit period of the patient P is too long or too short, it is possible that it is not preferable to divide the uncollected money into installments. Therefore, it is possible to call the attention of the person in charge of collection.

Further, according to the uncollected money management device 201, it is determined whether or not the predicted remaining number of hospital visits indicated by the hospital visit schedule of the patient P is within the second range, and if the predicted remaining number of hospital visits is outside the second range, It is possible to output warning information according to the estimated number of remaining hospital visits.

As a result, when the uncollected money management device 201 creates an installment payment plan for the patient P, if the number of remaining hospital visits for the patient P is too large or too small, it is possible that it is not preferable to divide the uncollected money into installments. Therefore, it is possible to call the attention of the person in charge of collection.

Further, according to the accounts receivable management device 201, it is determined whether or not the number of installments in the created installment plan is within a predetermined range. Warning information can be output according to the number of installments.

As a result, when the uncollected money management device 201 proposes an installment payment plan for the patient P, if the number of installments is too large or too small, the burden on the patient P and staff may increase. It is possible to call attention to persons, etc.

In addition, according to the uncollected money management device 201, the uncollected money is paid in installments periodically regardless of the hospital visit interval indicated by the hospital visit schedule of the patient P, and the uncollected money is paid in installments for each hospital visit according to the patient P's hospital visit schedule. Even when a partial payment plan is created and the standard is satisfied, the created partial payment plan for periodically paying the uncollected money in installments and the created installment plan for paying the uncollected money in installments for each hospital visit can be output.

As a result, the person in charge of collection or the like can negotiate with the patient P using both the installment plan for paying the uncollected money in installments on a regular basis and the installment plan for paying the uncollected money in installments for each hospital visit.

In addition, according to the uncollected money management device 201, the uncollected money is paid in installments periodically regardless of the hospital visit interval indicated by the hospital visit schedule of the patient P, and the uncollected money is paid in installments for each hospital visit according to the patient P's hospital visit schedule. Even if the standard is not satisfied, the created installment plan for paying the uncollected money in installments for each hospital visit and the created installment plan for periodically paying the uncollected money in installments can be output.

As a result, the person in charge of collection or the like can negotiate with the patient P using both the installment plan for paying the uncollected money in installments on a regular basis and the installment plan for paying the uncollected money in installments for each hospital visit.

From these, according to the uncollected money management apparatus 201 (information processing apparatus 101) according to the embodiment, by creating a proper installment plan for the patient P, the patient P's awareness of payment is strengthened, and the uncollected money can lead to the collection of In addition, according to the uncollected money management device 201 (information processing device 101), by automatically creating an installment payment plan, it is possible to reduce the burden and mistakes of the person in charge of collection at the medical institution, and reduce the negotiation time with the patient P. can also be reduced. In addition, the patient P can also receive a prompt proposal for a proper partial payment plan based on a certain basis. Furthermore, according to the uncollected money management device 201 (information processing device 101), it is possible to respond to a condition change according to the request of the patient P, so that it is possible to quickly select an optimal divided payment plan. In addition, according to the accounts receivable management device 201 (information processing device 101), guidance to the family of the patient P, reminder, and securing an opportunity to pay on behalf of the patient prevent the decline in willingness to pay due to an unreasonable plan of the patient. be able to.

The method for managing uncollected money described in the present embodiment can be realized by executing a prepared program on a computer such as a personal computer or a workstation. This uncollected money management program is recorded in a computer-readable recording medium such as a hard disk, flexible disk, CD-ROM, DVD, USB memory, etc., and executed by being read from the recording medium by a computer. Also, the uncollected money management program may be distributed via a network such as the Internet.

In addition, the receivables management apparatus 201 (information processing apparatus 101) described in the present embodiment can be implemented by application-specific ICs such as standard cells and structured ASICs (Application Specific Integrated Circuits) and PLDs (Programmable Logic Devices) such as FPGAs. can also be realized.

Further, the following additional remarks are disclosed with respect to the above-described embodiment.

(Appendix 1) Acquire medical information of patients with uncollected money,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
An uncollected money management program characterized by causing a computer to execute processing.

(Appendix 2) If the criteria are not met, create a plan to pay the receivables in installments for each hospital visit according to the hospital visit schedule, and output the created plan.
The uncollected money management program according to appendix 1, characterized by causing the computer to execute processing.

(Appendix 3) Based on the attribute information of the patient, determine whether the patient can be paid in installments,
When it is determined that the patient cannot be paid in installments, a message is output to the effect that the patient cannot be paid in installments without creating a plan for paying the uncollected money in installments.
3. An uncollected money management program according to appendix 1 or 2, characterized in that the processing is executed by the computer.

(Appendix 4) The accrued money management program according to any one of Appendices 1 to 3, wherein the hospital visit schedule is a hospital visit schedule until the patient's injury or disease is cured.

(Appendix 5) Determining whether the predicted remaining hospital visit period indicated by the hospital visit schedule is within the first range,
If the predicted remaining hospital visit period is outside the first range, output warning information according to the predicted remaining hospital visit period;
The uncollected money management program according to any one of appendices 1 to 4, characterized in that the processing is executed by the computer.

(Appendix 6) Determining whether the predicted remaining number of hospital visits indicated by the hospital visit schedule is within a second range,
If the predicted remaining number of hospital visits is outside the second range, output warning information according to the predicted remaining number of hospital visits;
The uncollected money management program according to any one of appendices 1 to 5, characterized in that the processing is executed by the computer.

(Appendix 7) Determine whether the number of installments in the created plan is within a predetermined range,
When the number of installments is out of the predetermined range, outputting warning information according to the number of installments when outputting the plan;
The uncollected money management program according to appendix 1, characterized by causing the computer to execute processing.

(Appendix 8) The process to create is
When the criteria are met, the uncollected money is divided by the remaining months of hospital visits based on the predicted remaining hospital visit period indicated by the outpatient schedule, or the remaining installment months based on the preset minute delivery period. The uncollected money management program according to Supplementary Note 1, wherein a plan for periodically paying in installments is created.

(Appendix 9) The process to create is
The method according to appendix 2, wherein, if the criteria are not met, the unpaid money is divided by the estimated number of remaining hospital visits indicated by the hospital visit schedule, thereby creating a plan for paying the unpaid money in installments for each hospital visit. accounts receivable management program.

(Appendix 10) Create a plan to pay the receivables periodically regardless of the hospital visit interval and a plan to pay the receivables in installments for each hospital visit according to the hospital visit schedule,
Even if the criteria are met, outputting a plan for periodically paying the receivables created and a plan for paying the receivables created in installments for each hospital visit,
The uncollected money management program according to appendix 1, characterized by causing the computer to execute processing.

(Additional note 11) Acquire medical information of the patient for whom uncollected money has occurred,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
A method of managing accounts receivable, characterized in that the processing is executed by a computer.

(Appendix 12) Acquiring medical information of patients for whom receivables have occurred,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
An information processing apparatus comprising a control unit that executes processing.

101 Information Processing Device 102,P Patient 110 Medical Information 130 Monthly Payment Plan 200 Information Processing System 201 Accounts Receivable Management Device 202 Electronic Chart System 203 Medical Accounting System 204 Shared Terminal 210 Network 220 Patient DB
230 Billing DB
240 installment DB
250 Medical history DB
260 Electronic medical record DB
270 Medical Accounting DB
300 Bus 301 CPU
302 memory 303 disk drive 304 disk 305 communication I/F
306 portable recording medium I/F
307 portable recording medium 800 electronic medical record screen 900 uncollected money management screen 1001 acquisition unit 1002 identification unit 1003 determination unit 1004 creation unit 1005 output unit 1100, 1300 installment setting screen 1200, 1400 installment management screen

Claims (8)

Acquiring medical information of patients with uncollected money,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
An uncollected money management program characterized by causing a computer to execute processing. If the criteria are not met, create a plan for paying the receivables in installments for each hospital visit according to the hospital visit schedule, and output the created plan;
2. The uncollected money management program according to claim 1, which causes the computer to execute processing. Based on the attribute information of the patient, determine whether the patient can be paid in installments,
When it is determined that the patient cannot be paid in installments, a message is output to the effect that the patient cannot be paid in installments without creating a plan for paying the uncollected money in installments.
3. The uncollected money management program according to claim 1 or 2, wherein the processing is executed by said computer. The uncollected money management program according to any one of claims 1 to 3, wherein the hospital visit schedule is a hospital visit schedule until the patient's injury or disease is cured. Determining whether the predicted remaining hospital visit period indicated by the hospital visit schedule is within a first range,
If the predicted remaining hospital visit period is outside the first range, output warning information according to the predicted remaining hospital visit period;
5. The uncollected money management program according to any one of claims 1 to 4, wherein the processing is executed by the computer. Determining whether the predicted remaining number of hospital visits indicated by the hospital visit schedule is within a second range,
If the predicted remaining number of hospital visits is outside the second range, output warning information according to the predicted remaining number of hospital visits;
6. The uncollected money management program according to any one of claims 1 to 5, wherein the processing is executed by the computer. Acquiring medical information of patients with uncollected money,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
A method of managing accounts receivable, characterized in that the processing is executed by a computer. Acquiring medical information of patients with uncollected money,
Identifying the patient's hospital visit schedule based on the acquired medical information,
Determining whether the hospital visit interval indicated by the specified hospital visit schedule satisfies a criterion of not less than a first threshold or not more than a second threshold different from the first threshold,
If the criteria are met, create a plan to periodically pay the receivables in installments regardless of the hospital visit interval, and output the created plan;
An information processing apparatus comprising a control unit that executes processing.

Images