Dialysis information management system, dialysis information management method, and dialysis information management program
The dialysis information management system automates patient information sorting by using a database and estimator to predict and highlight relevant patient data, reducing operator workload and improving efficiency in accessing patient information.
Patent Information
- Application Number
- JP2020210768
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-12-18
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-12-18
AI Technical Summary
The existing medical care support systems require operators to manually search and sort through large patient lists, increasing workload due to the lack of automated patient information rearrangement.
A dialysis information management system that includes a database storing patient information, treatment timing, and operation history, with an estimator to predict and highlight likely patient information for operations, reducing the need for manual sorting.
Automated estimation and display of patient information reduces operator workload by eliminating the need for manual searching and narrowing down, allowing easier access to desired patient data.
Smart Images

Figure 0007585763000001 
Figure 0007585763000002 
Figure 0007585763000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a dialysis information management system, a dialysis information management method, and a dialysis information management program. [Background technology]
[0002] In the medical field, a medical support system has been disclosed that provides a patient list that consolidates the patient information of multiple patients and allows medical staff to view the patient list in order to smoothly advance treatment for patients (Patent Document 1). For example, the medical support system disclosed in Patent Document 1 has a function for sorting the display order of patient names included in the patient list. This sort function makes it possible to rearrange the display order of the patient list, such as by displaying the patient name of the patient information that the operator wishes to view at the top of the patient list, depending on the scheduled date of surgery application and the progress of the medical treatment process. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2018-185820 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, the rearrangement of the display order of patient information (patient names) in the display list disclosed in Patent Document 1 is performed by the system operator himself / herself. When there are a large number of patients, after rearranging the patient information, the operator needs to perform further operations such as searching and narrowing down, which imposes a large workload on the operator.
[0005] The object of the present disclosure is to provide a dialysis information management system, a dialysis information management method, and a dialysis information management program that can reduce the workload of an operator when viewing desired patient information. [Means for solving the problem]
[0006] In order to achieve the above-mentioned object, the dialysis information management system according to the first aspect of the present disclosure includes a memory unit in which a database related to hemodialysis treatment is stored, the database including patient information related to hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and implementation timing information for hemodialysis treatment for each hemodialysis patient, and operation history information including input operation information related to input operations performed on the database; an estimation unit that estimates and outputs patient information to be operated on from the database based on at least one of the treatment timing information and the operation history information; and a display control unit that displays the patient information output by the estimation unit on a display.
[0007] A dialysis information management method for managing information related to hemodialysis treatment according to a second aspect, which manages information related to hemodialysis treatment for hemodialysis patients, comprises the steps of storing, in a database related to hemodialysis treatment, patient information related to hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and information on the timing of hemodialysis treatment for each hemodialysis patient, and operation history information including input operation information related to input operations performed on the database, estimating and outputting patient information to be operated on from the database based on at least one of the treatment timing information and the operation history information, and displaying the outputted patient information on a display.
[0008] A dialysis information management program for managing information related to hemodialysis treatment according to a third aspect, which causes a computer processor to execute the following processes: storing, in a database related to hemodialysis treatment, patient information related to hemodialysis patients, treatment timing information including at least one of hemodialysis treatment reservation timing information and hemodialysis treatment implementation timing information for each hemodialysis patient, and operation history information including input operation information related to input operations performed on the database; estimating and outputting patient information to be operated on from the database based on at least one of the treatment timing information and the operation history information; and displaying the outputted patient information on a display. Effect of the Invention
[0009] According to the configurations of the first to third aspects, the patient information to be operated is estimated and the estimated patient information is displayed on the display, eliminating the need for the operator to rearrange the patient information or narrow down the patient information. As a result, the workload of the operator can be reduced when viewing desired patient information. [Brief description of the drawings]
[0010] [Figure 1] 1 is a block diagram showing a schematic configuration of a dialysis information management system according to one embodiment. FIG. [Diagram 2] FIG. 13 is a diagram for explaining the display of a patient list according to one embodiment. [Diagram 3] FIG. 2 is a diagram for explaining a configuration of a database according to an embodiment. [Figure 4] FIG. 2 is a block diagram showing a configuration of an operation terminal according to an embodiment. [Diagram 5] FIG. 2 is a block diagram showing a configuration of a server according to an embodiment. [Figure 6] FIG. 2 is a functional block diagram showing a configuration of a control unit according to one embodiment. [Figure 7] FIG. 2 illustrates an example of a database according to one embodiment. [Figure 8]FIG. 2 is a diagram for explaining a visit date and time history database in a database according to an embodiment. [Figure 9] FIG. 13 is a diagram for explaining a treatment end date and time history database in a database according to one embodiment. [Figure 10] FIG. 10 is a diagram for explaining information indicating a current situation in a database according to one embodiment. [Figure 11] FIG. 13 is a diagram for explaining an operation history database in a database according to an embodiment. [Figure 12] 11A and 11B are diagrams for explaining sorting patterns in estimation information according to an embodiment. [Figure 13] 11 is a diagram for explaining function settings in estimation information according to an embodiment. FIG. [Figure 14] FIG. 11 is a diagram for explaining a first example of creating a patient list according to one embodiment. [Figure 15] FIG. 11 is a diagram for explaining a second example of creating a patient list according to one embodiment. [Figure 16] FIG. 13 is a diagram for explaining a display before estimation processing on the display unit in the first example of creating a patient list. [Figure 17] FIG. 13 is a diagram for explaining a display before estimation processing on the display unit in the second example of creating a patient list. [Figure 18] FIG. 13 is a diagram for explaining the display after estimation processing on the display unit in the second example of creating a patient list. [Figure 19] FIG. 11 is a diagram for explaining a third example of creating a patient list according to one embodiment. [Figure 20] FIG. 13 is a diagram for explaining the display on the display unit in a fourth example of creating a patient list. [Figure 21] FIG. 13 is a diagram for explaining a fourth example of creating a patient list. [Figure 22] FIG. 2 is a flow chart for explaining the control process of the dialysis information management system according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference characters and their description will not be repeated.
[0012] [Outline of the dialysis information management system] 1 and 2 are diagrams showing a schematic configuration of a dialysis information management system 100 according to the present embodiment. As shown in Fig. 1, the dialysis information management system 100 is a system for managing information related to hemodialysis treatments performed in a plurality of hemodialysis apparatuses 1. Specifically, the dialysis information management system 100 includes an operation terminal 2 and a server 3. The hemodialysis apparatuses 1, the operation terminal 2, and the server 3 are connected to each other so as to be able to communicate with each other via a network such as a wireless or wired LAN.
[0013] As shown in FIG. 2, the dialysis information management system 100 of this embodiment is configured to, when medical staff and administrative staff operate the operation terminal 2, estimate patient information D1 to be operated next from the database 34a (described later) of the server 3, and display the estimated patient information D1 or a patient list E2, which is a list of estimated patients, on the display unit 24 (display) of the operation terminal 2.
[0014] FIG. 3 is a diagram for explaining an overview of the database 34a. Here, the database 34a stores patient information D1, treatment time information D2, operation history information D3, and dialysis condition information D4. The patient information D1 is information about a hemodialysis patient, and includes personal information of the patient, such as a patient ID, name, kana, sex, date of birth, and address. The treatment time information D2 includes reservation time information D21 for hemodialysis treatment for each hemodialysis patient, and implementation time information D22 for hemodialysis treatment for each hemodialysis patient. For example, the reservation time information D21 includes information on the day of the week when the patient is scheduled to visit the hospital, as described later. The implementation time information D22 includes, for example, a past visit date and time and a past treatment end date and time. The operation history information D3 includes input operation information D31 regarding an input operation performed on the database 34a, and an operator ID for identifying an operator who performed an input operation on the database 34a. The input operation information D31 is stored in the database 34a in a state associated with the operator ID.
[0015] As shown in Fig. 2, the server 3 estimates and outputs a plurality of pieces of patient information D1 to be operated from the database 34a based on at least one of the treatment timing information D2 and the operation history information D3. Then, the display unit 24 of the operation terminal 2 displays a patient list E2, which is a list of the patient information D1 estimated and output by the server 3. In addition, the patient information D1 (patient ID "P005" and name "Takahashi Saburo" in Fig. 2) that is likely to be operated in the patient list E2 is highlighted (part E2a). Examples of the highlighting method include changing the background color compared to the surroundings, making the font size larger than other patient information, and making the font bolder than other patient information.
[0016] According to the above configuration, the patient information D1 to be operated is estimated, and the estimated patient list E2 is displayed on the display unit 24. As a result, for example, when a doctor gives instructions for treatment of a patient, when a nurse records treatment performed on a patient, or when an office staff member updates personal information of a patient, the patient information D1 (patient list E2) that the doctor is attempting to operate or view can be displayed on the display unit 24. As a result, staff members including doctors and nurses do not need to search for patients in the database 34a, and the workload of the staff members can be reduced.
[0017] When the patient information D1 is estimated based on the treatment time information D2, for example, the patient information D1 related to the current time and the reservation time of the treatment or the implementation time of the treatment is displayed, so that the operator (staff member) can easily view the patient information D1 to be operated. Also, when the patient information D1 is estimated based on the operation history information D3, the patient information D1 that is likely to be the target of the operation can be appropriately estimated based on the input operation information D31 performed on the database 34a in the past.
[0018] In addition, since the estimated multiple pieces of patient information D1 are displayed on the display unit 24 as a patient list E2, it is possible to improve the possibility that the patient information D1 that the operator (staff member) desires to view or operate is displayed, compared to the case where a single piece of patient information D1 is displayed. Furthermore, since the patient information D1 that is likely to be the object of operation is highlighted, the operator (staff member) can easily visually recognize the patient information D1 (highlighted display E2a) that is likely to be the object of operation.
[0019] [Configuration of each part of the dialysis information management system and configuration of the hemodialysis machine] Next, the configuration of each part of the dialysis information management system 100 and the configuration of the hemodialysis device 1 will be described with reference to Fig. 1 and Figs. 3 to 7. The hemodialysis device 1 (see Fig. 1) is disposed, for example, in a dialysis room. For example, the hemodialysis device 1 is installed next to (near) a bed on which a patient lies. The hemodialysis device 1 is a device that performs hemodialysis treatment according to dialysis conditions set by an operator. Dialysis condition information D4, which is information on the dialysis conditions, is stored in the database 34a of the server 3. The dialysis conditions are various conditions set for each patient in dialysis treatment, such as dialysis time, blood flow rate, drugs used, their dosages, and administration conditions.
[0020] (Operation terminal configuration) The operation terminal 2 is, for example, a personal computer. The operation terminal 2 is operated by a medical staff or an office staff. The operation terminal 2 is configured to refer to (display) and update the database 34a of the server 3 based on an input operation by the medical staff or the office staff during dialysis treatment. The operation terminal 2 is installed in, for example, an examination room, but may be installed in any location other than the examination room (for example, a hospital reception desk, a nurse station, a dialysis room, etc.). The operation terminal 2 may also be configured as a mobile device such as a tablet. Here, in the present disclosure, the "input operation" is not limited to newly inputting character information, but is a broad concept including an operation to update or delete information, an operation to select or extract patient information D1, and an operation to select the contents of a function (the icons of "Doctor's Instructions", "Nursing Record", and "Dialysis Record" in FIG. 2).
[0021] Furthermore, the operation terminal 2 performs user authentication to allow the medical staff or administrative staff to operate the dialysis information management system 100. For example, the medical staff or administrative staff inputs an operator ID, which is their own ID, and a password into the operation terminal 2. The operation terminal 2 or the server 3 (a login processing unit 31e described later) performs user authentication based on the input operator ID and password. When the user authentication is completed in the operation terminal 2 or the server 3, the authenticated person is logged in. For example, FIG. 2 shows an example of a state in which a person with an operator ID "N005" is logged in. Note that any method such as reading an IC card or biometric authentication can be used for user authentication.
[0022] Fig. 4 is a block diagram showing the configuration of the operation terminal 2. As shown in Fig. 4, the operation terminal 2 includes a control unit 21, an input unit 22, a communication unit 23, and a display unit 24. The control unit 21 is a processor (control circuit) that executes control processing in the operation terminal 2. The input unit 22 is an input device that receives input from the outside, such as a touch panel, a touch pen, a button key, a keyboard, or a mouse. The communication unit 23 is an interface for communicating with the hemodialysis device 1 and the server 3 via a wired and / or wireless network. The display unit 24 is a display that displays an image based on a command from the control unit 21, such as a liquid crystal display.
[0023] (Server configuration) Fig. 5 is a block diagram showing the configuration of the server 3. As shown in Fig. 5, the server 3 includes a control unit 31, a memory 32, a communication unit 33, and a storage unit 34. The server 3 may be configured as an on-premise server installed in a medical facility, or may be configured as a cloud server virtually configured by a plurality of computers installed in different locations.
[0024] The control unit 31 is, for example, a processor (control circuit) that operates an operating system to control the entire server 3. Furthermore, the control unit 31 operates based on a program stored in the memory 32 to control each part. The memory 32 is a readable storage medium, and is composed of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. The memory 32 stores, for example, a program for the control unit 31 to control each part. The communication unit 33 is an interface for communicating with the hemodialysis device 1 and the operation terminal 2 via a wired and / or wireless network. The storage unit 34 stores a database 34a and estimation information 34b. The estimation information 34b includes information on a sort pattern when automatically sorting multiple pieces of patient information D1 in order to estimate the patient information D1 to be operated, or a learned model by machine learning, as will be described in detail later.
[0025] FIG. 6 is a functional block diagram showing the configuration of the control unit 31. As shown in FIG. 6, the control unit 31 includes a memory control unit 31a, a display control unit 31b, an estimation control unit 31c, an on / off setting unit 31d, and a login processing unit 31e. The memory control unit 31a updates the database 34a and the estimation information 34b based on the operator of the operation terminal 2. The display control unit 31b has a function of displaying a screen (see FIG. 2) for inputting operations to the database 34a on the display unit 24 of the operation terminal 2, and displaying a patient list E2 on the display unit 24. The estimation control unit 31c has a function of estimating patient information D1 that is likely to be the subject of an operation when a certain operator logs in, extracting it from the database 34a, and generating a patient list E2. The on / off setting unit 31d has a function of allowing each operator to select on / off information indicating whether or not to use the function of the estimation control unit 31c, and storing the information in the database 34a in association with the operator ID. The login processing unit 31e has a function of acquiring an operator ID for identifying an operator who is attempting to perform an input operation (attempting to log in) to the database 34a, and performing login processing (the above-mentioned user authentication).
[0026] FIG. 7 is a diagram for explaining an example of a part of the database 34a. As shown in FIG. 7, the database 34a stores patient information D1. As described above, the patient information D1 includes personal information such as a patient ID, a name, a kana, a sex, a date of birth, and an address. The database 34a also stores information on the day of visit in association with the patient information D1 as reservation time information D21 of the treatment time information D2. Here, in the case of a dialysis treatment patient, the day of the week on which the patient visits the hospital is generally determined in advance, and a reservation is made for the day of visit. The "day of visit information" indicates the day of the week on which the dialysis treatment patient is scheduled to visit the hospital. For example, the day of visit is three times a week on Tuesday, Thursday, and Saturday, or three times a week on Monday, Wednesday, and Friday. The information on the day of visit includes information on the time period. For example, in the case of a patient with a patient ID "P001" in FIG. 7, a reservation is made for dialysis treatment on Tuesday "morning", Thursday "afternoon", and Saturday "morning". Although the time zone information of patients other than "P001" is omitted in FIG. 7, the information of the visit reservations (day of the week and time zone) of the other patients is similarly stored in the database 34a.
[0027] In addition, the database 34a stores input operation information D31 of the operation history information D3 and the operator ID as information associated with the patient information D1. The input operation information D31 includes, for example, information indicating which patient the operation of updating or deleting was performed on, information indicating which patient information D1 was selected or extracted, and information indicating which function content (icons of "Doctor's Instructions", "Nursing Records", and "Dialysis Records" in FIG. 2) was selected. The input operation information D31 is stored in the database 34a in a state associated with the operator ID. Note that FIG. 7 shows an example in which, as information on doctor's instructions, a doctor inputs, for example, from the operation terminal 2, changes to the dosage of medicine in dialysis treatment, such as "The blood pressure dropped too much last time, so this time I will give less medicine." The input contents are stored in the database 34a together with information on the operator who input the change history (operator ID) and information indicating the input date and time. In addition, if the operator is a nurse, the comment may include the contents of the treatment performed and an observation on the state of the patient during dialysis treatment. Furthermore, the comment may be input to the database 34a by the operator selecting from a plurality of standard phrases stored in the storage unit 34 in advance.
[0028] In addition, the database 34a stores dialysis condition information D4 in association with patient information D1. In addition, when a patient visits the hospital, the database 34a stores bed number information in association with the patient information D1. The bed number is the number of the bed assigned to the dialysis patient on the day of the dialysis treatment, and is registered, for example, when the dialysis patient checks in for the dialysis treatment.
[0029] Here, the operation history information D3 is cumulatively stored for at least a predetermined period of time. As a result, the database 34a is configured to be able to retroactively refer to past operation content information, such as operation content information from the previous visit and operation content information from the visit before last. As other information, the database 34a includes data on the treatment status. However, what is included in the database 34a is not limited to the above-mentioned contents.
[0030] (Configuration for estimating the next patient information to be operated) 8 to 19, a configuration for estimating the next operated patient information D1 by the dialysis information management system 100 in this embodiment will be described. The next operated patient information D1 is estimated by the estimation control unit 31c of the control unit 31 based on the database 34a and the estimation information 34b.
[0031] <Database details> 8, the implementation time information D22 of the treatment time information D2 in the database 34a includes the visit date and time. For example, the server 3 obtains the time when the result of the "pre-treatment weight measurement" of the patient is input as the "visit date and time" and records it in the database 34a in association with the patient ID of the patient. In this way, the history of the visit date and time of each patient is accumulated and recorded in the database 34a for at least a certain period of time.
[0032] In the following, "before treatment" refers to the period before the time when the patient's "pre-treatment weight measurement" results are input (i.e., the "visit date and time"). "After treatment" refers to the period after the patient's "post-treatment weight measurement" results are input. "During treatment" refers to the period after the patient's "pre-treatment weight measurement" results are input and before the patient's "post-treatment weight measurement" results are input.
[0033] 9, the implementation time information D22 includes information on the treatment end date and time. The treatment end date and time information is information that associates the date and time and the day of the week when the patient's dialysis treatment (treatment on the day of the visit) ended with the patient ID of the patient. Here, the server 3 acquires, for example, the time when the result of the patient's "post-treatment weight measurement" is input as the "treatment end date and time."
[0034] 10, the appointment time information D21 in the database 34a also includes status information indicating the current status of each patient who has an appointment to visit the hospital on that day. The status information indicates "Waiting to visit" for patients at future hospitals, and indicates the arrival time for patients who have already visited the hospital.
[0035] As shown in FIG. 11, the database 34a stores operation history information D3 related to input operations performed on the database 34a. Each time a doctor, nurse, or the like accesses the database 34a and performs some input operation, the operation history information D3 is stored in the database 34a (storage unit 34) in association with the operator ID, and includes the date and time when the input operation was performed, the patient ID of the data that was the target of the operation, and the operation content. Note that the operation history information D3 also includes information that the input operation was not performed by the operator. Also, as shown in FIG. 11, the input operation information D31 of the operation history information D3 includes input time information indicating whether the input operation was performed "before treatment," "during treatment," or "after treatment."
[0036] In detail, as shown in FIG. 11, before treatment, a doctor (doctor with operator ID "D003") may use the operation terminal 2 to input a doctor's instruction to the database 34a of the server 3. Also, before treatment, an office staff member (staff member with operator ID "G005") may use the operation terminal 2 to input information to the database 34a of the server 3 in order to update patient information. Also, during treatment, in addition to dialysis treatment, a nurse may perform treatment or a doctor may make rounds. In this case, a nurse (nurse with operator ID "N005") may use the operation terminal 2 to input a nursing record (record of treatment content) to the database 34a of the server 3. Also, a doctor (doctor with operator ID "D004") may use the operation terminal 2 to input a doctor's instruction based on the rounds to the database 34a of the server 3. After the treatment, a nurse (nurse with operator ID "N005") may use the operation terminal 2 to input dialysis records (vital information during dialysis treatment, etc.) into the database 34a of the server 3. A doctor (doctor with operator ID "D003") may use the operation terminal 2 to input doctor's instructions based on rounds into the database 34a of the server 3. Thus, in the dialysis information management system 100, staff of various occupations perform various operations on the database 34a at each treatment period as operators involved in dialysis treatment.
[0037] <Configuration of Estimation Information> 12 is a diagram for explaining an example of the information for estimation 34b. The information for estimation 34b is information used when the estimation control unit 31c estimates the patient information D1 to be operated and extracts it from the database 34a. For example, the information for estimation 34b includes information on a pattern for automatically sorting (rearranging) the patient information D1, or a learned model by machine learning.
[0038] For example, as shown in FIG. 12, in the sort pattern "A11", when the day of the week on which the operator is operating is "Thursday", the estimation control unit 31c automatically sorts the patient information D1 in reverse order from the day of the week on which the operator is operating or the previous day of the week, based on the estimation information 34b and the reservation time information D21. For example, when the current day is "Thursday", the patient information D1 is automatically sorted so that the patient information D1 for which the previous visit day was "Tuesday" is placed at the top. With this configuration, it is possible to extract the patient information D1 for which the day of the week on which the estimation is performed is a day on which hemodialysis treatment is performed ("Tuesday", "Thursday", "Saturday"). As a result, since the patient information D1 for which hemodialysis treatment is not performed ("Monday", "Wednesday", "Friday") is not displayed on the display, for example, when a doctor is about to perform an input operation on the data of a patient who visited the hospital on Tuesday, the doctor can easily find the desired patient data.
[0039] The inference control unit 31c also automatically sorts the patient information D1 operated by the operator on the day before the login day as a sort pattern "A12" so that the patient information D1 operated by the operator on the day before the login day is placed at the top. The inference control unit 31c also automatically sorts the patient information D1 operated by the operator on the day before the login day as a sort pattern "A21" so that the patient information D1 for which the time elapsed since the operator last operated the input operation is placed at the top (sorting is performed based on the order of the input operation). With this configuration, the patient information D1 to be the target of the next operation is estimated according to the order of the input operation. As a result, for example, when a nurse tries to input nursing records in the order in which treatments were performed on patients, the patient list E2 is displayed on the display unit 24 by estimation based on the order of past input. As a result, the nurse can simply input the patient information in the order displayed, eliminating the need to search for the patient information D1 every time an operation is performed.
[0040] Furthermore, the inference control unit 31c automatically sorts the patient information D1 for which the operator has not yet performed an input operation, by referring to the operation history information D3, as the sort pattern "A22", so that the patient information D1 for which the operator has not yet performed an input operation is placed at the top. The inference control unit 31c then automatically sorts the patient information D1 for which the operator has performed an input operation a long time ago, below the patient information D1 for which the operator has not performed an input operation. Furthermore, when there is no patient for which the input operation has not been performed, the inference control unit 31c automatically sorts the patient information D1 for which the operator has performed an input operation a long time ago, to the top. As a result, for example, the patient information D1 of a patient who is a first-time patient and for whom the operator (for example, a doctor) has not performed an input operation is displayed at the top, eliminating the need to search for a first-time patient (a patient for whom the operator has not performed an input operation).
[0041] In addition, as a sort pattern "A23", the patient information D1 input at a time that matches the operation content is automatically sorted to be at the top. In other words, the time corresponding to the operation content (for example, "nursing record") is automatically sorted so that the patient information D1 input at the corresponding time ("during treatment" and "after treatment") among before, during, and after treatment is at the top by referring to the input time information. Here, in hemodialysis treatment, the order of patients and the order of treatments that the medical staff deals with change depending on whether it is before, during, or after treatment. For example, the object (patient information D1) that the nurse wants to view changes depending on the time when the nurse operates the system. Therefore, according to the above configuration, it is determined which of the above periods the current time is, and an estimate is made based on the determined time, so that the operator can view more appropriately estimated patient information. For example, if the "nursing record" is inputted "during treatment" or "after treatment", the patient information D1 inputted "during treatment" or "after treatment" is automatically sorted to be at the top.
[0042] In addition, as the sorting pattern "A24", the patient information D1 with the earliest visit date and time is automatically sorted based on the implementation time information D22 so that the patient information D1 is ranked higher. In the case of dialysis treatment, the order in which patients visit the hospital is approximately the same for each day of the week. With this configuration, the patient information D1 is automatically sorted in the order in which the patients visit the hospital, so that the workload of the operator can be further reduced when inputting the patient information into the database 34a in the order in which the patients visit the hospital.
[0043] FIG. 13 shows an example of information in which information on whether or not to use the function of the estimation control unit 31c (on / off information) is associated with an operator ID as the estimation information 34b. As shown in FIG. 13, the estimation control unit 31c refers to the "on / off information" corresponding to the logged-in operator ID, and when the information is "on (the function of the estimation control unit 31c is used)", it performs a process of estimating the patient information D1 to be operated, and when the information is "off (the function of the estimation control unit 31c is not used)", it does not perform a process of estimating the patient information D1 to be operated. According to this configuration, the function of the estimation control unit 31c can be applied only to an operator who wishes to use the function of the estimation control unit 31c among multiple operators. As a result, even if the multiple operators differ in whether or not they need the estimation function, all of the multiple operators can use the dialysis information management system 100.
[0044] FIG. 14 shows an example of the patient list E2 displayed on the display unit 24 when the operator ID "N005" selects the "Dialysis Record" icon (see FIG. 16) at "9:33" on "Thursday" while logged in. As shown in FIG. 14, the estimation control unit 31c sorts the patient information D1 of the previous day of the week "Tuesday" at the top by sorting by "A11". Then, the patient information D1 operated by the operator "N005" is sorted at the top. By sorting by "A23", the "Dialysis Record" is information input during or after treatment, so that the patient information D1 in the state corresponding to during or after treatment (see FIG. 10 and FIG. 11) is sorted at the top. For example, "N005" is assumed to "use the function of the estimation control unit 31c". Note that the currently displayed patient information D1 (patient information D1 being input) is not sorted at the top. As a result of these, for example, "P003", "P005", "P008" and "P009" are extracted as patient information D1 presumed to be the next target to be operated, and as shown in FIG. 2, a patient list E2 is displayed as a pop-up image (another window image) on the display unit 24 in addition to the patient list E1 before sorting. Then, "P005" is highlighted as the patient information D1 that is likely to be the target of operation. Note that the patient list E1 may display the patient's name together with the patient ID "P005", or may display only the patient's name instead of the patient ID "P005".
[0045] FIG. 15 shows an example of the patient list E2 displayed on the display unit 24 when the operator ID "D003" selects the "Doctor's Instructions" icon (see FIG. 17) at "9:12" on "Thursday" while logged in. As shown in FIG. 15, the estimation control unit 31c sorts the patient information D1 of the patient who visited the hospital last time on "Tuesday" at the top by sorting by "A11". Then, the patient information D1 operated by the operator "D003" is sorted at the top. The patient information D1 is sorted by sorting by "A21" in order of the elapsed time since the last operation by "D003". Note that the currently displayed patient information D1 (patient information D1 being input) is not sorted at the top. Also, it is assumed that "D003" "uses the function of the estimation control unit 31c". As a result, for example, "P003", "P005", "P003" and "P008" are extracted as patient information D1 estimated to be the next target to be operated, and as shown in Fig. 18, a patient list E2 is displayed as a pop-up image (another window image) on the display unit 24 in addition to the patient list E1 before sorting. Then, as shown in Fig. 15, "P003" is highlighted as patient information D1 that is likely to be the target of operation. Note that "P003" in the patient list E2 is estimated twice, but since there is an overlap, one of the "P003" is not displayed on the display unit 24 in Fig. 18.
[0046] FIG. 19 shows an example of the patient list E2 displayed on the display unit 24 when the operator ID "D003" selects the "Dialysis Record" icon (see FIG. 17) at "9:33" on "Thursday" while logged in. As shown in FIG. 19, the estimation control unit 31c sorts the patient information D1 of the previous day of the week "Tuesday" at the top by sorting with "A11". Then, the patient information D1 operated by the operator "D003" is sorted at the top. The patient information D1 is sorted in the order of visit by sorting with "A24". Note that the currently displayed patient information D1 (patient information D1 being input) is not sorted at the top. Also, it is assumed that "D003" "uses the function of the estimation control unit 31c". As a result, for example, "P003", "P002", and "P008" are extracted as the estimated patient information D1, and the patient list E2 is displayed as a pop-up image (another window image) for the patient list E1 before sorting on the display unit 24. Then, "P003" is highlighted as the patient information D1 that is likely to be the target of an operation.
[0047] 20 and 21 show an example of the patient list E2 displayed on the display unit 24 when the operator ID "D003" selects the "Doctor's Instructions" icon (see FIG. 17) at "12:50" on "Thursday" while logged in. As shown in FIG. 21, the estimation control unit 31c sorts the patient information D1 operated by the operator "D003" to the top. Then, by sorting by "A22", the patient information D1 of patients for whom the doctor "D003" has never performed an input operation is sorted to the top, and the patient information D1 is sorted in descending order of the elapsed time since the last operation by "D003". For example, it is assumed that the patient "P020" is a new patient, and the doctor "D003" has never performed an input operation on the patient information D1 of the patient. In addition, it is assumed that "D003" "uses the function of the estimation control unit 31c". As a result of these, for example, "P020", "P018", and "P017" are extracted as patient information D1 presumed to be the next target to be operated, and as shown in Fig. 20, a patient list E2 is displayed as a pop-up image (another window image) for the patient list E1 before sorting on the display unit 24. Then, as shown in Fig. 20, "P020" (Kimura Saburo) is highlighted as the patient information D1 that is likely to be the target of operation.
[0048] [Dialysis information management method] The dialysis information management method according to this embodiment will be described with reference to Fig. 22. Fig. 22 is a flow diagram of control processing by the control unit 31 of the dialysis information management system 100. Note that patient information D1, treatment timing information D2, and operation history information D3 are stored in advance (before step S1) in the database 34a.
[0049] In step S1, an operator logs in. That is, the operator inputs an operator ID and a password.
[0050] In step S2, the input operation screen (FIG. 16 or 17) is displayed on the display unit 24, and the pre-estimated patient list E1 is displayed on the display unit 24.
[0051] In step S3, it is determined whether or not to use the function of the estimation control unit 31c (whether it is on or off). If the function of the estimation control unit 31c is to be used (if it is on), the process proceeds to step S4, and if the function of the estimation control unit 31c is not to be used (if it is off), the process proceeds to step S6.
[0052] In step S4, a plurality of pieces of patient information D1 to be the target of the next operation are estimated, and a patient list E2 is created. Then, in step S5, the patient list E2 of the patient information D1 estimated to be the target of the next operation is displayed on the display unit 24. In addition, the patient information D1 in the patient list E2 that is likely to be the target of the operation is highlighted.
[0053] In step S6, input operation information D31, which is information input by the operator, is acquired. Then, in step S7, information in which the input operation information D31 is associated with the operator ID is stored as operation history information D3 in the database 34a and the estimation information 34b. This updates the database 34a and the estimation information 34b.
[0054] According to the above method, the patient information D1 to be operated is estimated and the estimated patient information D1 is displayed on the display unit 24, eliminating the need for the operator to rearrange the patient information D1 or narrow down the patient information D1. As a result, the workload of the operator can be reduced when viewing desired patient information D1.
[0055] [Variations] The above-described embodiment is merely an example for carrying out the present invention. Therefore, the present invention is not limited to the above-described embodiment, and the above-described embodiment can be appropriately modified and carried out without departing from the spirit of the present invention.
[0056] For example, in the above embodiment, an example is shown in which both the treatment time information D2 and the operation history information D3 are used to estimate the patient information D1 to be operated, but this is not limited to this. That is, it is sufficient to use at least one of the treatment time information D2 and the operation history information D3 to estimate the patient information D1 to be operated.
[0057] In the above embodiment, the patient list E2 is displayed on the display unit 24 of the operation terminal 2, but this is not limiting. For example, if the server 3 is provided with a display unit, the patient list E2 may be displayed on the display unit.
[0058] In the above embodiment, the days of the week on which hemodialysis treatment is performed are, for example, "Tuesday", "Thursday", "Saturday", "Monday", "Wednesday", and "Friday", but are not limited to these. For example, "Monday" and "Thursday" may also be used.
[0059] In the above embodiment, the example in which whether the state is before treatment, during treatment, or after treatment is determined based on the input of the weight measurement result is shown, but the present invention is not limited to this. For example, whether the state is before treatment, during treatment, or after treatment may be determined based on the operator's operation on the operation terminal 2 (for example, an operation of inputting "start of treatment" or "end of treatment").
[0060] In the above embodiment, the patient list E2 is created by estimating a plurality of pieces of patient information D1 to be operated, but the present invention is not limited to this. That is, only one piece of patient information D1 to be operated may be estimated, and the single piece of patient information D1 may be displayed on the display unit 24.
[0061] In addition, each process described in the above embodiment may be realized by hardware, or may be realized by software (including the case where it is realized together with an OS (operating system), middleware, or a predetermined library). Furthermore, it may be realized by a mixed process of software and hardware.
[0062] The present disclosure can also be explained as follows.
[0063] The dialysis information management system of the first configuration includes a memory unit in which a database related to hemodialysis treatment is stored, the database including patient information on hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and information on when hemodialysis treatment is performed for each hemodialysis patient, and operation history information including input operation information regarding input operations performed on the database; an estimation unit that estimates and outputs patient information to be operated on from the database based on at least one of the treatment timing information and the operation history information; and a display control unit that displays the patient information output by the estimation unit on a display (first configuration).
[0064] According to the first configuration, the patient information to be operated is estimated and the estimated patient information is displayed on the display, so that the operator does not need to rearrange the patient information or narrow down the patient information. As a result, the operator's workload can be reduced when viewing desired patient information. Here, when the patient information is estimated based on the treatment time information, for example, patient information related to the current time and the reservation time of treatment or the implementation time of treatment is displayed, so that the operator can easily view the patient information to be operated. Also, when the patient information is estimated based on the operation history information, the patient information that is likely to be the target of the operation can be appropriately estimated based on the input operation information performed on the database in the past.
[0065] In the first configuration, the reservation time information may include information on the day of the week on which hemodialysis treatment is performed, and the estimation unit may be configured to estimate and output patient information in the database in which the day of the week on which hemodialysis treatment is performed includes the current day as the patient information to be operated (second configuration).
[0066] Here, hemodialysis patients are generally provided with hemodialysis treatment on specific days of the week (for example, Tuesday, Thursday, and Saturday). In response to this, the second configuration described above makes it possible to extract from the database patient information on which the day of the week on which hemodialysis treatment is performed includes the current day of the week (the day of the treatment). As a result, patient information on which hemodialysis treatment is not performed is not displayed on the display, allowing the operator to easily recognize the desired patient information.
[0067] In the first or second configuration, the operation history information includes the operator ID of the operator who performed the input operation in association with the input operation information, and further includes a login processing unit that acquires the operator ID of the operator who is about to perform an input operation on the database, and the estimation unit estimates and outputs the patient information that is the target of the operation from the database by referring to the input operation information associated with the operator ID acquired by the login processing unit (third configuration).
[0068] According to the third configuration, it is possible to estimate the patient information to be operated from the database according to the operator (logged-in operator) who is going to perform an input operation to the database. As a result, it is possible to estimate appropriate patient information based on the operator's own past operation history.
[0069] In the third configuration, an on / off setting unit is further provided which allows each operator to select on / off information indicating whether or not to use the function of the estimation unit, and stores the information in the database in association with the operator ID. When the on / off information associated with the operator ID acquired by the login processing unit is on, the estimation unit estimates and outputs patient information to be operated from the database (fourth configuration).
[0070] According to the fifth configuration, the function of the estimation unit can be applied only to an operator who desires to use the function of the estimation unit among a plurality of operators. As a result, even if the necessity of the estimation function differs among a plurality of operators, the plurality of operators can use the present system.
[0071] In any of the first to fourth configurations, the input operation information for each hemodialysis patient includes input order information representing the order in which input operations were made to the database for that hemodialysis patient among a plurality of hemodialysis patients, and the estimation unit estimates and outputs the patient information to be the target of the next operation from the database based on the patient information currently displayed on the display and the input order information (fifth configuration).
[0072] According to the fifth configuration, the patient information of the patient to be operated next is estimated according to the order of input operations. This eliminates the need for the operator to extract and select patient information from the database for each operation when operating the data of multiple patients sequentially.
[0073] In any of the first to fifth configurations, the implementation time information includes information on the time when the hemodialysis patient started treatment and information on the time when the hemodialysis patient finished treatment, and the input operation information includes input time information indicating whether the time when the input operation was made to the database was before treatment, during treatment, or after treatment, and the estimation unit estimates and outputs the patient information to be operated on from the database based on the information indicating whether the current time is before treatment, during treatment, or after treatment and the input time information (sixth configuration).
[0074] In hemodialysis treatment, the order in which the medical staff treats patients and the order of treatments change depending on whether it is before, during, or after treatment. In other words, the subject (patient information) that the operator (medical staff) wants to view changes depending on when the operator operates the system. Therefore, according to the sixth configuration, it is determined which of the above periods the current time falls into, and patient information is estimated based on the determined time, so that the operator can view more appropriately estimated patient information.
[0075] In any of the first to sixth configurations, the estimation unit may be configured to estimate multiple patient information to be operated from the database based on at least one of the treatment timing information and the operation history information, and to output an operation target list corresponding to the estimated multiple patient information, and the display control unit may be configured to display the operation target list on the display (seventh configuration).
[0076] According to the seventh configuration, the estimated multiple patient information are displayed on the display as a list of patients to be operated, thereby improving the likelihood that the patient information that the operator desires to view or operate is displayed compared to when a single piece of patient information is displayed.
[0077] In the seventh configuration, the estimation unit may be configured to extract patient information that is likely to be a target of operation from the operation target list, and the display control unit may be configured to display the operation target list on a display and highlight, on the display, the patient information that is likely to be a target of operation from the operation target list (eighth configuration).
[0078] According to the eighth configuration, even when multiple pieces of patient information are displayed on the display, the patient information that is likely to be the target of operation is highlighted, so that the operator can easily see the patient information that is likely to be the target of operation.
[0079] A dialysis information management method according to a ninth configuration is a dialysis information management method for managing information regarding hemodialysis treatment for hemodialysis patients, and includes the steps of storing, in a database regarding hemodialysis treatment, patient information regarding hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and information regarding the timing of hemodialysis treatment for each hemodialysis patient, and operation history information including input operation information regarding input operations performed on the database, estimating and outputting patient information to be the subject of operation from the database based on at least one of the treatment timing information and the operation history information, and displaying the outputted patient information on a display (ninth configuration).
[0080] According to the ninth configuration, similarly to the first configuration, it is possible to reduce the workload of the operator when the operator views desired patient information.
[0081] The dialysis information management program of the tenth configuration causes a computer processor to execute the following processes: storing patient information about hemodialysis patients, treatment timing information including at least one of hemodialysis treatment reservation timing information and hemodialysis treatment implementation timing information for each hemodialysis patient, and operation history information including input operation information regarding input operations performed on the database; estimating and outputting patient information that is the subject of operation from the database based on at least one of the treatment timing information and the operation history information; and displaying the outputted patient information on a display (tenth configuration).
[0082] According to the tenth configuration, similarly to the first configuration, it is possible to reduce the workload of the operator when the operator views desired patient information. [Explanation of symbols]
[0083] 24...display unit, 31...control unit, 31a...storage control unit, 31b...display control unit, 31c...estimation control unit, 31d...on / off setting unit, 31e...login processing unit, 34...storage unit, 34a...database, 100...dialysis information management system, D1...patient information, D2...treatment time information, D21...reservation time information, D22...implementation time information, D3...operation history information, D31...input operation information, E2...patient list, E2a...highlighting
Claims
1. a storage unit in which a database relating to hemodialysis treatment is stored, the database including: patient information relating to hemodialysis patients; treatment timing information including at least one of reservation timing information for hemodialysis treatment and implementation timing information for hemodialysis treatment for each hemodialysis patient; and operation history information including input operation information relating to input operations performed on the database; an estimation unit that sorts the patient information in the database based on at least one of the treatment timing information and the operation history information, and outputs the top-ranked patient information among the sorted patient information in the database as the patient information to be operated from the database; A display control unit that displays the patient information output by the estimation unit on a display, the input operation information for each hemodialysis patient includes input order information representing an order in which an input operation was performed on the database for that hemodialysis patient among a plurality of hemodialysis patients; The reservation time information for each hemodialysis patient includes day of the week information that is a day on which the hemodialysis treatment is scheduled to be performed, The estimation unit is a first sorting so as not to place the patient information currently displayed on the display at a higher position, and to place the patient information in the database for which the time elapsed since the previous input operation is short or long with reference to the input order information at a higher position; and a second sorting such that the patient information currently displayed on the display is not placed at the top, and such that the patient information in the database in which the current day of the week is included in the day of the week information is placed at the top by referring to the day of the week information; A dialysis information management system that outputs the top-ranked patient information among the rearranged patient information in the database from the database as the patient information to be subjected to the next operation.
2. The reservation time information includes information on the day of the week on which the hemodialysis treatment is to be performed, The dialysis information management system according to claim 1 , wherein the estimation unit estimates and outputs patient information in the database in which the current day of the week is included in the day of the week in which the hemodialysis treatment is performed as the patient information to be operated.
3. the operation history information includes an operator ID of an operator who performed the input operation in association with the input operation information, A login processing unit that acquires an operator ID of an operator who is going to perform an input operation on the database, 3. The dialysis information management system according to claim 1, wherein the estimation unit estimates and outputs patient information to be operated from the database by referring to input operation information associated with the operator ID acquired by the login processing unit.
4. an on / off setting unit that allows an operator to select on / off information indicating whether or not to use a function of the estimation unit, and stores the on / off information in the database in association with an operator ID; The dialysis information management system according to claim 3, wherein the estimation unit estimates and outputs patient information to be operated from the database when on / off information associated with the operator ID acquired by the login processing unit is on.
5. The implementation time information includes information on a time when the hemodialysis patient started treatment and information on a time when the hemodialysis patient finished treatment, the input operation information includes input time information indicating whether the time point when the input operation was performed on the database was before treatment, during treatment, or after treatment; The dialysis information management system according to any one of claims 1 to 4, wherein the estimation unit estimates and outputs patient information to be operated from the database based on information indicating whether the current time corresponds to a period before treatment, during treatment, or after treatment, and the input time information.
6. The estimation unit estimates a plurality of pieces of patient information to be operated from the database based on at least one of the treatment timing information and the operation history information, and outputs an operation target list corresponding to the estimated plurality of pieces of patient information; The dialysis information management system according to any one of claims 1 to 5, wherein the display control unit causes the display to display the operation target list.
7. The estimation unit extracts patient information that is likely to be a target of operation from the operation target list, The dialysis information management system according to claim 6, wherein the display control unit displays the operation target list on the display and highlights, on the display, patient information in the operation target list that is likely to be a target of the operation.
8. A dialysis information management method for managing information regarding hemodialysis treatment of a hemodialysis patient, comprising: storing, in a database relating to hemodialysis treatment, patient information relating to hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and implementation timing information for hemodialysis treatment for each of the hemodialysis patients, and operation history information including input operation information relating to input operations performed on the database; A step of sorting the patient information in the database based on at least one of the treatment timing information and the operation history information, and outputting the top-ranked patient information among the sorted patient information in the database from the database as the patient information to be operated; and displaying the outputted patient information on a display. the input operation information for each hemodialysis patient includes input order information representing an order in which an input operation was performed on the database for that hemodialysis patient among a plurality of hemodialysis patients; The reservation time information for each hemodialysis patient includes day of the week information that is a day on which the hemodialysis treatment is scheduled to be performed, The outputting step includes: a first sorting so as not to place the patient information currently displayed on the display at a higher position, and to place the patient information in the database for which the time elapsed since the previous input operation is short or long with reference to the input order information at a higher position; and a second sorting such that the patient information currently displayed on the display is not placed at the top, and such that the patient information in the database in which the current day of the week is included in the day of the week information is placed at the top by referring to the day of the week information; A dialysis information management method performed by a computer, comprising outputting from the database the top-ranked patient information among the rearranged patient information in the database as the patient information to be subjected to a next operation.
9. The computer processor A process of storing, in a database relating to hemodialysis treatment, patient information relating to hemodialysis patients, treatment timing information including at least one of reservation timing information for hemodialysis treatment and implementation timing information for hemodialysis treatment for each of the hemodialysis patients, and operation history information including input operation information relating to input operations performed on the database; A process of sorting the patient information in the database based on at least one of the treatment timing information and the operation history information, and outputting the top-ranked patient information among the sorted patient information in the database from the database as the patient information to be operated; and displaying the outputted patient information on a display. the input operation information for each hemodialysis patient includes input order information representing an order in which an input operation was performed on the database for that hemodialysis patient among a plurality of hemodialysis patients; The reservation time information for each hemodialysis patient includes day of the week information that is a day on which the hemodialysis treatment is scheduled to be performed, The output process includes: a first sorting so as not to place the patient information currently displayed on the display at a higher position, and to place the patient information in the database for which the time elapsed since the previous input operation is short or long with reference to the input order information at a higher position; and a second sorting such that the patient information currently displayed on the display is not placed at the top, and such that the patient information in the database in which the current day of the week is included in the day of the week information is placed at the top by referring to the day of the week information; A dialysis information management program that includes a process of outputting the top-ranked patient information among the rearranged patient information in the database from the database as the patient information to be subject to a next operation.
Citation Information
Patent Citations
Diagnosis / Treatment data processor
JP1995271874A
Data processing system
JP2006301809A
Person-in-charge determining method, person-in-charge determining apparatus, and person-in-charge determining program
JP2018151956A
Medical examination support device, operation method and operation program for medical examination support device, and medical examination support system
JP2018185820A
Hemodialysis patient data acquisition, management and analysis system
US20100113891A1
