Program, system, and method

Abstract

To provide a program and the like that can integrate two or more pieces of medical treatment accounting information into one piece of information.SOLUTION: According to an aspect of the present invention, a program is provided. The program causes a computer managing reservations of medical treatment on patients to execute link processing of associating two or more reservations for medical treatment on the same patient on the basis of a user operation, and accounting output processing of outputting accounting information according to a result of the medical treatment conducted on the basis of the medical treatment reservations. The accounting output processing is processing of, when a medical treatment reservation requiring accounting is a medical treatment reservation subjected to the link processing, outputting accounting information in which respective times of medical treatment conducted on the basis of two or more medical treatment reservations associated with the medical treatment reservation are integrated into one.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a program, a system, and a method.

Background Art

[0002] Patent Document 1 discloses a technique for automatically calculating and paying medical treatment fees based on medical treatment guidance ticket data read from an IC card and causing a patient to pay the medical treatment fees.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When a patient receives medical treatment multiple times, it is troublesome for both the patient and the medical institution to perform accounting for each medical treatment. In view of the above circumstances, the present invention aims to provide a program or the like that can integrate the accounting information of two or more medical treatments into one.

Means for Solving the Problems

[0005] According to one aspect of the present invention, a program is provided. This program causes a computer that manages a patient's medical treatment reservation to execute a link process for associating two or more medical treatment reservations of the same patient based on a user operation, and an accounting output process for outputting accounting information according to the result of the medical treatment performed based on the medical treatment reservation. When the medical treatment reservation for which accounting is to be performed is the medical treatment reservation for which the link process has been performed, the accounting output process is a process of outputting integrated accounting information for the medical treatments performed based on two or more medical treatment reservations associated with the medical treatment reservation.

[0006] According to such an aspect, accounting information of two or more medical treatments can be grouped into one.

Brief Description of Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

BEST MODE FOR CARRYING OUT THE INVENTION

[0008] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Various characteristic matters shown in the embodiments shown below can be combined with each other.

[0009] Incidentally, the program for realizing the software appearing in the present embodiment may be provided as a non-transitory computer-readable medium readable by a computer, may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer to realize its function on a client terminal (so-called cloud computing).

[0010] Also, in the present embodiment, the “section” may include, for example, a combination of hardware resources implemented by a circuit in a broad sense and information processing of software that can be specifically realized by these hardware resources. Also, in the present embodiment, various types of information are handled, and these information are represented, for example, by physical values of signal values representing voltage and current, the high and low of signal values as a set of binary bits composed of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be executed on a circuit in a broad sense.

[0011] Also, a circuit in a broad sense is a circuit realized by appropriately combining at least a circuit, circuitry, a processor, a memory, and the like. That is, it includes an application specific integrated circuit (ASIC), programmable logic devices (for example, a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), and the like.

[0012] 1. Hardware Configuration In this section, the hardware configuration of the medical treatment management system according to the present embodiment will be described.

[0013] FIG. 1 is a diagram showing the overall configuration of the medical treatment management system 1. In FIG. 1, an overview of each device included in the medical treatment management system 1, users who use each device, information processed in each device, etc. is shown. Each overview will be described as needed with reference to other figures.

[0014] The medical treatment management system 1 is an information processing system that manages the medical treatment of patients in a medical institution. Medical treatment refers to one or both of examination and treatment of patients, and is performed by a doctor. The medical treatment management system 1 includes a communication line 2, a server device 10, a patient terminal 20, a reception terminal 30, and a doctor terminal 40. Note that the medical treatment management system 1 may include two or more of the patient terminal 20, the reception terminal 30, and the doctor terminal 40 each, but only one is shown in FIG. 1.

[0015] The communication line 2 includes the Internet, etc., and mediates the exchange of data between devices connected to a private line. Each device included in the medical treatment management system 1 is connected to the communication line 2 either wired or wirelessly. The patient terminal 20 is a terminal used by a patient (including those who are about to receive a first medical examination). The reception terminal 30 is a terminal used by, for example, a reception staff member (also simply referred to as "reception") of a medical institution.

[0016] The doctor terminal 40 is a terminal used by, for example, a doctor who performs medical treatment on a patient. Each terminal is an information processing terminal such as a desktop personal computer, a notebook personal computer, a tablet terminal, or a smartphone. The server device 10 is an information processing device that executes processing related to medical treatment reservation, medical records, accounting, etc. Further, the server device 10 controls the display of system screens by the patient terminal 20, the reception terminal 30, and the doctor terminal 40. The system screens include a patient-oriented screen and a medical institution-oriented screen.

[0017] FIG. 2 is a diagram showing the hardware configuration of the server device 10. The server device 10 includes a control unit 11, a storage unit 12, a communication unit 13, and a bus 14. The bus 14 electrically connects each part included in the server device 10.

[0018] (Control Unit 11) The control unit 11 is, for example, a Central Processing Unit (CPU) not shown in the figure. The control unit 11 is a computer that realizes various functions related to the medical treatment management system 1 by reading a predetermined program stored in the storage unit 12. That is, the information processing by software stored in the storage unit 12 is specifically realized by the control unit 11, which is an example of hardware, and can be executed as each functional unit included in the control unit 11. These will be described in more detail in the next section. Note that the control unit 11 is not limited to being single, and may be implemented to have a plurality of control units 11 for each function, or a combination thereof may also be used.

[0019] (Storage Unit 12) The storage unit 12 stores various information defined by the foregoing description. This can be implemented, for example, as a storage device such as a Solid State Drive (SSD) that stores various programs and the like related to the medical treatment management system 1 executed by the control unit 11, or as a memory such as a Random Access Memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to the calculation of the program. The storage unit 12 stores various programs, variables, and the like related to the medical treatment management system 1 executed by the control unit 11.

[0020] (Communication Unit 13) The communication unit 13 is configured to be able to transmit various electrical signals from the server device 10 to external components. Further, the communication unit 13 is configured to be able to receive various electrical signals from external components to the server device 10. More preferably, the communication unit 13 has a network communication function, and thereby, various information may be communicatively implemented between the server device 10 and external devices via the communication line 2.

[0021] FIG. 3 is a diagram showing the hardware configuration of the patient terminal 20. The patient terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a bus 26. The bus 26 electrically connects each part included in the patient terminal 20. The control unit 21, the storage unit 22, and the communication unit 23 may have different specifications, models, etc. from the control unit 11, the storage unit 12, and the communication unit 13 shown in FIG. 2, but are the same hardware.

[0022] (Input unit 24) The input unit 24 has one or more input interfaces such as keys, buttons, touchscreens, and mice, and receives inputs from the user. (Output unit 25) The output unit 25 has output devices such as a display and a speaker, and displays visual information generated in a manner visible to the user, such as screens, images, icons, text, etc. on the display surface, and outputs sounds including voices.

[0023] The reception terminal 30 and the doctor terminal 40 have the same hardware configuration as the patient terminal 20. Regarding the reception terminal 30, only the control unit 31 will be described with a different reference numeral from the control unit 21 of the patient terminal 20. The doctor terminal 40 has the same hardware configuration as the patient terminal 20. Regarding the doctor terminal 40, only the control unit 41 will be described with a different reference numeral from the control unit 21 of the patient terminal 20.

[0024] 2. Information processing In this section, in this embodiment, information processing executed by the medical treatment management system 1 (specifically, the processors provided in the server device 10, the patient terminal 20, the reception terminal 30, and the doctor terminal 40) will be described. The medical treatment management system 1 executes medical treatment management processing for managing medical treatment for patients. The medical treatment management processing includes reservation processing, medical record processing, accounting processing, and the like.

[0025] FIG. 4 is an activity diagram showing an example of reservation processing. The activities shown after FIG. 4 are started when the patient, the reception staff, and the doctor log in to the medical treatment management system 1 by operating the terminals they each use. In the medical treatment management system 1, it is assumed that authentication information has been issued in advance to the users (patients, reception staff, doctors) of each terminal. When a patient logs in for the first time, the server device 10 accepts the input of the patient's basic information (such as name and address) and issues authentication information for the patient. The server device 10 displays, as a system screen, a screen designed for the user (patient, reception staff, doctor) of each terminal indicated by the authentication information input at the time of login.

[0026] In A11, the server device 10 executes, as display processing, a process of generating screen data indicating the system screen and transmitting the generated screen data to each terminal. The patient terminal 20 displays, in A12, the patient-oriented screen indicated by the transmitted screen data. The reception terminal 30 displays, in A13, the reception-oriented screen indicated by the transmitted screen data. The users (patients and reception) of each terminal use the medical treatment management system 1 by displaying the system screen at the necessary timing.

[0027] The screen data is, for example, an HTML (Hyper Text Markup Language) file, an image file, or the like. In that case, a web page indicating the system screen is displayed on each terminal. In addition, when an application program for using the medical treatment management system 1 is introduced in each terminal, the server device 10 may generate and transmit the display data of the application as the screen data.

[0028] Next, information processing when a patient makes a medical appointment will be described. When making a medical appointment, the patient performs an operation to display a screen for making a medical appointment and conducting a medical interview, for example, on the patient-oriented screen displayed on the patient terminal 20. When this operation is performed on the patient terminal 20, the server device 10 causes the patient terminal 20 to display a reservation screen for the patient. In the present embodiment, the reservation screen for the patient includes a first screen and a second screen for reservation.

[0029] FIG. 5 is a diagram showing an example of the first screen for patient reservation. On the first screen C1 for patient reservation shown in FIG. 5, reservation icons E1 to E6 prepared for each medical menu are displayed. For example, the reservation icon E1 is an image including a medical menu of "Treatment F1", the time required for examination, etc. being "60 minutes", the medical treatment form being "face-to-face", a text indicating the outline of the medical treatment, and a button B11 to proceed with the reservation.

[0030] Also, the reservation icons E2 to E6 are similar images for each medical menu of "Treatment F2", "Treatment F3", "Treatment F4", "Consultation G1", and "Consultation G2", respectively. The patient terminal 20 accepts, at A21, an operation on the button B11 to proceed with the reservation of the reservation icon of the medical menu that the patient wishes to receive as an operation for making a medical appointment. When an operation on the button B11 to proceed with the reservation is accepted, the server device 10 causes the patient terminal 20 to display a second screen for patient reservation.

[0031] FIG. 6 is a diagram showing an example of the second screen for patient reservation. On the second screen C2 for patient reservation shown in FIG. 6, a display column E21 for the medical menu, an input column E22 for the reservation date and time, an input column E23 for the medical treatment form, an input column E24 for the medical interview information, a patient-oriented schedule table L11, a reservation confirmation button B21, a reservation change button B22, and a cancel button B23 are displayed. In the display column E21, the medical menu selected on the first screen C1 shown in FIG. 5 (in the example of FIG. 6, "Consultation G2") is displayed.

[0032] The server device 10 refers to the medical information database described later and displays a patient schedule table L11 indicating the time slots available for reservation by medical staff. In this embodiment, the server device 10 indicates, as the available time slots, the date and time when at least one medical staff member can make a reservation and at least one facility can be reserved, in a white rectangular area, and indicates, as the unavailable time slots, the time slots when no medical staff member can make a reservation or no facility can be reserved, in a hatched area, and displays the patient schedule table L11. That is, when a reservation is made from the patient terminal 20, the server device 10 displays the schedule table L11 that allows reservation from the available frames based on the schedules of both medical staff and facilities.

[0033] The patient inputs the date and time he / she wishes to reserve in the input field E22 (in the example of FIG. 6, "12:00 - 12:30" of "mm / dd") while looking at the patient schedule table L11. This input may also be made by an operation of specifying the date and time to be reserved in the patient schedule table L11. The server device 10 highlights (displayed surrounded by a thick line in the example of FIG. 6) the reservation area H21, which is the area corresponding to the input reservation date and time, in the schedule table L11.

[0034] Also, when the patient can select either in-person or online as the medical treatment format, the patient inputs the selected medical treatment format (in the example of FIG. 6, "in-person") in the input field E23. Whether the medical treatment format can be selected or not is determined for each medical treatment menu, such as not being able to in "Treatment F1" but being able to in "Consultation G1". If possible, the patient inputs the inquiry information provided for each medical treatment menu in the input field E24. Note that the input of the inquiry information is not mandatory and can also be done, for example, when visiting a medical institution.

[0035] After the patient terminal 20 receives each of the above operations by the patient and then receives an operation on the reservation confirmation button B21, the patient terminal 20 transmits reservation data indicating each piece of information for the input reservation to the server device 10. In this way, in A21 and A22, the patient terminal 20 displays a reservation screen and an inquiry screen, and the patient terminal 20 receives the reservation of medical treatment by the patient and (if input) the operation of the inquiry.

[0036] Note that the reservation change button B22 is a button for changing the medical treatment reservation, and the cancel button B23 is a button for canceling the medical treatment reservation. The information processing when these buttons are operated will be described in detail later.

[0037] The server device 10 performs the reservation of medical treatment and the reception process of the inquiry received at the patient terminal 20 in A23. The reservation content of the medical treatment and the inquiry result are each information regarding the patient's medical treatment (hereinafter referred to as "medical treatment information"). The server device 10 stores a medical treatment information database and a patient information database for storing such medical treatment information, and executes a process of storing new medical treatment information in those databases as a reception process.

[0038] FIG. 7 is a diagram showing an example of the medical treatment information database. In the medical treatment information database DB1 shown in FIG. 7, the medical treatment information is stored for each medical staff and each facility. The "-" in the figure indicates that no information has been stored yet. Note that, for the sake of clarity of the item names of the medical treatment information, the item names ("patient name", etc.) are shown in parentheses at some un-stored locations.

[0039] Medical staff refers to the personnel who provide medical treatment to patients, such as doctors. Facilities refer to equipment and the like used in medical treatment. For example, if a medical institution is a dental clinic, the facilities are units that consist of a chair for the patient to sit on and the equipment necessary for medical treatment. In the medical information database DB1, for each medical staff, medical information including patient name, medical treatment menu, medical treatment form, medical treatment time, reception status, equipment used, and link information is stored in association with a medical information ID. Also, for each piece of equipment, medical information including patient name, medical treatment menu, medical treatment form, medical treatment time, status, corresponding staff, and link information is stored in association with a medical information ID.

[0040] The patient name is the name of each patient and is associated with a patient ID for identifying each patient. The medical treatment menu is the name of the medical treatment planned for the patient. The medical treatment form is the form of the medical treatment, which is either in-person medical treatment or online medical treatment. The medical treatment time is information indicating the time when the medical treatment is to be carried out. The medical treatment time is a scheduled time before the patient is received at the medical institution and becomes a confirmed time after the reception. In the figures after Figure 7, only the hours and minutes are shown as the medical treatment time, but it is assumed that the date information is also included.

[0041] The status is information indicating the status of the medical treatment reservation. In the medical treatment management system 1, it is indicated by four statuses: "not received", "examination", "accounting", and "completed". "Not received" indicates the situation where the patient has not yet been received at the medical institution. "Examination" indicates the situation from when the patient is received at the medical institution until the examination is completed. "Accounting" indicates the situation from when the patient's examination is completed until the accounting is carried out. "Completed" indicates the situation where the patient has completed the accounting and the medical treatment is finished. The equipment used indicates the equipment used during the medical treatment. The corresponding staff indicates the medical staff corresponding to the patient. The link information will be explained later.

[0042] For example, in the medical treatment information S11 of doctor D1, medical treatment information including patient name "K1", consultation "G1", face-to-face, "9:30 - 10:00", completed, equipment "Unit U1" and link information "NA" is associated. Also, in the medical treatment information S12 of Unit U1, medical treatment information including patient name "K1", consultation "G1", face-to-face, "9:30 - 10:00", completed, corresponding staff "doctor D1" and link information "NA" is associated.

[0043] Note that "NA" indicates that there is no corresponding link information, which will be explained in detail later. Also, these medical treatment information S11 and S12 represent information regarding the same medical treatment for the same patient. Hereinafter, similarly, medical treatment information with the same tens digit of the code represented by "S" + "two-digit number" (in this case, "S11" and "S12") attached to "medical treatment information" is considered to represent information regarding the same medical treatment performed by the same doctor at the same medical treatment time for the same patient (for example, the medical treatment indicated by "medical treatment information S11" and the medical treatment indicated by "medical treatment information S12" are the same).

[0044] In other words, medical treatment information S11 and S12 are medical treatment information indicating the same medical treatment reservation, but are represented by codes including two-digit numbers with only the units digit changed to separately represent the reservation of medical staff and the reservation of equipment. When not distinguishing between medical treatment information S11 and S12, for example, the same medical treatment information ID such as medical treatment information S10 may be associated.

[0045] In the medical treatment information S21 of doctor D3, medical treatment information including "K2", treatment "F3", face-to-face, "10:30 - 11:00", accounting, equipment "Unit U2" and link information "NA" is associated, and in the medical treatment information S22 of Unit U2, medical treatment information including "K2", treatment "F3", face-to-face, "10:30 - 11:00", accounting, doctor D3 and link information "NA" is associated.

[0046] In addition, in the medical treatment information S31 of doctor D2, medical treatment information such as "K3", "treatment F1", "in-person", "11:00 - 12:00", "medical treatment", "unit U1", and "NA" is associated. In the medical treatment information S32 of unit U1, medical treatment information such as "K3", "treatment F1", "in-person", "11:00 - 12:00", "medical treatment", "doctor D2", and "NA" is associated.

[0047] In addition, in the medical treatment information S41 of doctor D3, medical treatment information such as "K4", "consultation G2", "in-person", "12:00 - 12:30", "not yet accepted", "unit U2", and "NA" is associated. In the medical treatment information S42 of unit U1, medical treatment information such as "K4", "consultation G2", "in-person", "12:00 - 12:30", "not yet accepted", "doctor D3", and "NA" is associated.

[0048] The server device 10 stores the examination menu and examination format input on the second screen C2 for reservation for patients shown in FIG. 6, and stores the input reservation date and time as the medical treatment date and time. In addition, the server device 10 stores any examination staff and facilities among the examination staff and facilities with an available schedule at the reservation date and time as the corresponding staff and used facilities. In this way, in the present embodiment, the patient cannot make a reservation by specifying a specific medical staff and specific facilities.

[0049] When storing the reservation date and time as the medical treatment date and time, if there is no examination staff with an available schedule at the reservation date and time, that is, if the patient has erroneously entered a non-reservable time zone as the reservation date and time, the server device 10 does not store the reservation date and time, and transmits notification data notifying that the reservation reception process cannot be performed to the patient terminal 20. The patient terminal 20 displays the notified content and prompts the input of a reservable date and time. Then, when a reservable date and time is input, the server device 10 executes the reservation reception process.

[0050] Each time a medical appointment is reserved, the server device 10 creates new medical information and stores it in the medical information database DB1 in association with the medical staff who will conduct the medical examination and the units used for the medical examination. In this way, the server device 10 performs the reservation acceptance process when a reservation is made by a patient. By performing the reservation acceptance process, referring to the medical information database DB1 makes it possible to grasp the reservation status of each medical staff and each facility, the content of the reserved medical examination, the implementation status of the medical examination, and so on.

[0051] The server device 10 stores a part of the above-mentioned medical information and the interview results in the patient information database. FIG. 8 is a diagram showing an example of the patient information database. The server device 10 stores the patient's basic information, medical information ID, link information, medical record information, accounting information, and status as patient information in the patient information database DB2 shown in FIG. 8. In the figure, "-" indicates that no information has been stored yet, and "···" indicates that some information has been stored.

[0052] First, the server device 10 secures a new area for storing patient information and stores the same medical information IDs (S41 and S42 in the example of FIG. 8) as those stored in the medical information database DB1 in that area. By this medical information ID, the medical information stored in the medical information database DB1 and the patient information stored in the patient information database DB2 are associated with each other.

[0053] In addition, the server device 10 stores the basic information of the patient who will receive the medical examination in association with the medical information ID. The basic information of the patient is the patient name, address, patient ID of the patient, etc. that were input when the patient registered as a user of the medical examination management system 1. The link information will be described later.

[0054] In addition, the server device 10 stores medical record IDs, history information, interview information, symptoms, treatment details, etc. as medical record information. The medical record ID is identification information for associating the medical record used in medical treatment with medical treatment information. In the example of FIG. 8, the medical record ID "R10" is stored in association with the medical treatment information S11 and S12. Similarly, the medical record IDs "R20", "R30", and "R40" are stored in association with the medical treatment information S21 and S22, the medical treatment information S31 and S32, and the medical treatment information S41 and S42, respectively.

[0055] The history information is information indicating the history of the patient's past medical records. The history of medical records is stored, for example, in an electronic medical record system and managed in association with the patient ID. Each time the server device 10 stores a medical treatment information ID in association with the patient ID, it reads out the history information associated with that patient ID from the electronic medical record system and stores it in the patient information database DB2. Information input in medical treatment based on the current examination reservation is stored in the interview information, symptoms, treatment details, etc.

[0056] In addition, the server device 10 stores an accounting ID, treatment fees, and information indicating the presence or absence of payment as accounting information. The accounting ID is identification information for associating the accounting of each patient with medical treatment information. In the example of FIG. 8, the accounting ID "T10" is stored in association with the medical treatment information S11 and S12. Similarly, the accounting IDs "T20", "T30", and "T40" are stored in association with the medical treatment information S21 and S22, the medical treatment information S31 and S32, and the medical treatment information S41 and S42, respectively.

[0057] The status stores the status described in FIG. 7. Since the interview information may be input at the time of reservation, it is already stored for patients with the status of "medical treatment" or "not yet received". In this way, the server device 10 executes the reception process for the interview results by the patient.

[0058] In addition to making a reservation by operating the patient terminal 20, the patient can make a reservation by calling the medical institution. In that case, the receptionist at the medical institution performs an operation to display a screen for making a medical appointment on the reception screen displayed on the reception terminal 30, for example. When this operation is performed on the reception terminal 30, the server device 10 executes, as display processing, a process of generating screen data indicating a reservation screen for reception at A24 and transmitting the generated screen data to the reception terminal 30.

[0059] FIG. 9 is a diagram showing an example of a reservation screen for reception. The reception terminal 30 displays a reception reservation screen C3 including an input field E31 for the patient name, an input field E32 for the medical menu, an input field E33 for the reservation date and time, an input field E34 for the medical treatment format, an input field E35 for the corresponding staff, an input field E36 for the equipment to be used, a schedule table L21 for the medical institution, a reservation confirmation button B31, a reservation change button B32, a cancel button B33, and a linked reservation button B34.

[0060] The schedule table L21 is a table showing the schedule of medical treatment for each patient. In the present embodiment, the medical treatment information is arranged in chronological order and shown in the schedule table L21. The server device 10 reads the medical treatment information from the medical treatment information database DB1 shown in FIG. 7 and displays it as the schedule table L21 arranged in chronological order in the schedule columns of each medical staff and each equipment. In the present embodiment, the server device 10 shows the time zones in which reservations can be made as white rectangular areas, and shows a table in which the time zones with existing reservations are shown as rectangular areas including examination information (referred to as "reservation areas" as in FIG. 6) as the schedule table L21.

[0061] The receptionist talks to the patient while looking at the schedule L21 for medical institutions, and enters the patient's name in the input field E31 and the date and time the patient wishes to make a reservation in the input field E33. Also, the receptionist enters the medical menu heard from the patient in the input field E32 and the medical treatment format in the input field E34. Further, the receptionist enters the corresponding staff in the input field E35 and the equipment to be used in the input field E36 from the medical staff and equipment available at the reservation date and time. The server device 10 causes the medical information indicating the entered medical reservation to be displayed in the reservation area in the schedule of the reserved corresponding staff and equipment.

[0062] In the example of FIG. 9, the server device 10 displays medical information indicating that a medical reservation for "consultation G1" for "patient K1" by "doctor D2" is made in the reservation area H311 of the "unit U2" at "9:30 - 10:00" which is the equipment to be used. Also, the server device 10 displays medical information indicating that a medical reservation for "consultation G1" for "patient K1" using the "unit U2" is made in the reservation area H312 of "doctor D2" who is the corresponding staff for patient K1 at "9:30 - 10:00". These medical information are information showing a part of the medical information S11 and S12 shown in FIG. 7.

[0063] Similarly, the server device 10 displays medical information indicating that a medical reservation for "treatment F2" for "patient K2" by "doctor D3" is made in the reservation area H321 of the "unit U2" at "10:30 - 11:00" which is the equipment to be used. Also, the server device 10 displays medical information indicating that a medical reservation for "treatment F2" for "patient K2" using the "unit U2" is made in the reservation area H322 of "doctor D3" who is the corresponding staff for patient K2 at "10:30 - 11:00". These medical information are information showing a part of the medical information S21 and S22 shown in FIG. 7.

[0064] Similarly, the server device 10 also displays medical information indicating that a medical appointment for "Treatment F3" for "Patient K3" by "Doctor D2" has been made in the reserved area H331 from "11:00 - 12:00" of the "Unit U1" which is the equipment in use. Also, the server device 10 displays medical information indicating that a medical appointment for "Treatment F3" for "Patient K3" using "Unit U1" has been made in the reserved area H332 from "11:00 - 12:00" of "Doctor D2" who is the staff corresponding to Patient K3. These medical information are the information showing a part of the medical information S31 and S32 shown in FIG. 7.

[0065] Similarly, the server device 10 also displays medical information indicating that a medical appointment for "Consultation G2" for "Patient K4" by "Doctor D3" has been made in the reserved area H341 from "12:00 - 12:30" of the "Unit U2" which is the equipment in use. Also, the server device 10 displays medical information indicating that a medical appointment for "Consultation G2" for "Patient K4" using "Unit U2" has been made in the reserved area H342 from "12:00 - 12:30" of "Doctor D3" who is the staff corresponding to Patient K4. These medical information are the information showing a part of the medical information S41 and S42 shown in FIG. 7.

[0066] In addition, the server device 10 displays characters "Completed" (status where accounting is completed and medical treatment is completed. Also referred to as "Completed"), "Accounting" (status where medical treatment is completed but accounting has not been completed yet. Also referred to as "Accounting"), "Medical Treatment" (status where reception of the visit to the hospital has been done but medical treatment has not been completed yet. Also referred to as "Medical Treatment"), and "Not Reserved" (status where a medical appointment has been made but reception of the visit to the hospital has not been done yet. Also referred to as "Not Received") as the status of the medical appointments for Patients K1, K2, K3, and K4. Thus, the server device 10 also executes a display process for displaying the status of medical appointments in addition to the schedule table in A24, and the reception terminal 30 displays the schedule table and the status in A25.

[0067] Note that the input of the date and time (time zone) that the patient wishes to reserve may be performed by directly specifying the reservation area in the schedule table L21 for medical institutions. For example, the reception staff performs an operation to specify the date and time to be reserved in the schedule column of the medical staff. Then, the server device 10 causes the reservation area including the name of the medical staff and the reservation date and time to be displayed at the corresponding date and time in the schedule column of the medical staff. At that time, the server device 10 causes the specified reservation date and time to be displayed in the input field E33 and the name of the medical staff to be displayed in the input field E35. This eliminates the need for input into the input fields E33 and E35.

[0068] In addition, when there is a facility with an available schedule at the specified reservation date and time, the server device 10 causes the name of that facility (any one of them if there are multiple) to be displayed in the input field E36. When an operation of pressing the reservation confirmation button B31 is performed in this state, the server device 10 causes the information indicating the medical appointment displayed in the input field E36 to be displayed in the reservation area in the schedule table of the reserved facility. Similarly, when an operation of specifying the date and time to be reserved is performed first in the schedule column of the facility, the server device 10 also causes the name of the medical staff with an available schedule to be displayed in the input field E35 as the corresponding staff, and when an operation of pressing the reservation confirmation button B31 is performed, the information indicating the medical appointment is displayed in the reservation area in the schedule table of the reserved medical staff.

[0069] As described above, when the patient makes a reservation using the second screen C2 for patient reservation, it is not possible to specify a specific medical staff and facility for reservation, but when the reception staff makes a reservation using the reception reservation screen C3, it is possible to specify a specific medical staff and facility for reservation.

[0070] The reservation change button B32 is a button to be operated when changing a medical appointment that has been confirmed once. The cancel button B33 is a button to be operated when canceling a medical appointment that has been confirmed once. The linked reservation button B34 is a button to be operated when making a linked reservation.

[0071] Link reservation means associating two or more medical appointments of the same patient. Link reservation is performed, for example, when a patient consults a doctor and is likely to receive treatment immediately depending on the result of the consultation, in order to manage by associating the reservation for the consultation and the reservation for the treatment. Also, when the medical management system 1 manages medical treatments at medical institutions other than dentists, the same patient may receive medical treatments in multiple departments or undergo multiple examinations. Therefore, for example, link reservation may be performed to manage by associating the reservation for the first medical department or examination with the reservation for the second medical department or examination.

[0072] In link reservation, it is necessary to perform an operation of associating two or more medical appointments of the same patient (hereinafter referred to as "link operation"). An example of the link operation will be described with reference to FIGS. 10 and 11.

[0073] FIG. 10 is a diagram showing an example of the link operation. In FIG. 10, the reception terminal 30 is displaying the reception reservation screen C3 shown in FIG. 9. When the reception staff performs link reservation for the medical appointment of patient K4, first, the medical appointment of patient K4 is selected from the schedule table L21. The selection of the medical appointment of patient K4 is performed, for example, by operating such as tapping or clicking on the reservation area H341 or H342 where the medical information of patient K4 is shown.

[0074] When the medical appointment is selected, the server device 10 highlights the selected reservation area (in the example of FIG. 10, thickens the frame line) and displays the contents of the selected medical appointment in the input fields E31 to E36 respectively. Next, the reception staff performs an operation of pressing the link reservation button B34. When the link reservation button B34 is operated, the server device 10 displays the input fields for the medical information regarding the link reservation.

[0075] FIG. 11 is a diagram showing an example of an input field for link reservation. In FIG. 11, the reception terminal 30 displays, on the reception reservation screen C3, in addition to the input field E31 for the patient name shown in FIG. 10, the input field E32 for the medical menu, the input field E33 for the reservation date and time, the input field E43 for the reservation date and time of the link reservation, the input field E44 for the medical menu of the link reservation, the input field E45 for the medical treatment format of the link reservation, the input field E46 for the corresponding staff of the link reservation, and the input field E47 for the equipment to be used in the link reservation.

[0076] The reception staff inputs the reservation date and time of the link reservation while referring to the reservation date and time of the selected medical reservation and the availability of medical staff and equipment in the schedule table L21. In the example of FIG. 11, medical information such as "13:00-14:00", "Treatment F4", "In-person", "Doctor D1", and "Unit U1" is input. Note that, also in the input of the link reservation, the input of the date and time (time zone) to be reserved may be performed by an operation of directly designating the reservation area in the schedule table L21.

[0077] The server device 10 causes the medical information indicating the input link reservation to be displayed in the reservation areas (reservation areas H351 and H352 in the example of FIG. 11) corresponding to the medical treatment times in the schedule table L21. At that time, the server device 10 causes the reservation areas to be linked (associated with each other) to be displayed in the same manner. In the example of FIG. 11, the server device 10 causes the reservation areas H351 and H352 to be highlighted in the same way as the linked reservation areas H341 and H342 (in the example of FIG. 11, the frame lines are thickened). When the input of the link reservation is completed, the reception staff operates the reservation confirmation button B31 to confirm the link reservation.

[0078] When the receiving terminal 30 receives a series of operations for inputting the above link reservation at A31, it transmits link reservation data indicating each piece of information (such as reservation date and time) for the input link reservation to the server device 10. When the link reservation data is transmitted, the server device 10 executes a link process for reflecting the link reservation at A32. The server device 10 executes, as the link process, a process of storing the content of the link reservation in the medical information database DB1 and the patient information database DB2.

[0079] FIG. 12 is a diagram showing an example of the medical information database after the link process. The server device 10 stores medical information S51 and S52 indicating a new link reservation in the medical information database DB1. In the medical information S51 of doctor D1, medical information including "K4", "treatment F4", "face-to-face", "13:00 - 14:00", "not received", "unit U2", and patient name "S41", medical menu, medical form, medical time, status, used equipment, and link information is associated.

[0080] Also, in the medical information S52 of unit U2, medical information including "K4", "treatment F4", "face-to-face", "13:00 - 14:00", "not received", "doctor D1", and patient name "S42", medical menu, medical form, medical time, status, used equipment, and link information is associated. Further, the server device 10 stores "S51" in the link information of the medical information S41 indicating the linked medical reservation, and stores "S52" in the link information of the medical information S42 indicating the original medical reservation.

[0081] By storing the link information in the medical information database DB1 as described above, the medical information S41 and S51 of the medical staff are associated with each other, and the medical information S42 and S52 of the equipment are associated with each other. The server device 10 further stores the link information in the patient information database DB2.

[0082] FIG. 13 is a diagram showing an example of a patient information database after link processing. The server device 10 stores patient information indicating a link reservation with medical information S41 and S42 as link destinations in the patient information database DB2. First, the server device 10 secures a new area for storing patient information, and stores medical information IDs (S51 and S52 in the example of FIG. 13) indicating the same link reservation as that stored in the medical information database DB1 in that area.

[0083] Next, the server device 10 stores, as link information, the medical information IDs of the link destinations (S41 and S42 in the example of FIG. 13) in association with the medical information IDs indicating the link reservation. Further, the server device 10 stores, as link information, the medical information IDs of the link reservation (S51 and S52 in the example of FIG. 13) in association with the medical information IDs of the link destinations (S41 and S42 in the example of FIG. 13) stored as "medical information IDs".

[0084] By storing the link information in the patient information database DB2 as described above, the set of medical information S41 and S42 indicating the link destination and the set of medical information S51 and S52 indicating the link source are associated with each other. Medical information with link information being "NA" (not applicable), such as the set of medical information S11 and S12, indicates that it is independent medical information for which such a link reservation has not been made.

[0085] In addition, the server device 10 stores the patient name (in the example of FIG. 13, "K4") and the patient ID stored in association with the medical information ID of the link destination, "S41, S42", in association with the medical information ID "S51, S52". In this case, since the basic information of patient K4 can be referred to by referring to the basic information associated with "S41, S42", the server device 10 does not store the basic information of the patient other than the patient name and the patient ID in the storage area associated with "S51, S52".

[0086] In addition, the server device 10 stores the medical record ID associated with the medical information ID of "S51, S52", that is, the medical record ID of "R40" which is the same as the linked destination and is associated with the medical information ID of the linked destination "S41, S42". In this case, since the medical record information of patient K4 can be referred to by referring to the medical record information associated with "S41, S42" and "R40", the server device 10 does not store the medical record history information and the interview information in the storage area associated with "S51, S52".

[0087] In addition, the server device 10 stores the accounting ID of "T40" assigned to patient K4, which is the same as the linked destination "S41, S42", in association with the medical information ID of "S51, S52". Since the medical treatment has not been completed yet when this link reservation is made, the server device 10 does not store accounting information other than the accounting ID. In addition, the server device 10 stores the status (since it is the reservation time, "not received") in association with the medical information ID of "S51, S52".

[0088] The display of the schedule table after the link process is executed as described above will be explained. When the server device 10 is requested to display the schedule table from the patient terminal 20 or the reception terminal 30 by the operation of the patient or the operation of the reception staff, at A33, the server device 10 executes display processing for displaying the schedule table for the patient or the schedule table for the medical institution. The reception terminal 30 displays, at A34, the schedule table L21 shown in FIG. 11, for example, as the schedule table for the medical institution. In the schedule table L21, the source medical treatment area and the destination medical treatment area of the link are displayed separately.

[0089] The patient terminal 20 displays, at A35, the schedule table for the patient. FIG. 14 is a diagram showing an example of a schedule table for a patient to be displayed. The patient terminal 20 is displaying a second screen C2 for reservation for the patient shown in FIG. 6. A patient schedule table L11 is displayed on the second screen C2. In the schedule table L11, only the area corresponding to the reserved date and time of the medical appointment reserved by the patient is displayed (other reserved areas shown in FIG. 6 are omitted).

[0090] When the server device 10 is requested by the patient terminal 20 to display the patient schedule table L11, it refers to the patient information database DB2 and reads out the medical information associated with the patient who has logged in by operating the patient terminal 20. The server device 10 displays a reservation area within the range of the medical treatment time indicated by the read medical information.

[0091] As a result, in the example of FIG. 6 before the linked reservation, a reservation area H21 with a medical treatment time of "12:00 - 12:30" was displayed, but in the example of FIG. 14 after the linked reservation, a reservation area H22 with a medical treatment time of "12:00 - 14:00" including the linked reservation is displayed. The reservation area H22 is the same as the reservation area H21 in that it indicates one medical appointment, although the medical treatment time has changed from the reservation area H21. Note that although the time period from 12:30 to 13:00, which is the time period between the end time of the linked medical treatment and the start time of the linked reservation, is not scheduled for medical treatment, the server device 10 displays an area representing one medical appointment including that time period as the reservation area H22.

[0092] Next, the medical record process will be described. FIG. 15 is an activity diagram showing an example of the medical record process. In the example of FIG. 15, the reception terminal 30 displays a reception-oriented screen indicated by the screen data transmitted from the server device 10 at A13, and the doctor terminal 40 displays a doctor-oriented screen indicated by the screen data transmitted from the server device 10 at A14.

[0093] A patient who has made a medical appointment visits a medical institution to receive medical treatment at the reserved date and time, and goes to the reception desk to check in. The reception staff of the medical institution performs an operation to accept the patient's visit on the reception terminal 30. The reception terminal 30 displays a screen for receiving the patient's visit. FIG. 16 is a diagram showing an example of a screen for receiving a patient's visit. On the screen C4 for receiving a patient's visit shown in FIG. 16, a schedule table L21 of medical treatment times after link reservation in the example of FIG. 11 is displayed. A current time line J1 is shown in the schedule table L21. Before the current time line J1 represents a past time zone, and after the current time line J1 represents a future time zone.

[0094] The server device 10 causes the characters "not yet" to be displayed in reservation areas H341, H342, H351, and H352 for medical treatment information that has not yet been received. Also, the server device 10 causes the characters "medical treatment" to be displayed in reservation areas H331 and H332 in a situation where reception has been completed and the patient is waiting for medical treatment or is in the middle of medical treatment. When the medical treatment result is input and the patient is in a state of waiting for accounting, the server device 10 causes the characters "accounting" to be displayed in reservation areas H321 and H322. Also, when the accounting process is completed, the server device 10 causes the characters "completed" to be displayed in reservation areas H311 and H312.

[0095] When a patient who has come to the hospital arrives at the reception desk, the reception staff performs a visit operation to accept the patient's visit. The visit operation is, for example, an operation of clicking on the characters "not yet". At A41, the reception terminal 30 accepts the visit operation by the reception staff and transmits patient name and visit data indicating the visit to the server device 10. When the server device 10 receives the visit data, at A42, the server device 10 executes a reception process to accept the visit of the patient indicated by the visit data. The server device 10 executes, as the reception process for the visit, a process of changing the status of the corresponding medical treatment information in the medical treatment information database DB1 shown in FIG. 12 from "not received" to "medical treatment". When the server device 10 executes the reception process, the server device 10 changes the characters "not yet" of the corresponding medical treatment information to the characters "medical treatment" and displays them on the reception terminal 30.

[0096] Here, when the patient has not entered the medical interview information at the time of reservation, the medical interview information is entered. The medical interview information can be entered by the patient himself / herself using the patient terminal 20 after arriving at the hospital, or by the patient or the receptionist using the reception terminal 30. In the example of FIG. 15, the case of using the reception terminal 30 will be described. The reception terminal 30 displays an input field E24 for medical interview information similar to that in FIG. 6 at A43 and accepts the input operation of the medical interview. When the reception terminal 30 is a tablet terminal, the tablet terminal may be handed to the patient to input the medical interview information. If it is difficult to let the patient operate the reception terminal 30, the receptionist may input the content described by the patient on the paper medical interview form. The server device 10 executes the reception process of the medical interview in the same manner as A23 shown in FIG. 4 at A42.

[0097] The patients who have completed the reception at the hospital and, in some cases, the reception of the medical interview receive the medical treatment of the reserved doctor in the reserved unit. The doctor conducts medical treatment on the patient and, using the doctor terminal 40, performs an operation to display the patient's medical record information. First, the doctor performs an operation to display a reservation screen for doctors on the doctor terminal 40. By this operation, the server device 10 performs a display process for displaying a schedule table for doctors at A44. Then, the doctor terminal 40 displays a schedule table for doctors at A45.

[0098] FIG. 17 is a diagram showing an example of the displayed schedule table for doctors. The doctor terminal 40 displays a doctor-oriented screen C5 including a schedule table L51 that extracts a portion of the schedule table L21 of the medical treatment time shown in FIG. 16 that shows the medical treatment reservations related to the doctor using the terminal itself (doctor D3 in the example of FIG. 17). Similar to the example of FIG. 16, a current time line J1 is shown in the schedule table L51, and the reservation area overlapping the current time line J1, that is, the reservation area indicating the current medical treatment reservation, is highlighted (displayed surrounded by a thick line).

[0099] In the example of FIG. 17, the current time is earlier than that in the example of FIG. 16, and the times at which the medical treatments indicated by the reservation areas H321 and H322 are currently being performed. When doctor D3 selects this reservation area H321 or H322 by an operation such as tapping or clicking, the doctor terminal 40 receives, at A51, this operation as a display operation for displaying the medical record information of the patient (patient K2 in the example of FIG. 17) for whom a medical treatment reservation is indicated in the selected reservation area.

[0100] The doctor terminal 40 transmits request data indicating a display request for the medical treatment reservation (medical treatment information S21, S22 in the example of FIG. 17) and the medical record information of the patient for whom the display operation has been performed to the server device 10. When the server device 10 receives the request data, the process to be performed next changes depending on whether the medical treatment reservation for which the display of the medical record information is requested is a linked reservation. In the example of FIG. 17, since the medical treatment reservation is not a linked reservation, the server device 10 reads out, at A52, the medical record information associated with the medical treatment reservation indicated by the request data from the patient information database DB2.

[0101] The server device 10 transmits the read medical record information to the doctor terminal 40. The doctor terminal 40 displays, at A53, the transmitted medical record information. The doctor performs the medical treatment while looking at the displayed medical record information, and inputs the results of the examination and the results of the treatment, etc. When the doctor terminal 40 receives, at A54, those medical record input operations, it transmits update information of the input medical record information to the server device 10. The server device 10 stores, at A55, the transmitted update information in the patient information database DB2 to update the medical record information of the patient who has received the medical treatment.

[0102] FIG. 18 is a diagram showing an example of the patient information database after the medical treatment. The server device 10 stores, in the patient information database DB2, the medical record information (the portion surrounded by the thick frame) input by doctor D3 for patient K2, in association with the medical treatment information S21, S22 of patient K2. In FIGS. 17 and 18, the medical record processing for patient K2 for whom no linked reservation has been made has been described. Next, with reference to FIGS. 19 to 22, the medical record processing for patient K4 for whom a linked reservation has been made will be described.

[0103] FIG. 19 is a diagram showing an example of a schedule table for doctor D1. The doctor terminal 40 of doctor D1 displays a doctor-oriented screen C6 including the schedule table L61 of doctor D1. In the example of FIG. 19, the reservation area where the current time line J1 overlaps, that is, the reservation area indicating the current medical appointment, is the reservation areas H341 and H342 of patient K4. When doctor D1 selects the reservation area H341 or H342, the doctor terminal 40 accepts this operation as a display operation for displaying the medical record information of patient K4 at A51.

[0104] The medical information S41 indicated by the reservation area H341 is the "linked destination" medical appointment of the medical information S51 which is the above-described linked reservation. The medical appointment that is the "linked destination" of the linked reservation is regarded as not being a linked reservation. Therefore, in the example of FIG. 19, since the medical appointment is not a linked reservation, the server device 10 reads out the medical record information associated with the medical appointment indicated by the request data from the patient information database DB2 at A52 in the same manner as in the example of FIG. 17. Thereafter, the information processing from A53 to A55 is performed, and the medical treatment result of patient K4 by doctor D1 is stored in the patient information database DB2.

[0105] FIG. 20 is a diagram showing another example of the patient information database after medical treatment. The server device 10 stores in the patient information database DB2 the medical record information (the portion surrounded by the thick frame) input by doctor D1 for patient K4 in association with the medical information S41 and S42 indicating the reservation of the medical treatment received by patient K4. Since doctor D1 continues to have a medical treatment for patient K4, doctor D1 performs an operation to display his / her schedule table on the doctor terminal 40.

[0106] FIG. 21 is a diagram showing another example of the schedule table for the displayed doctor D1. The doctor terminal 40 of doctor D1 is again displaying a doctor-oriented screen C6 including the schedule table L61 of doctor D1. In the example of FIG. 21, the reservation area where the current time line J1 overlaps, that is, the reservation area indicating the current medical appointment, is the reservation areas H351 and H352 of patient K4. When doctor D1 selects the reservation area H351 or H352, the doctor terminal 40 accepts this operation as a display operation for displaying the medical record information of patient K4 at A51.

[0107] The medical information S51 indicated by the reservation area H351 is a linked reservation associated with the medical information S41. When the medical appointment is a linked reservation, as described above, in the area associated with the medical information ID indicating the medical appointment, no medical record information other than the medical record ID (in the case of medical information S51, the medical record ID of "R40") is stored. Therefore, the server device 10 reads, at A61, the linked medical record information associated with the same medical record ID as the medical record ID of "R40" associated with the requested medical information S51, in other words, the medical record information (the medical record information stored in the example of FIG. 20) associated with the medical information S41 associated with the medical information S51 by the linked reservation, from the patient information database DB2.

[0108] The server device 10 transmits the read medical record information to the doctor terminal 40. The doctor terminal 40 displays, at A62, the transmitted medical record information. Doctor D1 performs the medical treatment while looking at the displayed medical record information, and inputs the results of further examinations and treatments for patient K4. When the doctor terminal 40 accepts those medical record input operations at A63, it transmits the updated information of the input medical record information to the server device 10. The server device 10 stores, at A64, the transmitted updated information in the patient information database DB2 to update the medical record information of the patient who has received the medical treatment.

[0109] FIG. 22 is a diagram showing another example of a patient information database after medical treatment. The server device 10 stores the medical record information (the portion surrounded by the thick frame) input by the doctor D1 for the patient K4 in the patient information database DB2 in association with the medical treatment information S41 and S42. As a result, the result of the medical treatment performed based on the medical treatment information S41 and the result of the medical treatment performed based on the medical treatment information S51, which is a link reservation associated with the medical treatment information S41, are reflected in the same medical record information (the medical record information associated with the medical treatment information S41 and S42).

[0110] In this way, the medical record information stored in the patient information database DB2 is stored in the electronic medical record system when the medical treatment is completed. At that time, by storing the medical record ID "R40" included in the medical record information together, it becomes possible to determine that the stored medical record information shows the results of medical treatments based on the medical treatment information S41, S42, S51, and S52 associated with the medical record ID "R40". Note that the medical record information may be associated with the medical treatment information ID instead of the medical record ID and stored in the electronic medical record system to associate the medical record information with the medical treatment.

[0111] In the example of FIG. 22, no medical record information other than the medical record ID is stored in the storage area of the medical record information associated with the medical treatment information S51, which is a link reservation. This is an example of a method for storing medical record information in a link reservation, and the method for storing medical record information in a link reservation is not limited to this. For example, the storage areas of the medical record information associated with the medical treatment information S41 and S51 may be integrated, and the medical record information may be stored in the integrated storage area. In short, when the medical record information for the link reservation is read out, the medical record information associated with the linked medical treatment reservation is read out, and when the read medical record information is updated, the medical record information associated with the linked medical treatment reservation should be updated.

[0112] Next, the accounting process will be described. FIG. 23 is an activity diagram showing an example of accounting processing. In the example of FIG. 23, the server device 10 performs display processing of a reception-oriented screen at A71, and the reception terminal 30 displays the reception-oriented screen indicated by the screen data transmitted from the server device 10 at A72.

[0113] FIG. 24 is a diagram showing an example of a reception screen for accounting. On the accounting reception screen C7 shown in FIG. 24, a schedule table L71 of medical treatment times is displayed. A current time line J1 is shown in the schedule table L71. The server device 10 highlights (displays surrounded by a thick line) a reservation area whose status is "accounting". When a patient comes for accounting, the accounting reception staff performs an operation of selecting the reservation area corresponding to that patient. The reception terminal 30 receives, at A73, that operation as an accounting operation for outputting accounting information.

[0114] The reception terminal 30 transmits request data indicating the medical treatment reservation of the patient for whom the accounting operation has been performed (medical treatment information of patient K2 in the example of FIG. 24) and a request for output of accounting information to the server device 10. When the server device 10 receives the request data, the processing to be performed next changes depending on whether the medical treatment reservation for which output of accounting information is requested is a linked reservation. In the example of FIG. 24, since the medical treatment reservation is not a linked reservation, the server device 10 reads out the medical record information associated with the medical treatment reservation indicated by the request data from the patient information database DB2 at A74.

[0115] The server device 10 generates accounting information based on the read medical record information at A75. For example, the server device 10 calculates the medical treatment fee points from the medical treatment content, and generates, as accounting information, the patient's out-of-pocket amount, that is, the treatment fee, obtained from the calculated medical treatment fee points. The server device 10 transmits the generated accounting information to the reception terminal 30. The reception terminal 30 displays the transmitted accounting information at A76.

[0116] When a patient makes a payment based on the presented accounting information (treatment fees), the receptionist inputs to the reception terminal 30 that the payment has been completed. The reception terminal 30, at A77, accepts the input of the payment result and transmits payment data indicating the payment result to the server device 10. The server device 10, at A78, updates the accounting information in the patient information database DB2 based on the payment result indicated by the transmitted payment data.

[0117] Figure 25 is a diagram showing an example of the patient information database after accounting. The server device 10 stores, in the patient information database DB2, the treatment fees and payment results (the parts enclosed by thick frames) output for patient K2 as accounting information, associated with the medical treatment information S21 and S22 of patient K2. Since the payment by patient K2 has been completed, the server device 10 has changed the status to "completed". In FIGS. 24 and 25, the accounting process for patient K2 for whom no link reservation has been made has been described. Next, with reference to FIGS. 26 to 28, the accounting process for patient K4 for whom a link reservation has been made will be described.

[0118] Figure 26 is a diagram showing an example of the displayed schedule table for reception. In FIG. 26, the same accounting reception screen C7 as in FIG. 24 and the schedule table L71 of the medical treatment time are displayed. In the example of FIG. 26, the reservation areas where the current time line J1 overlaps, that is, the reservation areas indicating the current medical treatment reservations, are the reservation areas H351 and H352 of patient K4. In the example of FIG. 26, the medical treatments indicated by the reservation areas H341 and H342 indicating the linked medical treatment reservations have ended, but the medical treatments indicated by the reservation areas H351 and H352 which are link reservations have not ended yet.

[0119] In this case, the server device 10 also causes the status indicating "medical treatment in progress" rather than "completed" to be displayed for the medical treatments indicated by the reservation areas H341 and H342. The server device 10 causes the status indicating "medical treatment in progress" to be displayed for the medical treatments indicated by the reservation areas H341 and H342 associated with the link reservation until the medical treatments indicated by the reservation areas H351 and H352 which are still link reservations end.

[0120] While the server device 10 is displaying the status of "examination", it does not highlight the reservation area and does not accept accounting operations. By doing so, the server device 10 ensures that accounting information is not output for the linked examination until the examination of the link reservation is completed. After the examination of the link reservation is completed, that is, after the examinations indicated by the reservation areas H351 and H352 are completed, a reception schedule table is shown in FIG. 27.

[0121] FIG. 27 is a diagram showing another example of the displayed reception schedule table. As shown in FIG. 27, the server device 10 sets the status of the reservation areas H341, H342, H351, and H352 to "accounting" and highlights (displays them surrounded by a thick line) those reservation areas. When the patient K4 whose examination has ended comes for accounting, the accounting reception staff performs an operation of selecting any of these reservation areas corresponding to the patient K4. The reception terminal 30 receives, at A73, that operation as an accounting operation for outputting accounting information.

[0122] The reception terminal 30 transmits request data indicating the examination reservation of the patient for whom the accounting operation has been performed (the examination information S41, S42, S51, S52 of the patient K4 in the example of FIG. 27) and the output request for accounting information to the server device 10. In the example of FIG. 27, since the examination information S51 and S52, which are link reservations, are included in the examination reservation indicated by the request data, the examination reservation for which the output of accounting information is requested is a link reservation. When the examination reservation is a link reservation, accounting operations cannot be accepted until the examination of the link reservation is completed. Therefore, in the area associated with the examination information ID indicating the link reservation and the linked examination reservation, accounting information other than the accounting ID (the accounting ID of "T40" when the examination information ID is S41, S42, S51, S52) is not yet stored.

[0123] In that case, in step A81, the server device 10 reads out the medical record information associated with the linked medical information S41 and S42 from the patient information database DB2 among the medical appointments indicated by the request data. In step A82, the server device 10 generates accounting information based on the read medical record information and transmits the generated accounting information to the reception terminal 30. The reception terminal 30 displays the transmitted accounting information in step A83. The reception terminal 30 receives the input of the payment result by the patient K4 in step A84 and transmits payment data indicating the payment result to the server device 10. In step A85, the server device 10 updates the accounting information in the patient information database DB2 based on the payment result indicated by the transmitted payment data.

[0124] Figure 28 is a diagram showing another example of the patient information database after accounting. The server device 10 stores the accounting information (the part surrounded by the thick frame) generated in step A82 in the patient information database DB2 in association with the medical information S41 and S42 indicating the linked medical treatment. The treatment fee indicated by this accounting information is obtained from the medical treatment reward points calculated based on the results of two medical treatments performed based on the medical record information associated with the medical information S41 and S42, that is, the linked medical information S41 and S42 and the medical information S51 and S52 which are the linked appointments.

[0125] In the example of Figure 28, the server device 10 stores accounting information other than the accounting ID in the storage area of the accounting information associated with the medical information whose link destination and accounting ID are common, that is, the medical information S51 which is the linked appointment (the accounting information with the accounting ID of "T40"), so that the accounting information does not overlap. Note that the storage method of the accounting information in the linked appointment is not limited to this. For example, the storage areas of the accounting information associated with the medical information S41 and S51 may be integrated, and the accounting information may be stored in the integrated storage area. In short, as long as one piece of accounting information is stored together based on the results of the linked medical treatment and the results of the medical treatment based on the linked appointment, it is acceptable.

[0126] In this way, the accounting information stored in the patient information database DB2 is stored in, for example, the medical accounting system when the accounting is completed. At this time, by storing the accounting ID "T40" included in the accounting information together, it becomes possible to determine that the stored accounting information is output based on the results of medical treatments based on the medical treatment information S41, S42, S51, and S52 associated with the accounting ID "T40". Note that the association between the accounting information and the medical treatment may be made by associating the medical treatment information ID with the accounting information and storing it in the medical accounting system instead of the accounting ID.

[0127] As described above, the server device 10 is a computer that manages the medical treatment reservations of patients. The server device 10 executes, for example, a generation process for generating medical treatment information indicating the medical treatment reservations of patients based on a user operation. As described above, the generation process can be performed either from the patient terminal 20 or from the reception terminal 30. That is, the user referred to here includes both the patient and the reception staff.

[0128] In addition, the server device 10 executes a link process for associating two or more medical treatment reservations of the same patient based on a user operation. When the link process is performed, as described above, the medical record information and accounting information of the same patient can be grouped together. Here, in the medical treatment management system 1, it is assumed that the link process is a process executed when a user operation is performed from a terminal of a medical institution (the reception terminal 30 is an example). That is, as shown in FIG. 6 and the like, the server device 10 does not display a link reservation button on the patient terminal 20 and does not allow a user operation for the link process from the patient terminal 20.

[0129] According to such an aspect, a medical institution can manage whether to summarize medical record information and accounting information. Also, if link reservations can be made from the patient terminal 20 as well, it may happen that link reservations not grasped by the medical institution side are accepted, which may cause confusion in the reservation management in the medical institution. According to the above aspect, since all link reservations are made on the medical institution side, such confusion is not caused, and compared with the case where link reservations are possible from the patient terminal 20, the reservation management in the medical institution can be facilitated.

[0130] Also, as shown in FIGS. 6 and 9 etc., the server device 10 executes reservation display processing for displaying a medical appointment on a schedule table. As shown in FIG. 11 etc., the server device 10 executes, as reservation display processing, processing for displaying two or more medical appointments associated by link processing in a manner different from other medical appointments (in the example of FIG. 11, a manner of thickening the frame line). Here, the different manner is not limited to the manner shown in FIG. 11, and may be, for example, the color or size of the area, the color or type of the frame line, the color or size of the font, etc. By making the manners of the medical appointments different in this way, compared with the case where the manners are uniform, it is possible to make it easier to grasp the medical appointments for which the medical record information and accounting information are summarized into one.

[0131] Also, together with the reservation display processing, the server device 10 executes status display processing for displaying the status information of the patient who made the medical appointment together with the medical appointment of that patient on the schedule table. The server device 10 executes, as status display processing, processing for displaying the same status information about the patient who receives medical treatment based on two or more medical appointments for which link processing has been executed in any of those two or more medical appointments.

[0132] For example, in the reserved areas H341 and H351 where link processing has been executed, in the example of FIG. 11, the same status information of "not yet" is displayed for both, in the example of FIG. 26, the same status information of "diagnosis" is displayed for both, and in the example of FIG. 27, the same status information of "calculation" is displayed for both. According to such a mode, compared with the case where status information is displayed separately, it is possible to make it easier to grasp the medical reservation in which medical record information and accounting information are grouped together.

[0133] In addition, the server device 10 executes, as reservation display processing, a process of causing a medical institution terminal to display two or more medical reservations for which link processing has been executed as separate medical reservations, and causing a patient terminal to display two or more medical reservations for which link processing has been executed as one medical reservation. In the reception terminal 30 which is an example of a medical institution terminal, the server device 10 displays the medical information S41 and S51 for which link processing has been executed in separate reservation areas called the reservation area H341 and the reservation area H351, as shown in FIG. 11 and the like.

[0134] On the other hand, in the patient terminal 20 which is an example of a patient terminal, the server device 10 displays a reservation area H22 in which the medical reservation shown in the reservation area H341 and the medical reservation shown in the reservation area H351 for which link processing has been executed are grouped together, as shown in FIG. 14. According to such a mode, it is possible to show that two or more medical reservations are associated with a medical institution and convey accurate information. On the other hand, for a patient, if two or more reservation areas are displayed for one reservation, the patient will be confused. Therefore, by grouping the reservation areas into one, such confusion can be suppressed compared with the case where the reservation areas are not grouped.

[0135] In addition, as described with reference to FIG. 17 and the like, when medical treatment is performed based on a medical reservation, the server device 10 executes medical record output processing for outputting the medical record information of the patient who receives the medical treatment. At this time, when two or more medical reservations are associated by link processing, the server device 10 executes, as the medical record output processing, a process of outputting the medical record information output in one of the two or more medical treatments performed based on the two or more medical reservations also in the next medical treatment.

[0136] For example, in the example of FIG. 21, since the medical treatment information S41 and S51 are associated by link processing, the server device 10 outputs the medical record information output in the medical treatment based on the medical treatment information S41 also in the medical treatment based on the medical treatment information S51. If the medical record information is separately output in two or more medical treatments for the same patient, since the results of the previous medical treatment are not reflected in the subsequent medical record information, the previous medical record information must also be considered. On the other hand, according to the mode of outputting the previously output medical record information also in the medical treatment of the link reservation as described in FIG. 21, compared with the case where the medical record information of two or more medical treatments associated by link processing is separately output, two or more medical treatments for the same patient can be performed smoothly.

[0137] In addition, when medical treatment is performed based on the medical reservation indicated by the generated medical treatment information, the server device 10 executes accounting output processing for outputting accounting information corresponding to the result of the medical treatment. When the medical reservation for which accounting is to be performed is a medical reservation for which link processing has been performed, the server device 10 outputs the accounting information summarized into one for the medical treatments performed based on two or more medical reservations associated with the medical reservation. For example, in the example of FIG. 28, the server device 10 outputs the accounting information (the accounting information stored in the patient information database DB2 in association with the medical treatment information S41) summarized into one for the medical treatment of the medical treatment information S41 and the medical treatment of the medical treatment information S51 associated with each other by link processing. According to such a mode, the accounting information of two or more medical treatments can be summarized into one.

[0138] The information processing performed by the server device 10 can also be described as follows. The server device 10 executes, as generation processing, processing for generating at least one of first medical information not associated with two or more medical reservations and second medical information associated with two or more medical reservations. The first medical information is medical information about reservations for which no linked reservation has been made, for example, the medical information of patients K1, K2, and K3 shown in the reservation areas H311 to H332 shown in FIG. 9 and the like. The second medical information is medical information about reservations for which a linked reservation has been made, for example, the medical information of patient K4 shown in the reservation areas H341 to H352 shown in FIG. 11 and the like.

[0139] Then, when a medical treatment based on the medical reservation indicated by the first medical information generated by the generation processing is performed, the server device 10 executes, as accounting output processing, processing for outputting accounting information about that medical treatment. Also, when two or more medical treatments based on two or more medical reservations indicated by the second medical information generated by the generation processing are performed, the server device 10 outputs the accounting information for those two or more medical treatments consolidated into one. In such a manner as well, the accounting information for two or more medical treatments can be consolidated into one.

[0140] Subsequently, the change of the medical reservation will be described. FIG. 29 is an activity diagram showing an example of the reservation change process. In the example of FIG. 29, the case where a medical reservation is changed by an operation on the reception terminal 30 will be described. First, the server device 10 performs, at A91, display processing of the reception-oriented screen, and the reception terminal 30 displays, at A92, the reception-oriented screen indicated by the screen data transmitted from the server device 10. The reception terminal 30 displays, for example, the reception-oriented reservation screen C3 shown in FIG. 10.

[0141] When, for example, the receptionist receives a call from a patient to change the schedule, the receptionist causes the reservation screen C3 for reception to be displayed in order to change the patient's schedule. When the receptionist selects the reservation area to be changed, the details of the medical appointment shown in the selected reservation area as described in FIG. 10 are displayed in the input fields E31 to E36. The receptionist changes the content displayed in the input fields E31 to E36 and performs an operation of pressing the reservation change button B32. The reception terminal 30 receives these operations as reservation change operations at A93 and transmits reservation change data indicating the content of the reservation changed by the reservation change operation to the server device 10.

[0142] Since the medical appointment for which the reservation change is requested is neither a linked destination nor a linked reservation, the server device 10 performs, at A94, a process of storing the change content indicated by the reservation change data in the medical information database DB1 as a medical appointment change process. When the server device 10 performs the change process, the server device 10 transmits the change result to the reception terminal 30. The reception terminal 30 displays, at A95, the transmitted change result.

[0143] Also, the server device 10 generates, at A96, notification data for notifying the patient (the patient who made the changed medical appointment) of the change result and transmits the notification data to the patient terminal 20 of that patient. The patient terminal 20 displays, at A97, the reservation change notification indicated by the transmitted notification data. In this way, when there is a change in the content of the medical appointment, the server device 10 executes a notification process of notifying the terminal of the patient (the patient terminal 20 of that patient) who will receive the medical treatment based on the medical appointment that there has been a change.

[0144] When the medical appointment for which a reservation change is requested is a linked destination or a linked reservation, the following reservation change process will be performed. For example, in A92, when the reservation screen C3 for reception after the linked reservation described in FIG. 11 is displayed, it becomes possible to change the medical information S41 and S51 in the respective reservation areas H341 and H351 associated by the link process. When any of the medical information S41 and S51 is changed, since the medical appointment for which the reservation change is requested is a linked reservation, the server device 10 reads out all the medical appointments associated with the medical appointment for which the change is requested from the medical information database DB1 in A101.

[0145] Next, the server device 10 executes a change process for all the read medical appointments, that is, all the medical appointments associated by the link process, in A102. For example, when the medical treatment time of the medical information S41 is changed from 12:00 - 12:30 to 13:00 - 13:30, one hour later, the server device 10 makes a change to shift the medical treatment time of the medical information S51 by the same amount of time as the medical information S41 (changing 13:00 - 14:00 to 14:00 - 15:00, shifting one hour later).

[0146] Also, when the corresponding staff of the medical information S41 is changed from doctor D1 to doctor D2, the server device 10 also changes the corresponding staff of the medical information S51 from doctor D1 to doctor D2. In this way, the server device 10 makes the same changes to the medical appointments associated with that medical appointment as the changes made to the medical appointment by the reception staff. When the change process is completed, the processes of A103 (display of change results), A104 (generation of notification data), and A105 (notification of reservation change) are performed in the same way as A95, A96, and A97.

[0147] In this way, when a change is made to one of two or more medical appointments associated by link processing in the server device 10, the server device 10 executes, as reservation display processing, processing for reflecting the change in the other medical appointments among the two or more medical appointments and displaying them in the schedule table. By automatically reflecting the change in the linked reservation in this way, it is possible to reduce the labor of reservation changes compared to the case where the user makes changes to both of the two or more medical appointments associated by link processing.

[0148] In the example of FIG. 29, the reservation was changed by the reception staff, but the reservation may also be changed by the patient operating the patient terminal 20. In that case, the reservation result is displayed on the patient terminal 20, and a notification of the reservation change is sent to the reception terminal 30. However, for linked reservations, since the patient does not know the details of the reservation (the corresponding staff and equipment used for the linked reservation, etc.), it may be made impossible to change the reservation from the patient terminal 20 (changing a normal medical appointment is of course possible).

[0149] Further, when the server device 10 automatically reflects a change in a linked reservation as described above, if the facilities and medical staff are quite booked with reservations and there will be a gap of a certain time (for example, one hour or more) or more between the linked medical appointment and the linked reservation after reflecting the change, the server device 10 may notify to that effect and notify to correct the change content.

[0150] Further, when the medical appointment is changed as shown in FIG. 29, the server device 10 notifies the patient's terminal (patient terminal 20) that such a change has occurred. On the other hand, when one of two or more medical appointments associated by link processing is input from the patient's terminal (patient terminal 20) and another of the two or more medical appointments is input from the medical institution's terminal (reception terminal 30), as shown in FIG. 4, the server device 10 does not notify that the input has been made (in the example of FIG. 4, after the link processing is executed at A32, the schedule table is displayed on the patient terminal 20 based on the patient's operation, but no notification is sent from the server device 10).

[0151] Even if a link reservation is made, for the patient, it is still necessary to visit the hospital for medical treatment, and detailed medical treatment information such as the equipment to be used and the corresponding staff is not originally presented to the patient. Therefore, even if the patient is notified that a link reservation has been made, only the fact that the medical treatment time has become a little longer is conveyed, which may be rather troublesome. Therefore, by preventing the execution of the notification process in the above case, it is possible to reduce the annoyance caused by the notification to the patient compared to the case where the patient terminal 20 is notified during link reservation.

[0152] Next, the cancellation of the medical appointment will be explained. FIG. 30 is an activity diagram showing an example of the reservation cancellation process. In the example of FIG. 30, the case where the medical appointment is cancelled by an operation on the reception terminal 30 will be explained. First, the server device 10 performs the display process of the reception-oriented screen at A111, and the reception terminal 30 displays the reception-oriented screen indicated by the screen data transmitted from the server device 10 at A112. The reception terminal 30 displays, for example, the reception-oriented reservation screen C3 shown in FIG. 10.

[0153] When the reception staff selects the reservation area to be cancelled, the details of the medical reservation shown in the selected reservation area are displayed in the input fields E31 to E36 as described in FIG. 10. After the reception staff confirms the content displayed in the input fields E31 to E36 and confirms that it is the target for cancellation, the reception staff performs an operation of pressing the cancel button B33. The reception terminal 30 accepts these operations as a reservation cancellation operation at A113, and transmits cancellation target data indicating the medical reservation to be cancelled by the reservation cancellation operation to the server device 10.

[0154] When the server device 10 receives the cancellation target data, the process to be performed next changes depending on whether the medical appointment for which cancellation is requested is a linked appointment. If the medical appointment for which cancellation is requested is neither a linked destination nor a linked appointment, since there is no other medical appointment associated with that medical appointment, in A114, the server device 10 performs, as the medical appointment cancellation process, the process of deleting only the medical appointment indicated by the cancellation target data from the medical information database DB1. Note that the server device 10 may perform, as the cancellation process, the process of storing a cancellation flag in association with the medical appointment to be cancelled.

[0155] When the server device 10 performs the cancellation process, it transmits the cancellation result to the reception terminal 30. In A115, the reception terminal 30 displays the transmitted cancellation result. In this way, when a medical appointment is cancelled, the server device 10 executes the cancellation process for cancelling that medical appointment.

[0156] Also, when the medical appointment for which cancellation is requested is a linked destination or a linked appointment, since there are other medical appointments associated with that medical appointment, in A121, the server device 10 reads out all the medical appointments associated with the medical appointment to be cancelled from the medical information database DB1. Next, in A122, the server device 10 executes the cancellation process for all the read medical appointments, that is, all the medical appointments associated by the linking process.

[0157] For example, when the medical information S41 is cancelled, the server device 10 performs the process of cancelling the medical information S51 associated with the medical information S41. Also, when the medical information S51 is cancelled, the server device 10 performs the process of cancelling the medical information S41 associated with the medical information S51. The server device 10 transmits the cancellation result to the reception terminal 30, and in A123, the reception terminal 30 displays the transmitted cancellation result.

[0158] In this way, when one of two or more medical appointments associated by link processing is canceled in the server device 10, the server device 10 executes a process of canceling the other medical appointments among those two or more medical appointments. According to such an aspect, compared with the case where it is necessary to cancel both of two or more medical appointments associated by link processing manually (by the user's own operation), the labor of reservation cancellation can be reduced.

[0159] Further, even if there is a time interval between the end time of a medical appointment and the start time of the next medical appointment, the server device 10 executes link processing for those two or more medical appointments. For example, in the example of FIG. 11, the server device 10 may execute link processing for associating a medical appointment with a medical time of 13:30 - 14:30 with the medical information S41. According to such an aspect, compared with the case where link reservation is enabled only for medical appointments that are temporally continuous, the degree of freedom of reservation can be improved. Specifically, for example, even if the reservation of equipment or medical staff is filled at the time immediately after the medical appointment, a link reservation can be made at a time after those reservations end.

[0160] <Example: Link Reservation> In the example of FIG. 11, for the linked medical appointment, a link reservation with a different medical time, medical menu, and equipment used was made, but the present invention is not limited to this, and a link reservation with a different responsible staff may be made.

[0161] Further, in the above embodiment, the server device 10 performs link processing between medical appointments on the same day, but the present invention is not limited to this, and link processing may be performed between medical appointments on different days. However, since accounting cannot be performed until the last medical treatment ends when a link reservation is made, it is desirable to limit the period. Therefore, the server device 10 may execute link processing when all of two or more medical appointments are within a predetermined period.

[0162] The specified period is, for example, in the embodiment, the period of "the same day". In that case, for example, in the example of FIG. 11, even if the link reservation button B34 is operated, the server device 10 cannot associate the medical appointment on the same day with the medical appointment on the next day. According to such an aspect, it is possible to summarize the medical record information and accounting processing only for the medical treatment within the specified period.

[0163] The reservation forms include face-to-face and online. When one or more of the two or more medical appointments are online medical appointment reservations, the server device 10 may not execute link processing for those two or more medical appointments. For example, when a medical appointment with an online medical treatment format is selected, the server device 10 may disable the operation of the link reservation button B34 shown in FIG. 11, or when the link reservation button B34 is operated while an online medical appointment is selected, display "Link reservation is not possible" and not execute the link processing.

[0164] Link reservation is performed, for example, when it is necessary to use another facility for treatment immediately after receiving consultation or to change the corresponding staff during the treatment, based on the patient's medical condition. On the other hand, in online medical treatment, usually one medical staff is in charge and no facility is used, so there is no need to perform link reservation. Therefore, by not executing link processing when online medical treatment is included, it is possible to suppress confusion during the reservation of online medical treatment compared to the case where link reservation is possible even for online medical treatment.

[0165] Also, in the embodiment, the server device 10 executed the process of associating two pieces of medical information as a link process, but it is not limited to this. The server device 10 may execute, for example, a process of associating three or more pieces of medical information of the same patient with each other as a link process. Also in that case, the server device 10 outputs the medical record information output in the first medical treatment among the three or more medical treatments performed based on those three or more medical reservations also in the next medical treatment, and outputs the same medical record information also in the subsequent medical treatment, and executes the process of outputting the medical record information as a medical record output process. Further, the server device 10 outputs accounting information that summarizes into one the medical treatments performed based on three or more medical reservations associated with each other.

[0166] <Example: Link operation> In the embodiment, the server device 10 accepts, as a link operation, an operation of selecting one piece of medical information, an operation of pressing the link reservation button B34 shown in FIG. 11 etc., and an operation of inputting a new medical reservation, and executes the process of associating the existing medical reservation and the newly input medical reservation as a link process, but the link operation is not limited to this.

[0167] For example, when two or more pieces of medical information of the same patient are input separately, the server device 10 may accept, as a link operation, an operation of selecting those two or more pieces of medical information and an operation of pressing the link reservation button B34 performed thereafter, and execute a link process of associating the selected medical information.

[0168] When medical information is input separately, even if it is the same patient, since the medical information and the patient information are stored separately, not only the medical information ID but also the medical record ID and the accounting ID are stored as separate IDs. Therefore, the server device 10 changes the medical record ID and the accounting ID associated with the medical information of the link reservation to the medical record ID and the accounting ID associated with the medical information of the link destination, with the earlier medical reservation in terms of time as the link destination and the later medical reservation in terms of time as the link reservation.

[0169] Also, when medical treatment information is input separately, since the basic information and medical record information are stored in the patient information of the linked reservation, the server device 10 deletes the basic information (excluding the patient name and patient ID) and the medical record information (excluding the medical record ID) from the patient information of the linked reservation so that the information does not overlap between the linked destination and the linked reservation. By doing so, as in the embodiment, the same medical record information can be used for the medical treatment at the linked destination and the medical treatment of the linked reservation.

[0170] Also, at the time when the link operation is performed, since neither the medical treatment at the linked destination nor the medical treatment of the linked reservation has been performed yet, accounting information other than the accounting ID is not stored. Then, the server device 10 does not accept accounting operations until the medical treatment of the linked reservation is completed, so that, as in the embodiment, the output of accounting information is also performed collectively.

[0171] Also, when two or more medical treatment reservations are made for the same patient on the same day, the server device 10 may accept the operation of inputting the second and subsequent medical treatment reservations as a link operation, and execute a link process of associating two or more pieces of medical treatment information of the same patient on the same day that are input. The storage of medical record information and the output of accounting information in this case may be performed in the same manner as in the embodiment. In this case, two or more medical treatment reservations for the same patient on the same day will always be associated with each other. In short, any operation may be used as the link operation as long as it is an operation that can be determined to be two or more medical treatment reservations associated with each other and a linked reservation.

[0172] <Example: Reservation change> In the embodiment, the server device 10 executed status display processing for displaying the status information of the patient who made the medical treatment reservation together with the medical treatment reservation of the patient in the schedule table. The status information of the patient is information indicating the status before medical treatment or the status after medical treatment. "Not yet" shown in FIG. 11 is an example of the status before medical treatment, and "In progress" and "Completed" are examples of the status after medical treatment. Strictly speaking, "During treatment" includes both the situation before medical treatment and the situation after medical treatment, but here, "During treatment" is regarded as an example of the status after medical treatment.

[0173] When the server device 10 is instructed to change the content of the medical appointment, if the status information indicates the status before the medical treatment (for example, "not yet") and there is an instruction to change the content of the medical appointment, the server device 10 executes a change process to accept the changed content according to the instruction. However, if the status information indicates the status after the medical treatment (for example, "medical treatment", "calculation", "completed"), the server device 10 may not execute the change process. If the reservation is changed after the medical treatment, for example, the accounting process that has progressed halfway may be interrupted, which may cause confusion. By determining whether to execute the change process according to the status, it is possible to suppress the confusion caused by the reservation change as compared with the case where the change process is always executed.

[0174] <Example: Overall Configuration> In the embodiment, the server device 10 executes the process of reading and storing the medical record information in the patient information database DB2 as the medical record process, but it is not limited to this. The server device 10 may, for example, access an external electronic medical record system and execute the process of exchanging medical record information as the medical record process. Also, in the embodiment, the server device 10 executes the calculation, display, and storage of the patient's treatment cost in the patient information database DB2 as the accounting process, but it is not limited to this. The server device 10 may, for example, execute the calculation and output of the medical treatment fee (the treatment cost paid by medical insurance) as the accounting process.

[0175] The overall configuration shown in FIG. 1 is an example and is not limited thereto. For example, the server device 10 may be distributed among two or more devices, or may be replaced by a cloud computing system. Also, the medical information database DB1 and the patient information database DB2 may be an integrated single database, or each may be divided into two or more databases. Further, each database may be stored in an external device other than the server device 10.

[0176] The aspects of the above-described embodiments were the server device 10 and the medical treatment management system 1, that is, the information processing device and the information processing system, but it may also be an information processing method. The information processing method is a method including steps in which a computer executes each process executed by the information processing device or the information processing system. Further, the aspects of the above-described embodiments may also be a program. The program causes a computer to execute each process executed by a similar information processing device or information processing system.

[0177] <Appendix> Furthermore, it may be provided in each of the aspects described below.

[0178] (1) A program that causes a computer that manages medical treatment reservations of patients to execute a link process of associating two or more medical treatment reservations of the same patient based on a user operation, and an accounting output process of outputting accounting information according to the result of medical treatment performed based on the medical treatment reservation, wherein the accounting output process outputs the accounting information summarized into one for the medical treatment performed based on the two or more medical treatment reservations associated with the medical treatment reservation for which accounting is to be performed when the medical treatment reservation for which accounting is to be performed is the medical treatment reservation on which the link process has been performed.

[0179] According to such an aspect, the accounting information of two or more medical treatments can be summarized into one.

[0180] (2) In the program according to (1) above, the link process is a process executed when the user operation is performed from a terminal of a medical institution.

[0181] According to such an aspect, a medical institution can manage whether or not to summarize accounting information.

[0182] (3) In the program according to (1) or (2) above, the link process is a process executed when all of the two or more medical treatment reservations are reservations within a predetermined period.

[0183] According to such an aspect, accounting information can be summarized only for medical treatments during a predetermined period.

[0184] (4) In the program according to any one of (1) to (3) above, the link process is a process that is executed for two or more medical appointments even if there is a time interval between the end time of one medical appointment and the start time of the next medical appointment.

[0185] According to such an aspect, the degree of freedom of reservation can be improved.

[0186] (5) In the program according to any one of (1) to (4) above, the computer is caused to execute a reservation display process for displaying the medical appointment on a schedule table, and the reservation display process is a process for displaying the two or more medical appointments in a manner different from other medical appointments.

[0187] According to such an aspect, it is possible to easily grasp medical appointments for which accounting information is summarized into one.

[0188] (6) In the program according to any one of (1) to (5) above, the computer is caused to execute a reservation display process for displaying the medical appointment on a schedule table and a status display process for displaying status information of a patient who has made the medical appointment together with the medical appointment of the patient on the schedule table, and the status display process is a process for displaying the same status information for patients receiving medical treatment based on two or more medical appointments for which the link process has been executed in any of the two or more medical appointments.

[0189] According to such an aspect, it is possible to easily grasp medical appointments for which accounting information is summarized into one.

[0190] (7) In the program according to (6) above, the status information of the patient is information indicating the status before medical treatment or the status after medical treatment. When the status information indicates the status before medical treatment and there is an instruction to change the content of the medical appointment, the computer is made to execute a change process of accepting the changed content according to the instruction. When the status information indicates the status after medical treatment, the change process is not executed. Program.

[0191] According to such an aspect, it is possible to suppress confusion caused by reservation changes.

[0192] (8) In the program according to any one of (1) to (7) above, the computer is made to execute a reservation display process of displaying the medical appointment on a schedule table. The reservation display process is a process of displaying the two or more medical appointments as separate medical appointments on the terminal of a medical institution and displaying the two or more medical appointments as one medical appointment on the terminal of a patient. Program.

[0193] According to such an aspect, it is possible to suppress the patient from being confused while transmitting accurate information to the medical institution.

[0194] (9) In the program according to (8) above, when one of the two or more medical appointments is input from the terminal of the patient and another of the two or more medical appointments is input from the terminal of the medical institution where the medical treatment of the patient is performed, the computer does not notify that the input has been made. However, when there is a change in the content of the medical appointment, the computer is made to execute a process of notifying the terminal of the patient who will receive the medical treatment based on the medical appointment that there is such a change. Program.

[0195] According to such an aspect, it is possible to reduce the annoyance caused by notifications.

[0196] (10) In the program according to any one of (1) to (9) above, when the medical appointment is canceled on the computer, the computer is caused to execute a cancellation process for canceling the medical appointment, and when one of the two or more medical appointments is canceled in the cancellation process, the cancellation process is a process of canceling the other medical appointments among the two or more medical appointments.

[0197] According to such an aspect, the trouble of canceling the reservation can be reduced.

[0198] (11) In the program according to any one of (1) to (10) above, on the computer, a reservation display process for displaying the medical appointment on a schedule table is executed, and when a change is made to one of the two or more medical appointments in the reservation display process, the reservation display process is a process of reflecting the change to the other medical appointments and displaying them on the schedule table.

[0199] According to such an aspect, the trouble of changing the reservation can be reduced.

[0200] (12) On the computer, a generation process for generating medical information indicating a medical appointment of a patient and an accounting output process for outputting accounting information according to the result of the medical treatment when the medical treatment is performed based on the medical appointment indicated by the generated medical information are executed. The generation process is a process of generating at least one of first medical information in which two or more medical appointments are not associated and second medical information in which two or more medical appointments are associated. The accounting output process outputs the accounting information about the medical treatment when the medical treatment based on the medical appointment indicated by the generated first medical information is performed, and outputs the accounting information summarized into one for the two or more medical treatments when two or more medical treatments based on the two or more medical appointments indicated by the generated second medical information are performed.

[0201] According to such an aspect, the accounting information for two or more medical treatments can be summarized.

[0202] (13) An information processing system for managing medical appointments of patients, which executes a link process for associating two or more medical appointments of the same patient based on a user operation, and an accounting output process for outputting accounting information according to the result of medical treatment performed based on the medical appointment, wherein when the medical appointment for which accounting is to be performed is the medical appointment on which the link process has been performed, the accounting output process is a process for outputting the accounting information that summarizes into one the medical treatments performed based on the two or more medical appointments associated with the medical appointment.

[0203] According to such an aspect, the accounting information of two or more medical treatments can be summarized into one.

[0204] (14) A method for causing a computer to manage medical appointments of patients, which includes a link process step for associating two or more medical appointments of the same patient based on a user operation, and an accounting output process step for outputting accounting information according to the result of medical treatment performed based on the medical appointment, wherein when the medical appointment for which accounting is to be performed is the medical appointment on which the link process step has been performed, the accounting output process step is a step for outputting the accounting information that summarizes into one the medical treatments performed based on the two or more medical appointments associated with the medical appointment.

[0205] According to such an aspect, the accounting information of two or more medical treatments can be summarized into one. Of course, this is not the limit. Also, the above-described embodiments and modifications may be arbitrarily combined and implemented.

[0206] Finally, although various embodiments of the present invention have been described, these are presented as examples and are not intended to limit the scope of the invention. The novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. The embodiments and their modifications are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and its equivalents.

Description of Symbols

[0207] 1: Medical management system 2: Communication line 10: Server device 11: Control unit 20: Patient terminal 21: Control unit 30: Reception terminal 31: Control unit 40: Doctor terminal 41: Control unit

Claims

1. On a computer that manages medical appointments for patients, a linking process that associates two or more medical appointments of the same patient based on a user operation, and an accounting output process that outputs accounting information according to the result of medical treatment conducted based on the medical appointment are executed, wherein when the medical appointment for accounting is the medical appointment for which the linking process has been performed, the accounting output process is a process of outputting the accounting information that consolidates into one the medical treatments conducted based on the two or more medical appointments associated with the medical appointment. Program.

2. In the program according to Claim 1, the linking process is a process that is executed when the user operation is performed from a terminal of a medical institution. Program.

3. In the program according to Claim 1, the linking process is a process that is executed when all of the two or more medical appointments are appointments within a predetermined period. Program.

4. In the program according to Claim 1, the linking process is a process that is executed for the two or more medical appointments even if there is a time interval between the end time of one medical appointment and the start time of the next medical appointment. Program.

5. In the program according to Claim 1, the computer is caused to execute a reservation display process that displays the medical appointment in a schedule table, wherein the reservation display process is a process of displaying the two or more medical appointments in a manner different from other medical appointments. Program.

6. In the program according to Claim 1, the computer is caused to execute a reservation display process that displays the medical appointment in a schedule table and a status display process that displays status information of the patient who has made the medical appointment together with the medical appointment of the patient in the schedule table, wherein the status display process is a process of displaying the same status information for the patient who receives medical treatment based on the two or more medical appointments for which the linking process has been executed in any of the two or more medical appointments. Program.

7. In the program according to Claim 6, the status information of the patient is information indicating a status before medical treatment or a status after medical treatment, and when the status information indicates the status before medical treatment and there is an instruction to change the content of the medical appointment, the computer is caused to execute a change process of accepting the changed content according to the instruction. ​ ​ ​ When the status information indicates the status after the medical treatment, the change process is not executed. Program.

8. In the program according to claim 1, Cause the computer to Execute a reservation display process for displaying the medical appointment on the schedule, The reservation display process is a process of displaying the two or more medical appointments as separate medical appointments on the terminal of the medical institution and as one medical appointment on the patient's terminal. Program.

9. In the program according to claim 8, Cause the computer to When one of the two or more medical appointments is input from the patient's terminal and another medical appointment among the two or more medical appointments is input from the terminal of the medical institution where the patient's medical treatment is performed, do not notify that the input has been made, When there is a change in the content of the medical appointment, execute a process of notifying the patient's terminal receiving the medical treatment based on the medical appointment that there has been such a change. Program.

10. In the program according to claim 1, Cause the computer to When the medical appointment is canceled, execute a cancellation process for canceling the medical appointment, The cancellation process is a process of canceling the other medical appointments among the two or more medical appointments when one of the two or more medical appointments is canceled. Program.

11. In the program according to claim 1, Cause the computer to Execute a reservation display process for displaying the medical appointment on the schedule, The reservation display process is a process of reflecting the change on the other medical appointments and displaying them on the schedule when a change is made to one of the two or more medical appointments. Program.

12. Cause the computer to Execute a generation process for generating medical information indicating the patient's medical appointment and An accounting output process for outputting accounting information according to the result of the medical treatment when the medical treatment is performed based on the medical appointment indicated by the generated medical information And cause it to execute, The generation process is A process of generating at least one of the first medical information in which two or more medical appointments are not associated and The second medical information in which two or more medical appointments are associated, The accounting output process is When the medical treatment based on the medical appointment indicated by the generated first medical information is performed, output the accounting information for the medical treatment, When two or more medical treatments based on two or more medical appointments indicated by the generated second medical information are performed, it is a process of outputting the accounting information summarized into one for the two or more medical treatments. Program.

13. An information processing system for managing a patient's medical appointment, a link process for associating two or more medical appointments of the same patient based on a user operation, and an accounting output process for outputting accounting information according to the result of the medical treatment performed based on the medical appointment, are executed. When the medical appointment for accounting is the medical appointment for which the link process has been performed, the accounting output process is a process of outputting the accounting information summarized into one for the medical treatments performed based on the two or more medical appointments associated with the medical appointment. Information processing system.

14. A method for causing a computer that manages a patient's medical appointment to execute, a link process step for associating two or more medical appointments of the same patient based on a user operation, and an accounting output process step for outputting accounting information according to the result of the medical treatment performed based on the medical appointment, is provided. When the medical appointment for accounting is the medical appointment for which the link process step has been performed, the accounting output process step is a step of outputting the accounting information summarized into one for the medical treatments performed based on the two or more medical appointments associated with the medical appointment. Method.

Images