JP6062904B2 - Program, system, information processing method - Google Patents

Description

  The present invention relates to a program, a system, and an information processing method for managing appointments of doctors, comedies, and medical devices necessary for medical practice.

  Patent Literature 1 discloses a radiation therapy scheduling system for performing treatment scheduling for a patient who receives radiation therapy.

JP 2000-222507 A

  However, the system described in Patent Document 1 cannot perform appropriate reservation management for doctors, comedies, and medical devices.

  In one aspect, an object of the present invention is to provide an information processing program or the like that can individually set appointment times for doctors, comedies, and medical devices necessary for medical practice.

The program according to the present invention obtains the scheduled date and time of medical practice from a computer, obtains designation of participation of a doctor and a medical device and designation of use of a medical device, and designates participation within the range of the scheduled date of implementation. Obtained the scheduled date and time of participation of doctors and comedians who acquired the medical device, and the scheduled date and time of use of medical devices for which the designation of use was obtained, and obtained the planned date and time of participation and designation of use of the doctors and comedies who obtained the designation of participation The presence or absence of duplication of the scheduled use date and time of the medical device is determined by referring to a reservation database that records the scheduled date and time of participation of the doctor and the medical device and the scheduled use date and time of the medical device . If it is determined that none of the duplicates exist, the doctor or comedian who obtained the designation for participation Pressurizing the scheduled date and time, the medical devices and acquired using scheduled date and time to get the specification of use and output to the reservation database, if it is determined that there is the overlapping reservation doctor or co Medical, acquired participation date and time It is determined whether or not the start date and time and the start date and time of the duplicate reservation recorded in the reservation database match, and if it is determined that the start date and time do not match, designation of participation is made. When the acquired doctor or comedy, the acquired scheduled participation date and time, the medical device that acquired the designation of use and the acquired scheduled use date and time are output to the reservation database, and it is determined that the start dates and times match, A process of outputting information indicating duplication is executed.

  In one aspect, appointment times for doctors, comedies and medical devices necessary for the medical practice can be set individually within the range of the scheduled date and time for the medical practice.

It is explanatory drawing which shows the hardware constitutions of an information processing system. It is a block diagram which shows the hardware group of an operation terminal. It is a block diagram which shows the hardware group of a server. It is explanatory drawing which shows the initial screen of an information processing system. It is explanatory drawing which shows the image of a task list display screen. It is explanatory drawing which shows the record layout of reservation DB. It is explanatory drawing which shows the record layout of reservation DB. It is explanatory drawing which shows the record layout of reservation DB. It is explanatory drawing which shows the record layout of reservation DB. It is explanatory drawing which shows the record layout of task DB. It is explanatory drawing which shows one task record in task DB. It is explanatory drawing which shows the record layout of patient DB. It is explanatory drawing which shows the record layout of use apparatus DB. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is explanatory drawing which shows the image of a task input screen. It is a flowchart which shows the process sequence of information processing system. It is a flowchart which shows the process sequence of a task input. It is a flowchart which shows the process sequence of a time contradiction check. It is a flowchart which shows the process sequence of a time contradiction check. It is a flowchart which shows the process sequence of a time contradiction check. It is a flowchart which shows the process sequence of automatic setting. It is a flowchart which shows the process sequence of a double booking check. It is a flowchart which shows the process sequence of a task record preservation | save. It is a flowchart which shows the process sequence of reservation DB recording. It is a flowchart which shows the process sequence of reservation DB recording. 10 is a flowchart illustrating a processing procedure of the information processing system according to the second embodiment. 10 is a flowchart illustrating a processing procedure of the information processing system according to the second embodiment. FIG. 10 is an explanatory diagram illustrating an initial screen of the information processing system according to the third embodiment. FIG. 10 is an explanatory diagram illustrating an image of a task input screen according to the third embodiment. FIG. 10 is an explanatory diagram illustrating an image of a screen according to a fourth embodiment. FIG. 10 is an explanatory diagram illustrating an image of a screen according to a fourth embodiment. 10 is a flowchart illustrating a processing procedure of the information processing system according to the fourth embodiment. 10 is a flowchart illustrating a processing procedure of the information processing system according to the fourth embodiment. It is explanatory drawing which shows the record layout of the patient database of Embodiment 5. FIG. 10 is an explanatory diagram illustrating an image of a screen according to a fifth embodiment. FIG. 20 is an explanatory diagram showing a record layout of a device-in-use DB according to Embodiment 6. FIG. 20 is an explanatory diagram showing an image of a screen according to a sixth embodiment. FIG. 20 is an explanatory diagram showing an image of a screen according to a seventh embodiment. It is explanatory drawing which shows the image of reservation DB of Embodiment 9. FIG. It is explanatory drawing which shows the image of reservation DB of Embodiment 9. FIG. FIG. 38 is an explanatory diagram showing an image of a task input screen according to the ninth embodiment. FIG. 38 is an explanatory diagram showing an image of a task input screen according to the ninth embodiment. It is explanatory drawing which shows the image of reservation DB of Embodiment 9. FIG. 25 is a flowchart illustrating a processing procedure of the information processing system according to the ninth embodiment. FIG. 38 is a flowchart illustrating a processing procedure of a double booking check according to the ninth embodiment. FIG. 38 is a flowchart illustrating a processing procedure of a double booking check according to the ninth embodiment. FIG. 38 is a flowchart illustrating a processing procedure for reservation DB recording according to the ninth embodiment. FIG. FIG. 38 is a flowchart illustrating a processing procedure for reservation DB recording according to the ninth embodiment. FIG. It is explanatory drawing which shows the image of reservation DB of Embodiment 10. FIG. FIG. 38 is a flowchart showing a processing procedure for reservation DB recording according to the tenth embodiment. FIG. 38 is a flowchart showing a processing procedure for reservation DB recording according to the tenth embodiment.

[Embodiment 1]
FIG. 1 is an explanatory diagram showing a hardware configuration of the information processing system 4.

  As shown in FIG. 1, the information processing system 4 includes a first information processing apparatus 1 that inputs and outputs a reservation, and reservation contents input from the first information processing apparatus 1 with reference to a reservation database (hereinafter referred to as DB). This is a configuration in which a second information processing device 2 that determines whether there is an overlap with an existing reservation is connected via a network 3. The information processing system 4 according to the first embodiment is a system that manages a reservation status of a person such as a doctor or a comedy or a medical device such as a testing device or a treatment device in a medical institution. The medical device includes an operating room in which a plurality of medical devices such as a surgical light, an operating table, and a Schaukasten are combined. Comedy is a general term for various medical staff such as clinical technologists, clinical radiographers, clinical engineering technicians, and sonographers.

  The first information processing apparatus 1 is a desktop personal computer, a notebook personal computer, a tablet, a smartphone, a mobile phone, a wearable terminal, a dedicated terminal for the information processing system, or the like. Various terminal devices can be used according to the work of the user who performs the operation and the work environment. In the following description, the first information processing apparatus 1 is referred to as the operation terminal 1.

  The second information processing apparatus 2 is a desktop personal computer, a notebook personal computer, an application and database server virtualized using PaaS (Platform as a Service) on the cloud. In the following description, the second information processing apparatus 2 is referred to as a server 2.

  The network 3 is an in-hospital network inside a medical institution, a regional medical cooperation network that connects medical institutions in a certain area, the Internet, or the like. Take information security measures such as encryption as necessary.

  In the present embodiment, a medical practice plan input to the operation terminal 1 is sent to the server 2 via the network 3, and when there is an overlap of appointments of doctors or the like with reference to the appointment DB 253, information indicating that is shown. For example, the program is output to the operation terminal 1 via the network 3.

  FIG. 2 is a block diagram illustrating a hardware group of the operation terminal 1. As shown in FIG. 2, the operation terminal 1 includes a first calculation control unit 11, a first main storage unit 12, a first input unit 13, a first display unit 14, a first large capacity storage unit 15, a first communication unit 16, and The first clock unit 17 is connected via the first bus 18.

  The first arithmetic control unit 11 is a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or the like of the operation terminal 1. The first main storage unit 12 is an SRAM (Static RAM), a DRAM (Dynamic RAM), a flash memory, or the like of the operation terminal 1. The first main storage unit 12 temporarily stores information necessary during the processing performed by the first calculation control unit 11 and a program being executed by the first calculation control unit 11.

  The first input unit 13 is the keyboard, mouse, touch panel, pen tablet, voice input device, gesture input device, or the like of the operation terminal 1. When inputting a large amount of data at once, a disk drive capable of reading and writing a memory card, a network adapter, or the like can be used. The first display unit 14 is a liquid crystal display, an organic EL (Electro Luminescence) display, a head mounted display, a printer, or the like of the operation terminal 1.

  The first mass storage unit 15 is a hard disk, a semiconductor memory disk, or the like of the operation terminal 1. The first large-capacity storage unit 15 stores an operation terminal control program 151 to be executed by the first arithmetic control unit 11 and various data necessary for executing the operation terminal control program 151.

  The first communication unit 16 is a network adapter that performs transmission / reception of data between the operation terminal 1 and the network 3 in a wired or wireless manner. The first clock unit 17 is a clock that provides the current date and time to the first calculation control unit 11. It is desirable to automatically synchronize with Japan Standard Time via the network 3.

  FIG. 3 is a block diagram showing a hardware group of the server 2. As shown in FIG. 3, the server 2 includes a second calculation control unit 21, a second main storage unit 22, a second input unit 23, a second display unit 24, a second large capacity storage unit 25, a second communication unit 26, and a second communication unit 26. Two clock units 27 are connected via the second bus 28.

  The second arithmetic control unit 21 is a CPU of the server 2 or the like. The second main storage unit 22 is the SRAM, DRAM, flash memory, or the like of the server 2. The second main storage unit 22 temporarily stores information necessary during the processing performed by the second calculation control unit 21 and a program being executed by the second calculation control unit 21.

  The second input unit 23 is the keyboard, mouse, touch panel, pen tablet, voice input device, gesture input device, or the like of the server 2. The second display unit 24 is a liquid crystal display, an organic EL (Electro Luminescence) display, a head mounted display, a printer, or the like of the operation terminal 1. When the server 2 is controlled through the network, the second input unit 23 and the second display unit 24 may not be provided.

  The second mass storage unit 25 is a hard disk, a semiconductor memory disk, or the like of the server 2. The second large-capacity storage unit 25 includes a program storage unit and a DB storage unit 252 that store an information processing program 251 to be executed by the second calculation control unit 21. The DB storage unit 252 includes a reservation DB 253, a task DB 254, a used device DB 255, and a patient DB 256. The DB storage unit 252 may be provided in an external disk drive device in a separate housing from the server 2.

  The second communication unit 26 is a network adapter that performs transmission / reception of data between the server 2 and the network 3 in a wired or wireless manner. The second clock unit 27 is a clock that provides the current date and time to the second calculation control unit 21. It is desirable to automatically synchronize with Japan Standard Time via the network 3.

  FIG. 4 is an explanatory diagram showing an initial screen of the information processing system 4. A schedule list field 401 is displayed at about 2/3 of the lower side of the initial screen in FIG. In addition, there are provided a communication item column 428, a message column 427 addressed to an individual, a calendar column that also serves as a date input unit, a column that indicates the current date and time, a column that displays the name of the staff who is working, and a column that displays the name of the doctor scheduled to be on duty It has been. The scroll bar 402, task input instruction button 403, end button 404, display change button 425, ID setting field 431, name setting field 432, and patient information field 433 will be described later.

  In the schedule list column 401, the schedules of doctor A, doctor B, doctor C, laboratory technician D, and radiation technician E in increments of unit time are displayed in a simplified manner. In this embodiment, the unit time is 5 minutes. The leftmost column shows the start time of the time zone in increments of 5 minutes. That is, a schedule from 10:35 to 10:40 is shown in the row described as 10:35 in the leftmost column.

  The doctor's schedule is displayed in three items: patient ID, kana patient name, and content. The patient ID is a unique ID assigned to each patient. The patient name is displayed in kana. This is to avoid the risk of misreading when calling and talking with the patient. The content is a simple display of the content of the planned medical practice. Only the first few characters are displayed to save display space. The schedules of the laboratory technician D and the radiology technician E who are comedies are further simplified, and only the patient ID is displayed. The fact that “999999” is displayed in the patient ID indicates that the schedule in the upper row is continued. On the other hand, “0” displayed in the patient ID indicates that there is no plan.

  As an example, a 5-minute schedule from 10:35 to 10:40 shown in FIG. 4 will be described. Doctor A plans to perform Endoscopic Retrograde Cholangio Pancreatography (ERCP) of Endoscopic Retrograde Cholangio Pancreatography (ERCP) of Mr. Ryoko Yoshida with patient ID “AAAAAA”. Physician B plans to examine “Tanaka Hanako” with patient ID “WA1021”. Physician C plans to perform an operation on Mr. Shirou Matsumoto with patient ID “BBBBBBB”. Laboratory Technician D will continue to make plans for patient ID “DA4567” starting at 10:20. Radiologist E has no plans. Radiologist E has a plan for the patient ID “AAAAAAA” from 10:45. Therefore, doctor A participates in ERCP of Mr. Ryoko Yoshida of patient ID “AAAAAAA” starting at 10:35 from 10:45.

  Note that, by default, setting so that the time zone including the current time is displayed within the fifth line from the top is preferable because the user can easily grasp the real-time situation. In FIG. 4, a scroll bar 402 in the vertical direction is displayed at the right end of the schedule list field 401. Similarly, a horizontal scroll bar may be displayed at the top or bottom of the schedule list field 401.

  FIG. 4 shows an example of two comedies of “inspection engineer D” and “radiation engineer E”, but other occupations and abbreviations may be used. Further, “doctor A” may be displayed with a special field such as “medicine doctor A”. Further, only the personal name may be displayed by omitting the occupation type and the specialized field. Conversely, the specialized name or role may be displayed by omitting the personal name.

  FIG. 5 is an explanatory diagram showing an image of a task list display screen. A reservation status list 421 is displayed in a pop-up at the center of the initial screen in FIG. In the first row of the table showing the title of each item, the doctor, comedical, and medical device are all indicated by one or two alphabetic abbreviations, that is, “A”, “B”, “C” is an abbreviation for doctor A, doctor B, and doctor C, “D” is an abbreviation for laboratory technician D, and “E” is an abbreviation for radiologist E. “OP” stands for OPerating room and means operating room. “ES” is an abbreviation of EndoScope and means an endoscope. “US” is an abbreviation for UltraSonography and means an ultrasonic inspection apparatus. “CT” is an abbreviation for Computed Tomography and means a computed tomography apparatus. “XR” is an abbreviation of X Ray and means an X-ray fluoroscopic imaging apparatus.

  The reservation status list 421 displays a summary of reservations for one medical practice per line. The scheduled date and time of medical practice is indicated by the date at the top of the reservation status list 421 and the start time and end time of each row. The designation of physician or comedian participation and the use of medical devices are indicated by a “o” in each column. “◯” in the doctor or comedy column indicates a doctor or comedy who is accepted to participate. “○” in the column of medical equipment indicates a medical equipment for which use designation is accepted.

  Further, the task ID, patient ID, contents and remarks of the reservation for each medical practice are also displayed. The task ID is a unique ID assigned to each medical practice schedule. However, a task ID is not given to a unit time examination schedule performed by a single doctor. Therefore, the task ID column of such a scheduled row is blank.

  Since the abbreviations are used for compactness, the reservation status can be displayed as a list on the screen of a small device such as a portable terminal. The transition procedure from the initial screen of FIG. 4 to the screen of FIG. 5 will be described later.

  The pop-up position of the reservation status list 421 is not limited to the central portion of the initial screen in FIG. It may pop up at the top of the initial screen and be displayed side by side with the schedule list field 401 at the bottom of the initial screen. Instead of the pop-up display, the initial screen of FIG. 4 may be replaced and displayed. In the case of a so-called multi-monitor environment including a plurality of first display units 14, the initial screen and the reservation status list 421 of FIG. 4 may be displayed on separate first display units 14.

  6 to 9 are explanatory diagrams showing record layouts of the reservation DB 253. FIG. 6 to 9 show one table divided in the horizontal direction. The reservation DB 253 is a DB that records the reservation status of doctors, comedies, and medical devices. The reservation DB 253 includes a date field and a time field, a doctor ID, a doctor B, a doctor C, a laboratory technician D, and a radiographer E, a patient ID field, a content field and a remarks field, and an operating room, endoscope, ultrasound, CT And X-ray fluoroscopy each patient ID field. The ultrasonic wave means an ultrasonic inspection apparatus. X-ray fluoroscopy means an X-ray fluoroscopy apparatus.

  The reservation DB 253 has one reservation record for each unit time. In this embodiment, the unit time is 5 minutes. In the date field, the date targeted by the reservation record is recorded. In the time field, the start time of the unit time targeted by the reservation record is recorded.

  In the patient ID field of the doctor A, the patient ID of the patient who is scheduled to correspond to the doctor A in the unit time targeted by the record is recorded. However, when the same schedule as the previous unit time continues, “999999” is recorded in the patient ID field. In addition, when there is no plan in the unit time targeted by the reservation record, “0” is recorded in the patient ID field. In the content field of the doctor A, the type of medical practice performed by the doctor A of unit time targeted by the record is described. The type of medical practice will be described later. In the remarks field of doctor A, the detailed explanation of the medical action scheduled by doctor A for the unit time covered by the record, the matters to be sent from the person who made the reservation to the person in charge of the execution, etc. are described. . In a record where the patient ID field is “999999” or “0”, the content field and the remarks field are blank. The same applies to the columns after Doctor B.

  In the patient ID field of the operating room, the patient ID of a patient who plans to use the operating room in the unit time targeted by the record is recorded. When the same schedule as the previous unit time continues, “999999” is recorded in the patient ID field. In addition, when there is no plan in the unit time targeted by the reservation record, “0” is recorded in the patient ID field. The same applies to the patient ID fields for endoscopes, ultrasound CT and X-ray fluoroscopy.

  “999999” when the same schedule continues and “0” when no schedule is entered are examples, and other arbitrary values can be assigned. However, a value that is not used is adopted as the patient ID.

  The unit time of the reservation DB 253 is not limited to 5 minutes, and may be 1 minute or 10 minutes. The length of the unit time may be changed depending on the time zone, such as 5 minutes during busy daytime and 15 minutes at night. In addition, the numbers and types of doctors, comedies, and medical devices illustrated in FIG. 4 are examples, and can be arbitrarily set according to the situation. It is also possible to divide the reservation DB 253 into three types: a doctor, a comedy, and a medical device. It is also possible to divide the reservation DB 253 for each department such as surgery, internal medicine, gynecology, ophthalmology, and pediatrics. By dividing the reservation DB 253 for each management department, it is possible to divide the department in charge of DB maintenance when a new employee, a retired person, a newly purchased medical device, or the like occurs.

  The procedure for recording data in the reservation DB 253 will be described later.

  FIG. 10 is an explanatory diagram showing a record layout of the task DB 254. In the task DB 254, a schedule with a task ID is recorded. The task DB 254 includes fields listed below. Task ID field, date field, patient ID field, content field, remarks field, task start time field, task end time field, doctor A participation flag field, doctor A participation start time field, doctor A participation end time field, Doctor B participation flag field, Doctor B participation start time field, Doctor B participation end time field, Doctor C participation flag field, Doctor C participation start time field, Doctor C participation end time field, Laboratory technician D Participation flag field, participation start time field of laboratory technician D, participation end time field of inspection technician D, participation flag field of radiation technician E, participation start time field of radiation technician E, participation end time field of radiation technician E, operating room Field, endoscope Field, ultrasonic field, CT field and the X-ray fluoroscopy field.

  A task ID is recorded in the task ID field. As described above, the task ID is a unique ID assigned for each medical practice schedule. The task ID may be a sequential number in the order of creation, or information such as the creation date / time and creator may be embedded.

  In the date field, the task start time field, and the task end time field, the scheduled execution date and time of the medical practice are recorded as the scheduled start and end dates and times. In the case of a medical practice performed across dates, the date field records the date of the start date. Note that the date field may be omitted when values indicating the date and time are used in the task start time field and the task end time field.

  In the patient ID field, a patient ID of a patient who receives a medical practice is recorded. In the content field and the remarks field, the description items of the corresponding content field and remarks field in the reservation DB 253 are copied.

  In the participation flag field of the doctor A, a participation flag indicating whether or not the doctor A participates in the medical practice is recorded. FIG. 10 shows that a participation flag in which “◯” in the participation flag field means “participate” is set. In the participation start time field and the participation end time field of the doctor A, the time when the doctor A participates in the medical practice and the time when the participation ends are recorded. When the doctor A participation flag is not set, the participation start time and the participation end time are left blank. The same applies to the fields of doctor B, doctor C, laboratory technician D, and radiologist E.

  In the operating room field, a use flag indicating whether or not the operating room is used is recorded. In FIG. 10, “O” in the operating room field indicates that a use flag is set which means “use” the operating room. The same applies to the endoscope field, the ultrasound field, the CT field, and the X-ray fluoroscopy field.

  In FIG. 10, for each medical device from the operating room to the X-ray fluoroscopy, only the use flag is recorded on the assumption that reservation is made over the entire time from the task start time to the task end time. The use start time and use end time may be recorded as in the case of.

  FIG. 11 is an explanatory diagram showing one task record in the task DB 254. The recorded contents of the task record will be described with reference to FIG. The scheduled implementation date and time of the medical action with the task ID “0AA05” is from 10:35 to 11:15 on June 18, 2014. The patient ID of the patient who receives this medical practice is “AAAAAA”, and the content of the medical practice is ERCP. Physicians and comedians who are designated to participate in this medical practice are Doctor A and Radiologist E. Physician A participates throughout this medical practice. That is, doctor A's scheduled participation date is from 10:35, which is the participation start time on June 18, 2014, to 11:15, which is the participation end time. The scheduled participation date and time for Radiologist E is from 10:45, which is the participation start time on June 18, 2014, to 11:15, which is the participation end time. Medical devices that have been designated for use in this medical practice are endoscopes and X-ray fluoroscopy. The scheduled use date and time of the endoscope and X-ray fluoroscopy is from 10:35 to 11:15 on June 18, 2014, which is the same as the scheduled execution date of medical practice.

  The procedure for recording data in the task DB 254 will be described later.

  FIG. 12 is an explanatory diagram showing a record layout of the patient DB 256. The patient DB 256 includes a patient ID field, a kanji name field, a kana name field, and a date of birth field. In each field, the name, date of birth, etc. of the patient linked to the patient ID are recorded. In addition, a field for recording personal information such as an address, a telephone number, a health insurance card number, a maiden name, and a family register last name may be provided. The data in the patient DB 256 is registered when a new patient is accepted, and is updated as needed when there is a change in personal information.

  FIG. 13 is an explanatory diagram showing a record layout of the used device DB 255. The used device DB 255 includes a content field and a used device field. In the content field, items described in the content field of the task DB 254 are recorded. In the device field to be used, a medical device used when performing a medical action described in the content field is recorded. The data in the used device DB 255 is added or updated when there is an addition or change in the type of medical practice performed at the medical facility and the medical device.

  In FIG. 13, “GTF” is an abbreviation for GasTrocamera with Fiberscope. The literal translation means endoscopic examination of the stomach with an endoscope using an optical fiber, but in recent years when an endoscope using an image sensor instead of an optical fiber has become common, it means an upper gastrointestinal endoscopy To do.

  In addition, “Other” in FIG. 13 is used for inputting medical practice that is performed less frequently. By preparing the “other” record, it is not necessary to register all possible medical practices in the use device DB 255.

  14 to 21 are explanatory diagrams showing images of the task input screen. An outline of an operation for inputting a new task will be described with reference to FIGS. 4, 5, and 14 to 21. Note that the flow of processing performed inside the operation terminal 1 and the server 2 will be described later.

  When the first calculation control unit 11 receives the selection of the row on the schedule list column 401 and the selection of the task input instruction button 403 in this order when the initial screen of FIG. 4 is displayed, as shown in FIG. A reservation status list 421 is displayed. When the first calculation control unit 11 receives selection of the new addition button 422, the task input screen of FIG. 14 is displayed.

  The task input screen includes a task ID column 412, a date column 406, a task start time column 407, a task end time column 408, a person column 409, a patient ID column 405, a content column 411, a remarks column 413, a device column 410, and an end button. 404 is arranged.

  In the date column 406 and the task start time column 407 of the task input screen, the same date and time as the row selected in the schedule list column 401 is set. The end button 404 is displayed lightly and is set not to accept the selection.

  As shown in FIG. 15, the patient ID column 405 receives an input of a patient ID of a patient who receives a medical practice. As shown in FIG. 16, the content column 411 receives input of the content of the medical practice to be performed. The content is selected from the items listed in the content field of the used device DB 255 displayed by a pull-down menu in the vicinity of the content column 411. With reference to the used device DB 255, the use flag of the medical device corresponding to the item received in the content column 411 is set, and is displayed on the screen as “◯” as shown in FIG.

  As shown in FIG. 18, an input of the task end time is accepted in the task end time column 408. When the task end time column 408 is blank after the input is started, a message “task end time is not input” is displayed as shown in the lower part of FIGS. 15 to 17. As shown in FIG. 18, selection of doctors or comedies participating in the participation flag string in the person column 409 is accepted. The participation start time and participation end time of the doctor or comedy who has received the participation flag are set and displayed at the same time when the task start time and task end time are received.

  The second arithmetic control unit 21 refers to the reservation DB 253 to determine whether there is an overlap with an existing reservation. For example, when the schedule of radiologist E overlaps with an existing reservation, a message “Reservation of radiologist E is duplicated” is displayed as shown in the lower part of FIG. Since this message does not require a response, the first arithmetic control unit 11 can continue accepting various inputs while displaying the message.

  When the input of the minimum necessary items for registering the task is completed and there is no overlap with the existing reservation, the end button 404 is displayed darkly as shown in FIG. 19, and the selection can be accepted. .

  As shown in FIG. 20, the change of the participation start time and participation end time of a doctor or a comedy with the participation flag set is accepted. When the entry start time and participation end time are changed outside the range from the task start time to the task end time, the end button 404 returns to a light color display and is changed to a setting that does not accept selection. . When the input of the end button 404 is received, the second calculation control unit 21 stores the input content. When the saving is completed, a message indicating that the reservation has been saved is displayed as shown in the lower part of FIG.

  A processing flow of the information processing system 4 will be described with reference to a flowchart. FIG. 22 is a flowchart illustrating a processing procedure of the information processing system 4.

  The processing flow of the information processing system 4 will be described with reference to FIG. When the information processing system 4 is activated, the second calculation control unit 21 of the server 2 instructs the first display control unit 14 of the operation terminal 1 to output the initial screen shown in FIG. (Step S501). The first arithmetic control unit 11 receives an instruction from the second arithmetic control unit 21 via the second bus 28, the second communication unit 26, the network 3, the first communication unit 16, and the first bus 18, and receives the first bus 18. The initial screen shown in FIG. 4 is output to the first display unit 14 via (step S502). In the following description, description of communication paths of the second bus 28, the second communication unit 26, the network 3, the first communication unit 16, and the first bus 18 is omitted.

  The first calculation control unit 11 receives an input from the user (step S503), and sends the received content to the second calculation control unit 21 through communication. The second arithmetic control unit 21 acquires the transmitted input. In the following description, it is described that the sending operation and the obtaining operation are transmitted together. The second calculation control unit 21 determines whether or not the transmitted input means addition of a new task (step S504). Here, the input meaning the addition of a new task is the selection of a row in the schedule list column 401 shown on the initial screen of FIG. 4 and the subsequent selection of the task input instruction button 403.

  When the input content means addition of a new task (YES in step S504), the second calculation control unit 21 causes the first calculation control unit 11 to display the reservation status list 421 shown in FIG. An instruction is given (step S505). If the input content means other than adding a new task (NO in step S504), the operation of the information processing system 4 ends. The input content other than the addition of a new task is selection of the end button 404, for example.

  The first calculation control unit 11 outputs the display screen of the reservation status list 421 shown in FIG. 5 to the first display unit 14 (step S506). When receiving the input of the new addition button 422 (step S507), the first calculation control unit 11 transmits the input to the second calculation control unit 21 by communication.

  The second arithmetic control unit 21 cancels the end permission flag and the end button flag (step S508). The end permission flag is a flag indicating whether or not a task input end can be accepted. When the end flag is set, the first calculation control unit 11 accepts selection of the end button 404 on the task input screen shown in FIGS. When the end flag is canceled, the first calculation control unit 11 does not accept selection of the end button 404 on the task input screen. The end button flag is a flag indicating whether or not the selection of the end button 404 on the task input screen is accepted. When the end button flag is set, the end button 404 on the task input screen indicates that selection has been accepted. When the end button flag is canceled, the end button 404 on the task input screen indicates that selection is not accepted.

  The second arithmetic control unit 21 starts a task input subroutine (step S509). The task input subroutine is a subroutine for inputting data to the task DB 254 and the reservation DB 253. Processing in the task input subroutine will be described later.

  The second calculation control unit 21 determines the state of the end button flag (step S510). If step S510 is reached for the first time after releasing the end button flag in step S508, the end button flag remains released. In this case (NO in step S510), the second arithmetic control unit 21 activates a double-booking check subroutine (step S511). The double-booking check subroutine is a subroutine for determining whether or not there is an overlap between a doctor, a comedy, and a medical device schedule of an input task and an existing reservation recorded in the reservation DB 253. Processing in the double booking check subroutine will be described later.

  If the input task can be registered through the double-booking check subroutine, the second calculation control unit 21 sets an end enable flag. If the registration is impossible, the second calculation control unit 21 cancels the end possible flag (step S512). Thereafter, the process returns to step S509.

  The loop of step S509, step S510, step S511, and step S512 is repeated several times. When returning from the task input subroutine (step S509) with the end button flag set (YES in step S510), the second arithmetic control unit 21 activates a task record storage subroutine (step S513). The subroutine for saving task records is a subroutine for assigning a task ID to the task being input and saving it in the task DB 254. Processing in the task record storage subroutine will be described later.

  The second arithmetic control unit 21 activates a reservation DB recording subroutine (step S514). The reservation DB recording subroutine is a subroutine for reflecting the contents of the input task in the reservation DB 253. Processing in the reservation DB recording subroutine will be described later.

  After the reservation DB recording subroutine is completed (step S514), one reservation process of the present embodiment ends.

  FIG. 23 is a flowchart showing a task input processing procedure. As described above, the task input subroutine is a subroutine for inputting data to the task DB 254 and the reservation DB 253. With reference to FIG. 23, the flow of processing of a task input subroutine will be described.

  The second calculation control unit 21 instructs the first calculation control unit 11 to display the task input screen (step S521). The first calculation control unit 11 outputs the task input screen shown in FIG. 14 on the first display unit 14 (step S522). The first calculation control unit 11 sets the input to the patient ID column 405 on the task input screen so as to be accepted. When the first arithmetic control unit 11 receives an input (step S523), the first arithmetic control unit 11 transmits the input to the second arithmetic control unit 21 by communication.

  The second arithmetic control unit 21 determines whether the content of the received input is “input / change”, that is, input or change of any item in the task input screen, or “end”, that is, selection of the end button 404. Determination is made (step S524). In the first step S524, the end flag is canceled as described above, and the end button 404 does not respond to the user's operation, so that the selection of “end” is not accepted.

  When the accepted input is an input or change to any item on the task input screen of FIG. 14 (“input / change” in step S524), the second calculation control unit 21 sets the variable “error part” to an initial value. A blank is set (step S525). The second arithmetic control unit 21 activates a time conflict check subroutine shown in FIGS. 24 to 26 (step S526). The time conflict check subroutine is a subroutine for determining whether or not there is a time conflict in the input task. The contradiction means that the task end time is earlier than the task start time, for example. The processing in the subroutine for checking the time contradiction will be described later.

  The second arithmetic control unit 21 determines whether or not an error message is recorded in the variable “error part” (step S527). In the stage of FIG. 15, since the task end time column 408 is not input, an error message is recorded in the variable “error part” in the time inconsistency check subroutine (NO in step S527).

  The second calculation control unit 21 cancels the end possible flag (step S528). The second calculation control unit 21 instructs the first calculation control unit 11 to display the error content (step S529).

  The first calculation control unit 11 outputs the error content to the first display unit 14 (step S530). The error content is displayed, for example, with the text “task end time not entered” at the bottom of FIG. As another display method, the field to be input or corrected may be colored red or the like. Then, it returns to step S523 and accepts an input operation.

  In the second and subsequent steps S523, the first calculation control unit 11 causes the date field 406, task start time field 407, task end time field 408, person field 409, device field 410, and content field 411 in the task input screen of FIG. And the remarks column 413 is set to the state which receives the input by a user. The first calculation control unit 11 sets an already input item in an editable state.

  When the loop of step S523, step S524, step S525, step S526, step S527, step S528, step S529, and step S530 is repeated several times and no error occurs in the time conflict check subroutine (YES in step S527) The process proceeds to step S531.

  The second arithmetic control unit 21 activates an automatic setting subroutine shown in FIG. 27 (step S531). The automatic setting subroutine is a subroutine for automatically setting an input item from the immediately preceding input item and the used device DB 255 or the content being input.

  After the automatic setting subroutine (step S531) ends, the task input subroutine ends.

  If the end flag is set, the first calculation control unit 11 displays the end button 404 darkly as shown in FIG. 19 and sets it in a state of accepting the user's operation. When the second calculation control unit 21 determines that the first calculation control unit 11 has received the selection of the end button 404 (step S523) (“end” in step S524), the second calculation control unit 21 sets the end button. A flag is set (step S532). Thereafter, the task input subroutine ends.

  FIG. 24 to FIG. 26 are flowcharts showing the processing procedure for time conflict checking. As described above, the time conflict check subroutine is a subroutine for determining whether or not there is a time conflict in the task being input. Contradiction means that if the task start time or task end time is not entered, if the task end time is earlier than the task start time, or if the participation start time or participation end time of the participant is not entered, participation will start This means that the participation end time is earlier than the time, or the participation start time and the participation end time are not between the task start time and the task end time. With reference to FIGS. 24 to 26, the flow of processing of the time conflict check subroutine will be described.

  The second arithmetic control unit 21 determines whether or not a task start time has been input (step S561). If the second arithmetic control unit 21 determines that no task start time is input (NO in step S561), an error message “task start time is not input” is displayed in the variable “error part”. It adds (step S564). Thereafter, the second arithmetic control unit 21 determines whether or not a task end time has been input (step S565). If the second arithmetic control unit 21 determines that there is an input to the task end time field (YES in step S565), the time contradiction check subroutine ends.

  If the second arithmetic control unit 21 determines that there is no input in the task end time field (NO in step S565), the error “no task end time is input” in the variable “error part”. A message is added (step S566). Thereafter, the subroutine for checking the time contradiction ends.

  If it is determined that the task start time is input (YES in step S561), the second arithmetic control unit 21 determines whether the task end time is input (step S562). When the second calculation control unit 21 determines that there is no input to the task end time (NO in step S562), the process proceeds to step S566 described above.

  If it is determined that the task end time is input (YES in step S562), the second arithmetic control unit 21 determines the magnitude relationship between the task start time and the task end time (step S563). If the second arithmetic control unit 21 determines that the task start time is not earlier than the task end time (NO in step S563), the variable “error part” indicates that “the task start time is not earlier than the task end time. "Is added (step S567). Thereafter, the subroutine for checking the time contradiction ends.

  If it is determined that the task start time is earlier than the task end time (YES in step S563), the second arithmetic control unit 21 sets the counter I to 1 (step S568). The second calculation control unit 21 determines whether or not the participation flag of the I-th person of the task being input is set (step S569). In the following description, the name of the I-th person will be described as X.

  If it is determined that the participation flag for the I-th person is set (YES in step S569), the second calculation control unit 21 determines whether or not the participation start time of the I-th person has been input (step S569). S801). If the second calculation control unit 21 determines that the participation start time has not been input (NO in step S801), the error “the participation start time of X has not been input” is entered in the variable “error part”. A message is added (step S802). Thereafter, the second arithmetic control unit 21 determines whether or not the participation end time has been input (step S803).

  If it is determined that the participation start time is input (YES in step S801), the second arithmetic control unit 21 determines whether or not the participation end time is input (step S804). If the second calculation control unit 21 determines that the participation end time has not been input (NO in step S803 or NO in step S804), the variable “error part” is not input with the “X participation end time”. "Is added (step S805).

  If it is determined that the participation end time is input (YES in step S804), the second arithmetic control unit 21 determines the magnitude relationship between the participation start time and the participation end time (step S806). If the second calculation control unit 21 determines that the participation start time is not earlier than the participation end time (NO in step S806), the variable “error part” indicates that “X participation start time is greater than the participation end time. An error message “No sooner” is added (step S807).

  If it is determined that the participation start time is earlier than the participation end time (YES in step S806), the second arithmetic control unit 21 determines the magnitude relationship between the task start time and the participation start time (step S810). If the second arithmetic control unit 21 determines that the task start time is later than the participation start time (NO in step S810), the variable “error part” has “X participation start time earlier than the task start time. Is added (step S811).

  When it is determined that the task start time is not later than the participation start time (YES in step S810) or after step S811, the second arithmetic control unit 21 determines the magnitude relationship between the task end time and the participation end time ( Step S812). If the second arithmetic control unit 21 determines that the participation end time is later than the task end time (NO in step S812), the variable “error part” has “X participation end time later than the task end time”. Is added (step S813).

  If the second calculation control unit 21 determines that the participation end time is not later than the task end time (YES in step S812), the second calculation control unit 21 determines whether confirmation of all persons has been completed (step S814). The second calculation control unit 21 also determines that the participation flag of the I-th person has not been set (NO in step S569) and if it is determined that there is an input of the participation end time (YES in step S803). Then, it is determined whether or not all the persons have been confirmed (step S814). Even after the end of step S805, step S807, or step S813, the second calculation control unit 21 determines whether or not confirmation of all persons has been completed (step S814).

  If it is determined that there is a person who has not been confirmed (NO in step S814), the second arithmetic control unit 21 adds 1 to the counter I (step S815). Thereafter, the process returns to step S569. If the second arithmetic control unit 21 determines that all the persons have been confirmed (YES in step S814), the time contradiction check subroutine ends.

  FIG. 27 is a flowchart showing a processing procedure for automatic setting. As described above, the automatic setting subroutine is a subroutine for automatically setting an input item from the immediately preceding input item and the used device DB 255 or the content being input. With reference to FIG. 27, the processing flow of the automatic setting subroutine will be described.

  The second calculation control unit 21 determines whether the target of the “input or change” operation received in step S523 of the above-described task input subroutine is the content column 411 or the person column 409 of the task input screen of FIGS. It is determined whether the column is other than (step S541).

  When it is the content column 411 that has been input or modified (“content column” in step S541), the second calculation control unit 21 refers to the used device DB 255. The second calculation control unit 21 extracts from the used device DB 255 a record in which the same items as the items described in the input or modified content column are described in the content field (step S542). The second arithmetic control unit 21 sets a medical device use flag described in the device field used by the retrieved record (step S543). In accordance with this, the second calculation control unit 21 instructs the first calculation control unit 11 to output a “◯” mark to the device for which the use flag in the device column 410 is set. Thereafter, the automatic setting subroutine ends.

  An example of a task input screen upon completion of step S543 is shown in FIG. Since ERCP is input in the content column 411, the use flag for the endoscope and X-ray fluoroscopy is set with reference to the used device DB 255, and “O” is displayed in the endoscope and X-ray fluoroscopy frame in the device column 410. Has been.

  If the person field 409 was input or modified in the previous step S524 (“person field” in step S541), the second calculation control unit 21 determines whether or not the modification content is an additional setting for a person. (Step S544). It is determined that it is an additional setting for a person because a person participation flag is set. When a person has been added (YES in step S544), the second calculation control unit 21 displays the participation start time and participation end time of the additionally set person in a task start time field 407 and a task end time field. It is set according to 408 and is reflected on the display screen via the first calculation control unit 11 (step S545). Thereafter, the automatic setting subroutine ends. If the task start time column 407 or the task end time column 408 is blank, the corresponding participation start time or participation end time is also blank.

  As an example, a case where the participation flag of the radiologist E is changed from cancellation to setting in step S524 will be described with reference to FIG. The second calculation control unit 21 determines that the radiologist E has been added from the state of the participation flag (YES in step S544). At the time of step S544, the participation start time and participation end time of the radiologist E are blank. The second arithmetic control unit 21 adjusts the participation start time of the radiologist E to the time set in the task start time column 407 and the participation end time to the time set in the task end time column 408, respectively. Reflected in the display screen of the first display unit 14 via the unit 11 (step S545).

  If it is not the additional setting of the person participation flag (NO in step S544), the second calculation control unit 21 determines whether or not the correction content is deletion of the person (step S546). It is determined that the person has been deleted because the person's participation flag has been canceled. When the person is deleted (YES in step S546), the second calculation control unit 21 changes the participation start time and the participation end time of the person to blanks which are default values, and the first calculation control unit 11 is reflected on the display screen of the first display unit 14 (step S547). Thereafter, the automatic setting subroutine ends.

  The case where the input content is not deletion of a person in step S546 (NO in step S546) is a case where the participation start time or the participation end time in the person column 409 is changed. In this case, the automatic setting subroutine ends. Even if it is neither the content column 411 nor the person column 409 that has been input or modified (“others” in step S541), the automatic setting subroutine ends.

  FIG. 28 is a flowchart showing the processing procedure of the double booking check. As described above, the double-booking check subroutine is a subroutine for determining whether or not there is a duplication between a doctor, a comedy, and a medical device schedule of an input task and an existing reservation recorded in the reservation DB 253. With reference to FIG. 28, the flow of processing of the subroutine of the double booking check will be described.

  The second arithmetic control unit 21 determines whether there is a contradiction in the task (step S601). For example, if the content column 411 is blank, the content column 411 is an item in which participation of doctors such as surgery is indispensable, but there are no doctors for which the participation flag is set in the person column 409. This means that task input has not been completed, such as when appropriate characters have been input. If there is a contradiction in the task (NO in step S601), the double booking check subroutine ends. If there is no contradiction in the task (YES in step S601), the second calculation control unit 21 sets the counter I to the initial value 1, and initializes the warning device list and the warning person list to be blank (step S602).

  The second calculation control unit 21 extracts from the reservation DB 253 a reservation record for the time slot of the I-th unit time of the task being input (step S603). The second arithmetic control unit 21 determines whether or not the patient ID field of the device used in the entered task in the retrieved reservation record is “0” (step S605). If it is not “0” (NO in step S605), the name of the medical device for which the reservation is duplicated is added to the “warning device list” (step S606). If “0” (YES in step S605), the second calculation control unit 21 proceeds to step S607.

  The second arithmetic control unit 21 determines whether the patient ID field of the person in charge of the input task in the retrieved reservation record is “0” (step S607). If it is not “0” (NO in step S607), the name of the person whose reservation is duplicated is added to the “warning person list” (step S608).

  If it is “0” (YES in step S607) and after the process of step S608, the second arithmetic control unit 21 determines whether or not the confirmation has been completed until the end time of the input task (step S609). . If not completed (NO in step S609), the second calculation control unit 21 adds 1 to the counter I (step S610) and returns to step S605. If all the tasks in the task list have been confirmed (YES in step S609), the second calculation control unit 21 instructs the first calculation control unit 11 to display a message (step S611). The content of the message is that if there is data in the “Warning device list” or “Warning person list”, the task being entered has a duplicate reservation, and there is no data in either list Indicates that the input task can be registered. The first calculation control unit 11 outputs the instructed message to the first display unit 14 (step S612). Thereafter, the double booking check subroutine ends.

  It should be noted that step S605 and step S607 may be interchanged to determine whether there is duplication of people first.

  If there is no contradiction in the task in step S601 and there is no overlapping reservation in step S611, the input task is in a registerable state.

  FIG. 29 is a flowchart showing a processing procedure for saving a task record. As described above, the task record storage subroutine is a subroutine that assigns a task ID to the task being input and stores it in the task DB 254.

  The second calculation control unit 21 determines whether or not the content column of the task being input is “diagnosis” (step S830). If the second arithmetic control unit 21 determines that the content column of the task being input is “diagnosis” (YES in step S830), is only one doctor in charge of the task being input? It is determined whether or not (step S831). If the second arithmetic control unit 21 determines that only one doctor is in charge of the input task (YES in step S831), whether the time required for the input task is a unit time or not. Is determined (step S832). If the second calculation control unit 21 determines that the required time of the input task is a unit time (YES in step S832), the second calculation control unit 21 determines whether the input task is already stored in the task DB 254 ( Step S833). If it is determined that the task being input is already stored in the task DB 254 (YES in step S833), the second arithmetic control unit 21 deletes the stored task record from the task DB 254 (step S834). After that, the subroutine for saving task records ends.

  If the second calculation control unit 21 determines that the task being input is not stored in the task DB 254 (NO in step S833), the task record storage subroutine ends. When the content field of the task being input is not “diagnosis” (NO in step S830), the person in charge is not only one doctor (NO in step S831), or the required time is not a unit time (in step S832). NO), the second calculation control unit 21 assigns a task ID to the task being input (step S835). When a task record to which a task ID is already assigned is corrected, the assigned task ID is used as it is. Thereafter, the second calculation control unit 21 stores the task record being input in the task DB 254 (step S836), and the task record storage subroutine ends.

  30 and 31 are flowcharts showing the reservation DB recording processing procedure. As described above, the reservation DB recording subroutine is a subroutine for reflecting the contents of the task record in the reservation DB 253. With reference to FIG. 30 and FIG. 31, the flow of processing of the reservation DB recording subroutine will be described.

  The second calculation control unit 21 sets the counter I to 1 (step S621). The second calculation control unit 21 extracts a reservation record including the participation start time of the I-th participant in the task record being input from the reservation DB 253 (step S622). The second calculation control unit 21 records the patient ID, contents, and remarks of the task record being input in the field indicating the I-th participant in the retrieved reservation record (step S623).

  The second calculation control unit 21 takes out a reservation record for the next time zone from the reservation DB 253 (step S624). The second calculation control unit 21 determines whether or not the time zone of the retrieved reservation record is the time zone during which the I-th person is participating (step S625). In the case of the participating time zone (YES in step S625), the second calculation control unit 21 indicates that the same task is continuing in the patient ID field of the I-th participant in the retrieved reservation record. “999999” is recorded (step S626), and the process returns to step S624. If it is not the time zone in which the I-th person is participating in step S625 (NO in step S625), the second calculation control unit 21 determines whether or not the processing of all the participants in the input task record has been completed. (Step S627). If all the processes have not been completed (NO in step S627), the second calculation control unit 21 adds 1 to the counter I (step S628), and then returns to step S622. If all the processes are participating (YES in step S627), the second calculation control unit 21 determines whether to use the medical device in the task record being input (step S629).

  When using a medical device (YES in step S629), the second calculation control unit 21 extracts a reservation record including the task start time of the task record being input from the reservation DB 253 (step S631). The second calculation control unit 21 records the patient ID of the task record being input in the patient ID fields of all medical devices used in the task record being input in the retrieved reservation record (step S632).

  The second calculation control unit 21 extracts a reservation record for the next time zone from the reservation DB 253 (step S633). The second arithmetic control unit 21 determines whether or not the time zone of the extracted record is a time zone in which the task of the task record being input is continuing (step S634). In the case where the task is continuing (YES in step S634), the second arithmetic control unit 21 continues the same task in the patient ID fields of all medical devices used in the task record being input in the extracted record. “999999” indicating that it is in the middle is recorded (step S635), and the process returns to step S633. When it is not the time period during which the task is continuing (NO in step S634) and when the medical device is not used (NO in step S629), the second arithmetic control unit 21 stores the reservation DB 253 (step S638), and the reservation DB The recording subroutine ends.

  According to the present embodiment, it is possible to reserve a doctor's and comedy's schedule only for a time range in which it is necessary to participate in medical practice. In addition, since the task ID is not assigned to the examination scheduled for unit time by a single doctor having the largest number of cases, the capacity of the task DB is reduced. Therefore, the storage capacity of the task DB can be saved, and a system that operates lightly can be realized.

  Note that a task record may be created by assigning a task ID to a schedule of a unit time examination by a single doctor in the same manner as other schedules. In this case, the processing from step S830 to step S834 is omitted in the task record storage subroutine shown in FIG. 29, and task ID assignment (step S835) and storage (step S836) are performed for all tasks. Process.

[Embodiment 2]
In the second embodiment, the second calculation control unit 21 performs a double booking check after explicitly receiving the selection of the end button 404 in the task input screen of FIG. 14 via the first calculation control unit 11. It is. 32 and 33 are flowcharts illustrating the processing procedure of the information processing system 4 according to the second embodiment.

  With reference to FIG. 32 and FIG. 33, the flow of processing of the information processing system 4 of the present embodiment will be described. Note that description of portions common to FIG. 22 is omitted. The process from the start of the process until the input is accepted in step S507 is the same as the process of FIG.

  The second calculation control unit 21 cancels the end button flag (step S651). The second calculation control unit 21 sets an end possible flag (step S652). The second arithmetic control unit 21 starts a task input subroutine (step S509). The task input subroutine is the same as that shown in FIG. However, in this embodiment, since an end possible flag is set immediately before the start of the task input subroutine, the end button 404 in the task input screen of FIG. 14 can accept input from the first time.

  The second calculation control unit 21 determines whether or not the end button flag is set (step S653). If the end button flag is released (NO in step S653), the process returns to step S652. This means that the task input subroutine is repeated until the second calculation control unit 21 detects selection of the end button 404 via the first calculation control unit 11. If the end button flag is set (YES in step S653), the second calculation control unit 21 starts the double-booking check subroutine of FIG. 28 (step S511).

  The second arithmetic control unit 21 determines whether the input task can be registered (step S654). If some problem is found in the input task and cannot be registered (NO in step S654), the process returns to step S652. On the other hand, if registration is possible (YES in step S654), the second calculation control unit 21 starts a task record storage subroutine of FIG. 29 (step S513). The second arithmetic control unit 21 activates the reservation DB recording subroutine of FIGS. 30 and 31 (step S514).

  Before entering step S513, the second calculation control unit 21 displays a message such as “Do you want to save? (Y / N)” on the first calculation control unit 11 to input the user's intention. May be instructed to accept.

  When step S505, step S506, and step S507 are omitted and the input of the task input instruction button 403 is accepted from the initial screen shown in FIG. 4 (step S503), the process directly transitions to the task input screen of FIG. good.

  When the first calculation control unit 11 accepts that the task ID is selected on the screen of FIG. 5, the modification of the task record of the selected task ID may be started. Specifically, the second calculation control unit 21 starts the processing of FIG. 33 from step S652 in a state where both the end possible flag and the end button flag are set. With this flow, a task record that has already been registered can be corrected.

  When the first calculation control unit 11 accepts selection of the display change button 425 on the initial screen of FIG. 4, the examination engineer starts from the screen displaying the schedules of the doctors A, B, and C shown in FIG. You may make it switch to the screen which displayed the schedule of D and the inspection engineer E mainly. Similarly, a display change button 425 for displaying the schedule of the nurse or the schedule of the medical device may be provided.

  The initial screen of FIG. 4 may be different depending on the person who is logged on. For example, when the laboratory technician D is logged on, it is desirable that the laboratory technician D and the schedule of the medical device mainly handled by the laboratory technician D are displayed. With this setting, a user interface that accurately displays information tailored to the user can be realized.

  In the present embodiment, the second arithmetic control unit 21 performs a double booking check after explicitly receiving the selection of the end button 404 in the task input screen of FIG. Therefore, the reservation processing can be performed smoothly even when a load on the second arithmetic control unit 21 is light and a computer with relatively low capacity is used for the server 2.

[Embodiment 3]
In the third embodiment, the staff of other departments or other facilities can be reserved when it is desired to support the staff with special technical skills. FIG. 34 is an explanatory diagram illustrating an initial screen of the information processing system 4 according to the third embodiment. FIG. 35 is an explanatory diagram showing an image of the task input screen according to the third embodiment. If you want to support the staff with special technical skills here, for example, if you have surgery in a case where rectal cancer has invaded the uterus, participate in an experienced gynecologist If you want to ask.

  With reference to FIG. 34 and FIG. 35, operation | movement of the information processing system 4 of this embodiment is demonstrated. Note that description of portions common to the first embodiment is omitted.

  FIG. 34 is an initial scene of surgery in a general hospital. In FIG. 34, an affiliation tab 451 with names of a plurality of departments is displayed at the top of the schedule list field 401. FIG. 34 is an initial screen when a person belonging to surgery is logged on, and the “Surgery” membership tab 451 is selected. In FIG. 34, the schedules of doctors A, B, and C belonging to surgery are displayed in a list. In addition, a summary of schedules for the laboratory technician D and the radiology technician E is also displayed in a list. When the “surgical examination procedure” affiliation tab 451 is selected, a list of examination technicians D, radiologist E who belong to the surgery, and medical equipment schedules mainly handled by these two persons is displayed. When the “Internal Medicine”, “Gynecology”, “Ophthalmology”, and “Pediatric” affiliation tabs 451 are selected, a list of doctors and comedy schedules of each medical department is displayed. The affiliation tab 451 may target other departments in the same medical institution, or may target other medical institutions in the vicinity performing regional cooperation.

  When the first calculation control unit 11 receives the selection of the row on the schedule list column 401 and the selection of the task input instruction button 403 in this order when the initial screen of FIG. 34 is displayed, it is shown in FIG. In this way, the reservation status list 421 is displayed. Here, the reservation status list 421 displays a list of medical departments targeted by the selected affiliation tab 451. When the first calculation control unit 11 receives selection of the new addition button 422, the task input screen of FIG. 35 is displayed.

  In FIG. 35, a person selection tab 452 having names of medical departments “surgery”, “internal medicine”, “gynecology”, “ophthalmology”, and “pediatrics” is displayed in the upper part of the person column 409. FIG. 35 shows a state where the “Surgery” person selection tab 452 is selected. When the affiliation tab 451 of “Internal Medicine”, “Gynecology”, “Ophthalmology”, or “Pediatrics” is selected, a list of the participation flags and the like of doctors and comedies of each medical department is displayed, The status is set so that the selection can be accepted.

  A support field 453 is displayed below the person field 409. When the person selection tab 452 other than “Surgery” is selected, the affiliation, name, participation start time, and participation end time of the doctor and comedy for which the participation flag is set are displayed in the support column 453.

  In addition, since the user interface which switches the object displayed by list when the selection of the affiliation tab 451 and the person selection tab 452 is accepted, detailed description by a flowchart or the like is omitted.

  When the input is ended and the input content is stored in the task DB 254 and the reservation DB 253, the second calculation control unit 21 may directly record the support partner's reservation, or the second calculation control unit 21 may support the support partner. You may ask the system that manages the schedule to confirm and record the reservation. Moreover, you may ask | require approval from the system which the 2nd calculation control part 21 manages the schedule of a support partner, before confirming a reservation.

  In this way, it is possible to schedule doctors and comedies of other departments or medical institutions in conjunction with appointments of doctors, comedies and medical devices in their departments.

[Embodiment 4]

  The fourth embodiment provides a user interface for simply reserving routine tasks that are performed on a daily basis. Here, a routine task that is performed on a daily basis refers to a task that is not assigned a task ID and is not recorded in the task DB 254. In the following description, the unit time “diagnosis” performed by a doctor will be described as a routine task that is routinely performed. FIG. 36 and FIG. 37 are explanatory diagrams showing images of the screen according to the fourth embodiment.

  The outline of the fourth embodiment will be described with reference to FIG. 4, FIG. 36 and FIG. When the information processing system 4 is activated, the initial screen of FIG. 4 is displayed on the first display unit 14. When the patient ID input to the ID setting column 431 or the patient name input to the name setting column 432 is accepted, the patient ID, name, date of birth, and age of the patient are displayed in the patient information column 433 as shown in FIG. Is done.

  When the patient ID displayed in the ID setting column 431 is dragged and dropped into the schedule list column 401, a new reservation is input to the doctor and time of the drag and drop destination as shown in FIG.

  When an operation other than the input of the patient ID in the ID setting field 431 or the input of the patient name in the name setting field 432 is accepted, the same processing as in the first embodiment and the like is executed.

  38 and 39 are flowcharts showing the processing procedure of the information processing system 4 according to the fourth embodiment. With reference to FIG. 38 and FIG. 39, the flow of processing of the information processing system 4 according to the fourth embodiment will be described.

  When the information processing system 4 is activated, the second calculation control unit 21 instructs the first calculation control unit 11 to output the initial screen shown in FIG. 4 to the first display unit 14 (step S501). The first calculation control unit 11 outputs the initial screen shown in FIG. 4 on the first display unit 14 (step S502).

  The first calculation control unit 11 receives an input from the user (step S503), and transmits the received content to the second calculation control unit 21 through communication. The second arithmetic control unit 21 determines whether or not the transmitted input is a patient name or patient ID input (step S701). It is determined that the patient name is entered in the name setting field 432. The patient ID is determined when the input to the ID setting field 431 is performed. If neither the patient name nor the patient ID is input (NO in step S701), the same processing as in step S504 and subsequent steps in FIG. 22 is performed. In the case of inputting a patient name or patient ID (YES in step S701), the second calculation control unit 21 refers to the patient DB 256 and acquires patient information (step S702). The second calculation control unit 21 instructs the first calculation control unit 11 to display the patient information in the patient information column 433 (step S703). The patient information displayed here is the patient ID, name, date of birth, and age calculated from the date of birth.

  The first calculation control unit 11 outputs patient information to the first display unit 14 as shown in the patient information column 433 of FIG. 36 (step S704). The second calculation control unit 21 takes out the test data of the subject patient, the latest examination record, blood type, allergies, or past information from the electronic medical record and displays them in the patient information column 433 together with the date of birth. In this manner, the first arithmetic control unit 11 may be instructed.

  The first calculation control unit 11 selects the patient ID displayed in the ID setting column 431 displayed on the first display unit 14 by the pointer controlled by the user, and the pointer remains in the selected state in the schedule list column 401. It waits for acceptance of a so-called drag-and-drop operation that is moved up to cancel the selection (step S705). The first calculation control unit 11 detects the position where the selection is canceled, that is, the doctor name and the time zone displayed at the drop destination (step S706). Thereby, the input reception of the two information of the doctor who takes charge of one time and the time which implements medical practice by one drag and drop operation is performed simultaneously. When the drop destination is not a doctor name or when the drop destination is an area other than the schedule list column 401, the first calculation control unit 11 ignores the drag and drop operation. The first calculation control unit 11 transmits the detected time zone and doctor name to the second calculation control unit 21.

  The second calculation control unit 21 refers to the reservation DB 253 to determine whether or not there is a predecessor of the doctor's schedule in the transmitted time zone (step S707). Whether or not there is a prior agreement is determined by whether or not the patient ID field of the designated doctor in the transmitted time zone is “0”. If there is a prior agreement (YES in step S707), the second arithmetic control unit 21 instructs the first arithmetic control unit 11 to display a message indicating that there is a prior agreement and the reservation cannot be accepted (step S708). The first calculation control unit 11 outputs a message to the first display unit 14 (step S709), and then returns to step S705. If there is no prior agreement (NO in step S707), the second calculation control unit 21 activates the reservation DB recording subroutine shown in FIGS. 30 and 31 to reflect the input contents in the reservation DB 253 (step S514). At this time, the contents field of the reservation DB 253 is “diagnosis” and the remarks field is blank.

  The second calculation control unit 21 instructs the first calculation control unit 11 to display a reservation completion message (step S711). The first calculation control unit 11 outputs a reservation completion message to the first display unit 14 (step S712). The second calculation control unit 21 instructs the first calculation control unit 11 to update the schedule list column 401 (step S713). The first calculation control unit 11 outputs the schedule list column 401 to the first display unit 14 (step S714). Thereafter, the process ends.

  The routine tasks that are performed on a daily basis may be “periodic medical examination”, “preventive injection”, or the like instead of “diagnosis”. By handling routine tasks that are most frequently performed at medical institutions that use the information processing system 4 as routine tasks that are routinely performed, a system that reduces the load on the information processing system 4 and is easy to operate is realized. be able to.

  The operation accepted in step S705 is not limited to the drag and drop operation. For example, the patient ID column 405 and the schedule list column 401 may be continuously clicked, continuously double clicked, continuously tapped, or the like. A tap is a kind of operation method of a touch panel type input device, and means an operation of touching the touch panel. Further, for example, voice input such as “doctor C, 10:20” may be used, or gesture input such as pointing to the screen displayed on the first display unit 14 may be used.

  According to the present embodiment, the doctor who is in charge and the time for performing the medical practice are input by one operation, and the reservation can be recorded by receiving the input. Therefore, it is possible to provide a user interface that can easily reserve a routine schedule that is routinely performed.

[Embodiment 5]
In the fifth embodiment, a patient who has a situation in which he / she does not want to call his / her name at a medical facility window or waiting room, such as a celebrity or a celebrity, is handled in pseudonyms. FIG. 40 is an explanatory diagram of a record layout of the patient database according to the fifth embodiment. FIG. 41 is an explanatory diagram showing an image of the screen according to the fifth embodiment.

  In FIG. 41, “Suzuki Hanako”, who is examined by Doctor A from 10:15, is a pseudonym. The information of Mr. Hanako Suzuki is displayed in a different typeface from that of other patients so that the person viewing the screen can be identified as a pseudonym. The real name of “Suzuki Hanako” is not displayed on this screen, so pseudonyms are used for calls such as medical examinations and checkouts, thereby protecting the patient's privacy. On the other hand, in situations where it is necessary to process with real names, such as insurance claim procedures, the real names registered in advance are displayed, and the necessary processing can be performed smoothly.

  The patient DB 256 shown in FIG. 40 is obtained by adding fields of a Chinese character real name and a kana real name to the patient DB 256 of FIG. In the case of a patient who uses a kana, the kana name is recorded in the kanji name field and the kana name field when the patient DB 256 is input or updated, and the real name is recorded in the kanji real name field and the kana real name field. When a patient who does not have a Chinese character name, such as a Western patient, uses a kana, the original name or the reading of the patient name is recorded in the Kanji real name field. In this case, it is desirable to adopt the format required for official procedures such as insurance claim procedures.

  A procedure for displaying a pseudonym will be described taking the patient name displayed in the schedule list field 401 in the initial screen of FIG. 41 as an example.

  The second calculation control unit 21 takes out a reservation record of a time zone to be displayed from the reservation DB 253 of FIG. The second calculation control unit 21 determines whether data is recorded in the kana real name field of the patient record using the patient ID recorded in the reservation record as a key. If data is recorded in the Kana real name field, the patient is a patient using a pseudonym.

  The second arithmetic control unit 21 creates information to be displayed in the schedule list column 401 by arranging task IDs, kana names, contents, and remarks information so as to correspond to the recording of the reservation record. At this time, a typeface different from that of a normal patient is designated for a patient using kana. Thereafter, the second calculation control unit 21 instructs the first calculation control unit 11 to display a screen including the schedule list column 401. The first calculation control unit 11 outputs the screen of FIG. 41 to the first display unit 14.

  With the above processing, as shown in FIG. 41, the name of the patient who uses the pseudonym is displayed in a typeface different from that of the normal patient.

  Instead of changing the typeface of the patient's information using the pseudonym, the second arithmetic control unit 21 changes the color, puts a mark in the vicinity, changes the size of the character, and outputs it. One operation control unit 11 may be instructed. In addition, the second calculation control unit 21 may instruct the first calculation control unit 11 to write the real name near the pseudonym and output it. In this case, in order to avoid calling the real name by mistake in the waiting room, etc., it is instructed to display the real name in characters that are harder to read than kana, such as characters that are smaller than kana or lighter than kana. It is desirable to do.

  When the first arithmetic control unit 11 accepts selection of a patient using a pseudonym, the real name of the patient may be displayed in a pop-up on the screen of the first display unit 14. In this case, the data of the kanji real name field or the kana real name field of the patient who uses the kana is sent in advance from the second calculation control unit 21 to the first calculation control unit 11. The second calculation control unit 21 instructs the first calculation control unit 11 to pop up the real name only when a staff member who needs to know the real name is logged on, thereby protecting the privacy of the patient who uses the pseudonym. Can be done reliably. In addition, only when the staff who needs to know the real name is logged on, the data in the kanji real name field or the kana real name field of the patient using the kana from the second calculation control unit 21 to the first calculation control unit 11 is stored. You can send it.

  When a staff member who needs to know the patient's real name is logged on, the second calculation control unit 21 may instruct the first calculation control unit 11 to output the real name instead of the pseudonym. In this case, the second arithmetic control unit 21 uses the kanji name field data for the patient who uses the kana characters by replacing the kanji name field data with the kana name field data and the kana name field data. It is effective for protecting the privacy of a patient who uses a pseudonym to indicate that the patient normally uses the pseudonym with a typeface, color, mark, or the like.

  The second calculation control unit 21 may instruct the first calculation control unit 11 to output so that it cannot be identified that it is a pseudonym other than a specific staff who needs to know the real name of the patient. Since the use of the pseudonym itself is hidden from ordinary staff, privacy can be protected at a higher level.

  According to the present embodiment, it is possible to respect the privacy of a patient who does not want to call his name at a medical institution.

[Embodiment 6]
In the sixth embodiment, schedules other than medical activities such as academic societies, research groups, public lecture activities, and vacations are managed together with medical activities. FIG. 42 is an explanatory diagram illustrating a record layout of the used device DB 255 according to the sixth embodiment. FIG. 43 is an explanatory diagram showing an image of the screen according to the sixth embodiment.

  The use device DB 255 shown in FIG. 42 includes a record whose content field is “non-medical”. This record is used when inputting a schedule other than medical practice.

  If it is determined in step S524 of the task input subroutine of FIG. 23 that the input of “non-medical” is received in the content column 411, the second arithmetic control unit 21 sets “999999” indicating the action of “non-medical” as the patient ID. "Is set. Thereafter, processing is performed in accordance with the flowcharts after step S524, and after the input is completed, task records are recorded in the task DB 254 and the reservation DB 253.

  FIG. 43 shows an example of the schedule list column 421. Examining engineer D's “Non-medical ABC Study Group” and Doctor A's “Afternoon Half-Day Leave” are displayed side by side with the schedule for normal medical practice. Since the patient ID is “non-medical”, it can be determined that the activity is different from the normal medical practice. In FIG. 43, “ABC Study Group” and “Afternoon Half-Day Leave” are optional items recorded in the remarks field of each task record.

  The patient ID “999998” is an example, and any other value can be assigned. However, a value that is not used is adopted as the patient ID.

  According to the present embodiment, it is possible to collectively manage activities other than medical practice by doctors or comedies, specifically schedules such as academic conferences, research meetings, general lecture activities, vacations, and the like. The vacation schedule may be linked to a system for labor management such as attendance.

[Embodiment 7]
FIG. 44 is an explanatory diagram showing an image of the screen according to the seventh embodiment. FIG. 44 is a screen used instead of the task input screen of FIG. In FIG. 44, a patient name column 414 and an examination data column 415 are provided below the patient ID column 405.

  In this embodiment, after the 1st calculation control part 11 receives the input of the patient name to the patient name column 414, the 2nd calculation control part 21 converts into patient ID with reference to patient DB256. In response to an instruction from the second calculation control unit 21, the first calculation control unit 11 outputs the patient ID to the patient ID column 405. Furthermore, when there is a patient who may possibly mistake the name, such as a patient with the same surname, a notice to that effect may be displayed on the screen.

  The examination data column 415 displays patient examination data taken from the electronic medical chart. The examination data displayed here is a result of an infectious disease examination that is necessary in common during examination and surgery.

  According to the present embodiment, since the patient name and examination data are displayed during the input of the task record, an easy-to-use user interface can be realized.

[Embodiment 8]
In the case of the small-scale information processing system 4, a large-capacity storage device such as a hard disk drive mounted on the operation terminal 1 may be used as the second large-capacity storage unit 25 of the server 2. In this case, the first calculation control unit 11 also serves as the second calculation control unit 21. With such a configuration, the information processing system 4 can be constructed with a single computer.

  A plurality of operation terminals 1 may be connected by the network 3, and NAS (Network Attached Storage) connected to the network 3 may be used as the second mass storage unit 25. In this case, the first calculation control unit 11 also serves as the second calculation control unit 21. With such a configuration, the information processing system 4 can be constructed with a general-purpose personal computer, and the dedicated server 2 is not required, so that an inexpensive information processing system 4 can be constructed.

  The operation terminal 1 may adopt a so-called thin client type configuration in which only necessary minimum processing is performed and the CPU of the server 2 connected via the network 3 controls input / output operations described below. It becomes easier to take information security measures such as preventing the data in the DB from being taken outside. Furthermore, the additional investment at the time of system expansion such as the addition of the operation terminal 1 can be kept low. Furthermore, a so-called cloud service on the network may be used as the CPU of the server 2 and the mass storage device.

[Embodiment 9]
In the ninth embodiment, when there is an overlap between the task being input and the existing reservation, if the participation start time is different, the overlapping reservation is possible. 45 and 46 are explanatory diagrams showing images of the reservation DB 253 according to the ninth embodiment. 47 and 48 are explanatory diagrams showing images of the task input screen according to the ninth embodiment. FIG. 49 is an explanatory diagram showing an image of the reservation DB 253 according to the ninth embodiment. Note that the structure of the reservation DB 253 in this embodiment is the same as that shown in FIGS. 6 to 9, and the doctor C is cut out in FIGS. 45, 46, and 49.

  The recording state of the reservation DB 253 according to this embodiment will be described with reference to FIGS. 45 and 46. As shown in FIG. 45, doctor C has a schedule of surgery for the right cervical hernia of the patient with the patient ID “BBBBBBB” from 10:35 to 11:15. However, a case will be described in which it is necessary to perform a diagnosis of the patient ID “DDDDDD” from 10:45 in parallel with the operation. If it is 10 minutes from 10:45, the operation of the patient ID “BBBBBBB” can be handled only by another doctor in charge, so no problem occurs even if the doctor C leaves the operating room. In such a case, as shown in FIG. 46, a diagnosis of “DDDDDD” is reserved from 10:45.

  The reservation input method according to the present embodiment will be described with reference to FIGS. In FIG. 47, it is going to make a reservation for the examination of the patient ID “DDDDDDD” for 10 minutes from 10:35 to 10:45. However, a message indicating that the appointment cannot be accepted is displayed because the existing right appointment cervical hernia operation for the patient ID “BBBBBBB” and the participation start time coincide with 10:35.

  On the other hand, in FIG. 48, an appointment is made for a diagnosis of the patient ID “DDDDDDD” for 10 minutes from 10:45 to 10:55. Although it is a time zone that overlaps the right cervical hernia operation of the patient ID “BBBBBBB” that is an existing reservation, since the participation start time of both does not match, a message to inquire whether or not the reservation can be forced is displayed Yes. Here, when the second arithmetic control unit 21 accepts the selection of “Yes”, the reservation of the patient ID “DDDDDDD” is confirmed and recorded in the reservation DB 253 as shown in FIG. From the record in the reservation DB 253 alone, the scheduled end time of the examination of the patient ID “DDDDDDD” is not known, but it is understood that the doctor C has an appointment. The examination end time of the patient ID “DDDDDDD” can be confirmed by retrieving the task record from the task DB 254. When the task record corresponding to the patient ID “DDDDDDD” is not recorded in the task DB 254, it is understood that the examination is a unit time. Therefore, no problem occurs.

  Similarly, as shown in FIG. 49, in the case where the doctor C is scheduled to perform a diagnosis of the patient ID “DDDDDD” for 10 minutes from 10:45 to 10:50, in the same manner, “BBBBBB” right heel neck surgery can be reserved. Also in this case, the reservation DB 254 after the reservation of the patient ID “BBBBBBB” is in the state shown in FIG.

  FIG. 50 is a flowchart illustrating a processing procedure of the information processing system 4 according to the ninth embodiment. With reference to FIG. 50, the flow of processing of the information processing system 4 of the present embodiment will be described. Note that description of portions common to FIG. 22 is omitted. The process from the start of processing until the second calculation control unit 21 determines the state of the end button flag (step S510) is the same as in FIG. If the end button flag is not set (NO in step S510), the second arithmetic control unit 21 starts a double-booking check subroutine (step S851). The double-booking check subroutine determines whether there is a duplication between the doctor, comedy, and medical device schedule of the task being entered and the existing appointment recorded in the appointment DB 253, and permits duplicate registration if necessary. Is a subroutine. Processing in the double booking check subroutine will be described later.

  The second arithmetic control unit 21 determines the state of the duplication flag (step S852). The duplication flag is a flag indicating whether or not duplication reservation is allowed. When the duplication flag is set, it indicates that the setting for permitting duplication reservation in the double booking check subroutine is performed. If it is determined that the duplication flag is set (YES in step S852), the second calculation control unit 21 activates a task record storage subroutine (step S513). The task record storage subroutine is the same as that shown in FIG. Thereafter, the second calculation control unit 21 starts a reservation DB recording subroutine (step S853). Thereafter, the process ends. The reservation DB recording subroutine is a subroutine for reflecting the contents of the task being input to the reservation DB 253 including duplicate reservations. Processing in the reservation DB recording subroutine will be described later.

  If the second calculation control unit 21 determines that the duplication flag is not set (NO in step S852), the second calculation control unit 21 sets or cancels the end flag (step S512). Specifically, if the input task is in a registerable state, the second calculation control unit 21 sets an end possible flag. If the registration is impossible, the second calculation control unit 21 cancels the end possible flag (step S512). Thereafter, the process returns to step S509.

  51 and 52 are flowcharts showing the processing procedure of the double booking check according to the ninth embodiment. As described above, the double-booking check subroutine determines whether or not there is a duplication between the appointment of the doctor, comedy and medical device of the task being entered and the existing reservation recorded in the reservation DB 253. This subroutine allows duplicate registration. With reference to FIG. 51 and FIG. 52, the flow of processing of the subroutine of the double booking check will be described. Note that description of portions common to FIGS. 28 and 29 is omitted. The process from the start of the process to the end of the task being input by the second arithmetic control unit 21 is determined (step S609), and is common to FIG. If not completed (NO in step S609), 1 is added to counter I (step S610), and the process returns to step S605.

  If all tasks in the task list have been confirmed (YES in step S609), the second arithmetic control unit 21 determines whether the “warning device list” and the “warning person list” are empty ( Step S671). If both lists are not empty (YES in step S671), the second calculation control unit 21 instructs the first calculation control unit 11 to display a message (step S672). The content of the message indicates that the entered task can be registered. The first calculation display unit 11 outputs a message instructed to the first display unit 14 (step S673), and then the double booking check subroutine ends.

  If the “warning device list” or “warning person list” is not empty (NO in step S671), the second arithmetic control unit 21 determines whether the first unit time of the existing reservation and the input reservation are overlapping. It is determined whether or not (step S722). Whether the first unit time overlaps is determined by the fact that the patient ID has already been recorded in the first unit time of the task being input. If the first unit times overlap (YES in step S722), the second calculation control unit 21 instructs the first calculation control unit 11 to display a message indicating that the reservation cannot be accepted (step S723). ). As shown in FIG. 47, the first arithmetic control unit 11 outputs a message indicating that the reservation cannot be accepted as shown in FIG. 47 (step S724), and the double booking check subroutine ends.

  If the first unit time does not overlap (NO in step S722), the second calculation control unit 21 instructs the first calculation control unit 11 to inquire whether or not the reservation can be forced (step S725). As shown in FIG. 49, the first arithmetic control unit 11 outputs a message asking whether or not reservation forced execution is possible as shown in FIG. 49 (step S726). When receiving the input (step S727), the first calculation control unit 11 transmits the received content to the second calculation control unit 21. The second arithmetic control unit 21 determines whether or not the received content allows forcing the reservation (step S728).

  If it is determined that an input permitting forced reservation is accepted (YES in step S728), the second calculation control unit 21 sets a duplication flag (step S729), and the double booking check subroutine ends. If it is determined that an input that permits reservation reservation is not accepted (NO in step S728), the second calculation control unit 21 cancels the duplication flag (step S730), and the double booking check subroutine ends.

  FIGS. 53 and 54 are flowcharts showing the processing procedure of reservation DB recording according to the ninth embodiment. As described above, the reservation DB recording subroutine is a subroutine for reflecting the contents of the task being input to the reservation DB 253 including duplicate reservations. With reference to FIGS. 53 and 54, the processing flow of the reservation DB recording subroutine will be described. Note that description of portions common to FIGS. 30 to 33 is omitted.

  The second calculation control unit 21 sets the counter I to 1 and initializes the suspended task list to be blank (step S861). The second calculation control unit 21 extracts a reservation record including the participation start time of the I-th participant in the task record being input from the reservation DB 253 (step S862). The second arithmetic control unit 21 determines whether or not the I-th participant is participating in another task during the time period when the reservation record is extracted (step S863). Participation is determined by the fact that “999999” of the previous time zone is recorded in the patient ID field of the I-th participant. If it is determined that it is participating (YES in step S863), the second calculation control unit 21 examines the record in the reservation DB 253 retroactively to the start time zone of the participating task, and the patient ID, content, and remarks of the predecessor task. Is recorded in the suspended task list (step S864). Note that recording in the suspended task list is performed by adding to the already recorded content.

  When it is determined that it is not participating (NO in step S863) and after the end of step S864, the second calculation control unit 21 stores the patient ID of the task being input in the field of the I-th person in the retrieved reservation record, Contents and remarks are recorded (step S865).

  The second calculation control unit 21 takes out a reservation record for the next time zone from the reservation DB 253 (step S866). The second arithmetic control unit 21 determines whether or not the time zone in which the reservation record is extracted is a time zone during which the I-th participant is participating in the task being input (step S867). In the case of the participating time zone (YES in step S867), the second calculation control unit 21 determines whether or not the patient ID is recorded in the patient ID field of the I-th participant in the reservation record extracted in step S866. Is determined (step S868). If there is a record (YES in step S868), the second calculation control unit 21 records the patient ID, contents, and remarks recorded in the field indicating the I-th participant in the reservation record in the suspended task list. (Step S869). Note that recording in the suspended task list is performed by adding to the already recorded content. If there is no record (NO in step S868), the second calculation control unit 21 records “999999” in the patient ID field of the I-th participant in the reservation record (step S870). After step S869 or step S870 ends, the process returns to step S866.

  If the time zone in which the reservation record is extracted in step S866 is not the time zone in which the task being input is participating (NO in step S867), the second arithmetic control unit 21 determines that all the people who participate in the task being input It is determined whether or not the process has been completed (step S871). If it is determined that all the processes have not been completed (NO in step S871), 1 is added to the counter I (step S872), and the process returns to step S862.

  If it is determined that all the processes have been completed (YES in step S871), the second calculation control unit 21 records the reservation of the medical device used for the input task in the reservation DB 253 (step S872). The medical device reservation is the same as step S631 to step S635 in FIG. When the recording of the medical device reservation is completed, the second calculation control unit 21 stores the reservation DB 253 (step S873). The second arithmetic control unit 21 outputs the suspended task list (step S874), and the about DB recording subroutine ends. Note that the output destination of the suspended task list may be the second large-capacity storage unit 25 or an output device such as a printer of the second display unit 24.

  According to the present embodiment, it is possible to make a schedule so that medical activities such as diagnosis and treatment of many patients can be performed by effectively utilizing the gap time.

[Embodiment 10]
In the tenth embodiment, when a duplicate reservation is made, the time zone scheduled to return to the previously executed task is recorded in the reservation DB 253. FIG. 55 is an explanatory diagram showing an image of the reservation DB 253 according to the tenth embodiment.

  The recording state of the reservation DB 253 according to this embodiment will be described with reference to FIG. FIG. 55 shows the same schedule as in the ninth embodiment. That is, from 10:35 to 11:15, doctor C, who is scheduled to undergo surgery for the right cervical hernia of the patient with the patient ID “BBBBBBB”, moves from 10:45 to 10:55 in parallel with the operation. The patient ID “DDDDDD” is also examined in parallel. In FIG. 55, it is recorded in the reservation record at 10:55 that the doctor C participates in the operation of the patient ID “BBBBBBB”. That is, it can be seen that the doctor C who leaves the right cervical hernia operation of the patient “BBBBBBB” returns to the same operation at 10:55 once at 10:45. This content is displayed in the schedule list field 401 on the initial screen of the information processing system 4 shown in FIG.

  56 and 57 are flowcharts showing the reservation DB recording processing procedure according to the tenth embodiment. The subroutine shown in FIGS. 56 and 57 is used in place of the subroutine shown in FIGS. 53 and 54. The processing flow of the reservation DB recording subroutine will be described with reference to FIGS. 56 and 57. FIG. Note that description of portions common to FIGS. 53 and 54 is omitted.

  The process from the start of the process until “999999” is recorded in the patient ID field of the I-th person (step S870) is the same as the process of FIGS. If the second calculation control unit 21 determines that it is not a time zone during participation in the task being input (NO in step S867), the patient ID field of the I-th participant in the reservation record extracted in step S866. It is determined whether or not there is a record “999999” (step S881). If it is determined that there is a record (YES in step S881), the second calculation control unit 21 finally passes step S869 in the field indicating the I-th participant in the reservation record extracted in step S866. The items recorded in the interrupted task list are copied (step S882).

  When it is determined that there is no record of “999999” (NO in step S881) and after the end of step S882, the second arithmetic control unit 21 determines whether or not the processing of all the persons participating in the input task has been completed. (Step S871). The subsequent processing is the same as “processing” in FIGS. 53 and 54.

  According to the present embodiment, it is possible to realize the information processing system 4 that displays in the schedule list column 401 the time period for returning from the duplicate reservation.

The technical features (components) described in each embodiment can be combined with each other, and new technical features can be formed by combining them.
The embodiments disclosed herein are illustrative in all respects and should not be considered as restrictive. The scope of the present invention is defined not by the above-described meaning but by the scope of the claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of the claims.

1 Operation terminal (first information processing device)
2 Server (second information processing device)
3 Network 4 Information processing system 253 Reservation DB
401 Schedule list field 403 Task input instruction button 404 End button 407 Task start time field 408 Task end time field 409 Person field
410 Device field 411 Contents field 412 Task ID field 421 Reservation status list

Claims (7)

On the computer,
Get the scheduled date and time of medical practice,
Obtain designation of physician and comedy participation and use of medical devices,
Obtaining the scheduled date and time of participation of the doctor and the comedian who have obtained designation of participation within the range of the scheduled date and time of use and the scheduled date and time of use of the medical device having obtained designation of use,
The planned participation date and time of the doctors and comedies who have received the designation of participation, and the presence or absence of duplication of the scheduled use date and time of the medical devices that have been designated for use. Judgment by referring to the reservation database that records
If it is determined that there is no duplication in any of the doctor, comedy medical, and medical device reservations, the doctor or comedy that has obtained the designation of participation, the scheduled date and time of participation, the medical device that has obtained the designation of use, and Output the acquired scheduled use date and time to the reservation database,
Whether if it is determined that there is the overlapping reservation doctor or co Medical, the start date and time of the prospective participant date and time acquired, the start date of the reservation is duplicated is recorded in the reservation database match Determine whether
If it is determined that the start dates and times do not match, the reservation database includes the doctor or comedy who has obtained the designation of participation, the scheduled date and time of participation, the medical device that has obtained the designation of use, and the acquired scheduled date and time of use. Output to
A program that executes a process of outputting information indicating duplication when it is determined that the start dates coincide . The program according to claim 1 , wherein after executing the scheduled execution date and time, a process of outputting a list of reservation statuses of doctors, comedies or medical devices in a time zone including the scheduled execution date and time is executed. Get a scheduled date and time for a non-medical practice by a doctor or comedy,
Determine whether there is any overlap between the acquired schedule and the reservation recorded in the reservation database,
The program according to claim 1 or 2 , wherein when it is determined that there is no duplication, a process of outputting the acquired schedule to the reservation database is executed.   On the computer,
  Get two or more items of the start time, end time, and required time of the scheduled date and time of medical practice,
  Obtain designation of physician and comedy participation and use of medical devices,
  Acquire two or more items from the start time, end time, and required time of the planned participation date and time of each doctor and comedy who have received the designation of participation in a part of the range from the start to the end of the scheduled execution date and time. ,
  Obtain two or more items of the start time, end time, and required time of the scheduled use date and time of the medical device for which designation of use has been acquired, as part of the range from the start to the end of the scheduled execution date and time,
  The planned participation date and time of the doctors and comedies who have received the designation of participation, and the presence or absence of duplication of the scheduled use date and time of the medical devices that have been designated for use. Judgment by referring to the reservation database that records
  When it is determined that there is a duplication in the appointment of a doctor, comedy or medical device, information indicating the duplication is output.
A program that executes processing. In an information processing system using a first information processing apparatus and a second information processing apparatus connected to the first information processing apparatus via a network,
The first information processing apparatus
A first acquisition unit that acquires the scheduled date and time of medical practice;
A second obtaining unit for obtaining designation of participation of a doctor and a medical and designation of use of a medical device;
A third acquisition unit that acquires a scheduled date and time of participation of a doctor and a comedy who have obtained designation of participation within the range of the scheduled date and time of use, and a scheduled use date and time of a medical device that has acquired designation of use; A first output unit that outputs the information acquired by the third acquisition unit to the second information processing apparatus;
The second information processing apparatus
A first receiving unit for receiving information output from the first output unit;
The planned participation date and time of the doctors and comedies who have received the designation of participation, and the presence or absence of duplication of the scheduled use date and time of the medical devices that have been designated for use. A determination unit that determines with reference to the reservation database that records
If the determination unit determines that there is an overlap in the appointment of the doctor or comedy, the acquired start date / time of the scheduled participation date and the start date / time of the overlapping reservation recorded in the reservation database are the same. A second determination unit for determining whether or not
When the determination unit determines that there is no duplication in any of the doctor, the comedy, and the medical device reservation, the doctor or comedy who has obtained the designation of participation, the obtained scheduled participation date and time, and the designation of use have been obtained. The medical device and the acquired scheduled use date and time are output to the reservation database, and if the second determination unit determines that the start dates and times do not match, the doctor or comedical who acquired the designation of participation, acquisition A third output unit for outputting the scheduled participation date and time, the medical device that acquired the designation of use, and the acquired scheduled use date and time to the reservation database;
A system comprising: a second output unit that outputs information indicating duplication to the first information processing apparatus when the second determination unit determines that the start dates and times coincide with each other . The first information processing apparatus
When the information specifying the patient who is the drug is dragged to the position where the doctor or comedy and the participation start date and time are specified, the specified doctor or comedy and the start date and time of participation and the information specifying the patient are displayed. A third output unit for outputting to the second information processing apparatus;
The second information processing apparatus
A second receiving unit that receives information output from the third output unit;
The system according to claim 5, further comprising: a recording processing unit that records in the reservation database the doctor or comedy received by the second receiving unit, the participation start date and time, and information specifying the patient in association with each other. Get the scheduled date and time of medical practice,
Obtain designation of physician and comedy participation and use of medical devices,
Obtaining the scheduled date and time of participation of the doctor and the comedian who have obtained designation of participation within the range of the scheduled date and time of use and the scheduled date and time of use of the medical device having obtained designation of use,
The planned participation date and time of the doctors and comedies who have received the designation of participation, and the presence or absence of duplication of the scheduled use date and time of the medical devices that have been designated for use. Judgment by referring to the reservation database that records
If it is determined that there is no duplication in any of the doctor, comedy medical, and medical device reservations, the doctor or comedy that has obtained the designation of participation, the scheduled date and time of participation, the medical device that has obtained the designation of use, and Output the acquired scheduled use date and time to the reservation database,
Whether if it is determined that there is the overlapping reservation doctor or co Medical, the start date and time of the prospective participant date and time acquired, the start date of the reservation is duplicated is recorded in the reservation database match Determine whether
If it is determined that the start dates and times do not match, the reservation database includes the doctor or comedy who has obtained the designation of participation, the scheduled date and time of participation, the medical device that has obtained the designation of use, and the acquired scheduled date and time of use. Output to
An information processing method for causing a computer to execute a process of outputting information indicating duplication when it is determined that the start dates coincide .

Images