Graphical user interface for vital sign data entry

Abstract

This system provides a GUI for inputting vital sign data that simplifies input and improves the readability of input results. [Solution] The system comprises multiple elements 213 arranged in a matrix, and when one of these elements is selected, a row header 211 and a column header 212 are marked. When the selection of an element 213 is confirmed, a command is executed to retrieve the characters assigned to these headers and register them in a table along with the date and time.

Description

Technical Field

[0001] The present invention relates to a graphical user interface for inputting vital sign data used at the care site, and particularly relates to one effective for use in excretory care.

Background Art

[0002] In care facilities, the introduction of care record applications is progressing. This changes from the conventional handwritten recording of information to the recording of information by electronic input through a graphical user interface (hereinafter referred to as GUI), aiming to improve the efficiency and speed of operations, centralize information management, and share information among care staff. In particular, the working hours of care staff can be shortened, and an improvement in QOL can be expected.

[0003] In particular, excretory assistance is a work situation that care staff feel burdensome ( "Results of additional questionnaire survey on care facilities regarding burden reduction effect", Ministry of Land, Infrastructure, Transport and Tourism survey in 2023), and the care time also occupies a considerable proportion of the day ( "Results of survey on the actual state of care for the elderly", Ministry of Health, Labour and Welfare survey in 2021).

[0004] Care recipients with a high degree of care need not only cannot excrete independently but also may not even have a sense of excretion. Caregivers have to go to the recipient's hospital bed at an appropriate time, open the diaper, and check for excretion. However, since the condition of the care recipient is not always constant, the excretion time changes daily. Therefore, caregivers often open the recipient's diaper even when there is no excretion. Naturally, the QOL of both care staff and care recipients decreases, making it difficult to achieve well-being.

[0005] On the other hand, the nature of excrement is an important vital sign and is closely related to the disease currently being suffered from, so the recording of the nature of excrement is essential. Therefore, care staff are often provided with recording input terminals such as tablets installed with care record applications.

[0006] Patent Document 1 provides an example of a GUI for recording excretion. Figure 11 shows its details. Figure 11 is an input screen for stool volume and its characteristics displayed on the display of an excretion care terminal, and the GUI is constructed using various buttons. On the left side of the screen is a stool volume input field 91 for entering the stool volume, and on the right side is a characteristics input field 92 for entering the characteristics. Below, a confirmation button 93 labeled "OK" and a cancellation button 94 labeled "Cancel" are arranged side by side. The stool volume input button 911, characteristics input button 921, confirmation button 93, and cancellation button 94 are elements created using a predetermined programming language. When a caregiver performs an action such as tapping or clicking on the stool volume input button 911 or characteristics input button 921, those elements become selected, and if the caregiver then performs an action such as tapping or clicking on the confirmation button 93, the command associated with that element is executed.

[0007] For example, if the stool volume input button 911 labeled "small" is selected, and the consistency input button 921 labeled "watery stool" is selected, tapping the confirmation button 93 will execute the command, and a numerical value or other character indicating that the stool volume is small and the stool is watery will be saved to the terminal or server. In addition, to visually inform the caregiver that these buttons have been selected, commands that change the text color or background color in response to actions such as taps or clicks may also be executed (Figure 12). [Prior art documents] [Patent Documents]

[0008] [Patent Document 1] Japanese Patent Application Publication No. 2022-072766 [Overview of the Initiative] [Problems that the invention aims to solve]

[0009] Previous GUIs for recording bowel movements, such as the example in Patent Document 1, required users to individually select the amount and characteristics of their stool, which was cumbersome. In other examples, pop-up windows would appear during input, or users had to swipe to move to the next input screen, resulting in poor readability of the bowel movement record results. Furthermore, the lack of analysis functions meant that the acquired data was not being utilized.

[0010] In view of the above problems, one of the objectives of the present invention is to provide a GUI for inputting vital sign data that simplifies input and improves the readability of input results. [Means for solving the problem]

[0011] To solve the above problems, a graphical user interface for inputting vital sign data according to one embodiment is displayed on the terminal's display and comprises a plurality of first elements arranged in a matrix, one second element, row headers arranged in each row of the plurality of first elements, and column headers arranged in each column of the plurality of first elements, wherein one of the row headers or column headers is accompanied by an image showing the amount of excrement, and the other is accompanied by an image showing the quality of the excrement, and in response to the selection of one of the plurality of first elements, at least a portion of the row headers in the same row as the element and at least a portion of the column headers in the same column as the element are marked, and each of the row headers and column headers is assigned a different character, and in response to the selection of the second element, a command is executed to retrieve the characters assigned to each of the marked row headers and column headers and register them in a table along with the date and time. Here, the first element may be a selectable visualized block, and the second element may be a button.

[0012] Furthermore, if the excrement is stool, the image indicating the quality of the excrement may be the shape of the stool; if the excrement is urine, the image indicating the quality of the excrement may be the color of the urine. Furthermore, it further comprises multiple third elements, each of which is accompanied by a string of characters and an image indicating a different urine volume level, and is assigned a different character. The selection of the second element may trigger the execution of a command to retrieve the character assigned to the third element and register it in the table. Here, the third element may be a selectable visualized block.

[0013] Furthermore, a graphical user interface for inputting vital sign data according to another embodiment is displayed on the terminal's display and comprises a plurality of first elements arranged in a matrix, one second element, row headers arranged for each row of the plurality of first elements, and column headers arranged for each column of the plurality of first elements, wherein either the row header or the column header is accompanied by an image showing the amount of excrement, and the other is accompanied by an image showing the quality of the excrement, and in response to the selection of one of the plurality of first elements, at least a portion of the row headers in the same row as the selected element and the row headers in the same column as the selected element are displayed. At least a portion of the column headers are marked, and all of the row headers and column headers are assigned different characters. The selection of the second element temporarily stores the characters assigned to each of the marked row headers and column headers, and executes a command to display a confirmation screen. The confirmation screen displays the temporarily stored characters. The confirmation screen further comprises a fourth element, and the selection of the fourth element executes a command to register the temporarily stored characters along with the date and time in the table. Here, the fourth element may be a button.

[0014] The characters and dates and times registered in the table are visualized in a time-series heatmap or bar graph using a predetermined data visualization library, and the heatmap or bar graph may be used to analyze the excretion tendencies of a care recipient unit or an individual care recipient. The heat map may display excessive excretion frequency in different shades of color, and the bar graph may color-code the excretion frequency for each time period by excretion type (defecation and urination, defecation and urination). Also, fecal incontinence and urinary incontinence may be color-coded and displayed together.

Advantages of the Invention

[0015] According to one aspect of the present invention, by arranging the selection elements in a matrix, a GUI for vital sign data input with simple input and high listability can be provided. Also, according to another aspect of the present invention, by recording the characters assigned to the elements in a table, a GUI for vital sign data input that contributes to creating an analysis graph based on the table data can be provided.

Brief Description of the Drawings

[0016] [Figure 1] It is a system diagram showing the electronic device environment in a care facility. [Figure 2] It is a diagram showing the hardware architecture. [Figure 3] It is a diagram showing the GUI according to the first embodiment. [Figure 4] It is a diagram showing the GUI according to the first embodiment. [Figure 5] It is a diagram comparing the first embodiment and the conventional example in a flowchart. [Figure 6] It is a diagram showing the GUI according to the second embodiment. [Figure 7] It is a flowchart of the GUI according to the second embodiment. [Figure 8] It is a map displayed by a web application using the GUI of the present invention. [Figure 9] It is a graph displayed by a web application using the GUI of the present invention. [Figure 10] It is a graph displayed by a web application using the GUI of the present invention. [Figure 11] This is a diagram showing a GUI according to a conventional example. [Figure 12] This is a diagram showing a GUI according to a conventional example.

Embodiments for Carrying Out the Invention

[0017] Hereinafter, embodiments of the present invention will be described with reference to FIGS. 1 to 10. In each of the following embodiments, parts that are identical or equivalent to each other are denoted by the same reference numerals and will be described.

[0018] <Regarding the Network> FIG. 1 is a system diagram showing an electronic device environment 10 in a care facility. Various devices 122 to 125 inside or outside the care facility, including the tablet terminal 121, can transmit and receive data to and from each other via the network 110. This network can be a cloud, a local area network (LAN), a wide area network (WAN), etc. Although not shown, data transfer devices such as routers are interposed between the network 110 and each electronic device, and data transmission and reception between the electronic device and the router etc. are performed via wiring, as well as via wireless protocols such as WiFi and Bluetooth or via mobile phone lines such as LTE and 5G.

[0019] Also, in a web application, it is common to register the front - end source code in the storage device 1114 of the server 111 to form a server system that shares information among each electronic device. However, it is also possible to register the front - end source code only in the storage device 1214 of the tablet terminal 121 and have a data server at the back - end. The present invention can be applied to any system, but will be described as a server architecture using the former system unless otherwise specified.

[0020] <Regarding Hardware> Figure 2 shows the hardware architecture of a tablet terminal 121 and a server 111 located on a network 110. The server 111 is equipped with a processor 1111, ROM 1112, RAM 1113, storage device 1114, and communication device 1115, which are interconnected via a system bus 1110. On the other hand, the tablet terminal is equipped with a CPU 1211, ROM 1212, RAM 1213, storage device 1214, display 1216, and communication device 1217, which are interconnected via a system bus 1210. Here, the processor 1111 may include a CPU, etc. Data is transmitted and received between the tablet terminal 121 and the server 111 via communication devices 1217 and 1115.

[0021] Both the processor 1111 and the CPU 1211 are units that perform calculations based on user requests, etc. These units read data stored in ROM 1112 and ROM 1212 for calculation processing, temporarily store data to be processed or programs currently running in RAM 1113 and RAM 1213, and store the results of calculation processing in storage device 1114 and storage device 1214. The input device 1215 of the tablet terminal 121 is a pointing device such as a touch panel or mouse for inputting user requests, and the display 1216 displays the initial screen or images reflecting the results of calculation processing. If the input device 1215 is a touch panel, it is integrated with the display 1216.

[0022] <GUIについて> Display 1216 displays a GUI. A GUI is a visual interface for users to operate a computer or software, designed to allow users to operate it intuitively using graphical elements. The term "graphical elements" overlaps with the concept of the components described above, but in this specification, the term "elements" may also include transparent text boxes and other elements that are not visually displayed, so it may differ slightly from the definition of GUI described above.

[0023] Among the source code that forms the GUI, the front-end design elements are constructed using computer languages ​​(front-end languages) such as HTML, CSS, and JavaScript, and consist of a collection of components such as titles, dates, input fields, buttons, and links. In this specification, these components are not particularly distinguished, and those that can execute commands related to selection actions among user actions such as caregivers are referred to as "elements." Selection actions refer to actions such as tapping, touching, or bringing a finger or stylus close (hover input) when the input device 1215 of the tablet terminal 121 is a touch panel integrated with the display 1216, and mouse on-click, etc., when it is a separate device. In the detailed description of the invention in this specification, embodiments will be described using any of these selection actions as examples, but the present invention is not limited to those described and includes all selection actions using any pointing device (input device).

[0024] <First Embodiment> Figure 3 shows a GUI for inputting vital sign data according to the first embodiment of the present invention. The input GUI 20 consists of a stool input area 21, a urine input area 22, a leakage / abnormality input area 23, a care recipient ID input area 24, a field 25, and a confirmation button 26. The stool input area 21 consists of row headers 211, column headers 212, and stool selection blocks 213. The row headers 211 consist of 7 panels, and the column headers 212 consist of 5 panels. Along these, 7 x 5 = 35 stool selection blocks 213 (first elements) are arranged in a matrix.

[0025] In other words, each row is categorized by stool consistency, and each column is categorized by stool volume. Row header 211 displays the stool consistency, with rows 1 through 7 displaying images of the stool consistency alongside the text "hard stool," "slightly hard stool," "normal stool," "soft stool," "muddy stool," and "watery stool." Column header 212 displays the stool volume, with columns 1 through 5 displaying images of the stool volume alongside the text "adherent," "quail egg," "chicken egg," "one banana," and "more than one banana." Therefore, caregivers can instantly grasp the stool consistency and volume to be entered by looking at these images.

[0026] On the other hand, a urine input area 22 is provided to the right of the stool input area 21, and this area includes a urine selection block 221 (third element). Multiple urine selection blocks 221 are provided in this embodiment, each displaying a different urine volume level with text and images. Specifically, four text strings—full, 3 / 4 full, half full, and 1 / 4 full—are displayed side by side along with urine volume images representing those levels. The urine volume images depict a colored area representing urine against a transparent cylindrical container background. For example, the urine selection block 221 indicating full has the entire area of ​​the cylindrical container in the background as a colored area. Therefore, caregivers can instantly grasp the urine volume level to be entered by looking at these colored areas.

[0027] Below the urine input area 22, a leak / abnormality input area 23 is provided, which includes a leak / abnormality selection block 231. The leak / abnormality selection block 231 in this embodiment is provided for confirming that there is no leakage or abnormality of feces or urine. All four blocks are displayed assuming that there is no leakage or abnormality, but they may also be displayed assuming that there is leakage or abnormality. However, the definition of abnormal stool or abnormal urine may differ from one nursing facility to another, and it is not possible to uniquely determine what constitutes an abnormality, so it may be possible to display an input screen such as a pop-up screen after tapping the confirmation button 26 to record the details of the abnormality or to select from a list.

[0028] Above the stool input area 21 and urine input area 22, a care recipient ID input area 24 is provided, which includes an ID selection block 241. In this embodiment, the care recipient ID input area 24 has ID selection blocks 241 for 16 care recipients belonging to a unit where one care team provides care. Each block displays an ID that identifies the care recipient, but in this embodiment, the full name is displayed as the ID. However, for privacy reasons, numbers or symbols may be displayed instead of the full name.

[0029] Above the care recipient ID input area 24, there is a field 25 for displaying the date and time. This field 25 displays the time automatically obtained from the clock implemented in the terminal by a script. Below the leak / abnormality input area 23, there is a confirmation button 26 (second element). Tapping this button after completing various selections confirms the selection and executes the associated command.

[0030] Figure 4 shows an example of the moment when a selection block is selected in each area of ​​the input GUI 20 and the confirmation button 26 is tapped. As shown in this figure, the background color of all tapped selection blocks is changed, and in the toilet input area 21, the background color of not only the tapped selection block (toilet selection block 213) but also the selection blocks in the same row as the tapped selection block and between the selection block and the row header 211, as well as the row header 211, are changed. Similarly, in the column direction, the background color of the selection blocks in the same column as the tapped selection block and between the selection block and the column header 212, as well as the column header 212, are changed. At the same time, a check mark image, indicated by reference numeral 214, appears superimposed on the tapped selection block.

[0031] For reference, in the illustrated example, in the stool input area 21, the stool selection block 213 is selected where the row header 211 is in the row displaying "Normal stool" and the column header 212 is in the column displaying "One banana". In addition, in the urine input area 22, the urine selection block 221 displaying a 3 / 4 urine volume level is selected; in the leak / abnormality input area 23, all leak / abnormality selection blocks 231 are selected; and in the care recipient ID input area 24, the ID selection block 241 in the 1st row, 5th column is selected. The background color of the confirmation button 26 changes when the cursor is on it, and this color is maintained after tapping. Note that although the background color of these selection blocks (213, 221, 231, 241) and the confirmation button 26 are changed by the selection action, hatching or smudging may be added, the hue, tone or gradation of the background color may be changed, or these may be made to blink. In this specification, such commands are collectively referred to as markings.

[0032] The selection blocks, buttons, fields, strings, and images described above can be created and placed using HTML and CSS, while commands such as background color changes upon tapping or cursor hover, the appearance of checkmark images, and other actions can be implemented using JavaScript. These HTML, CSS, and JavaScript source codes, along with various images, are saved from the server to the device's browser cache or a designated folder in its storage device during the installation of the web application. When a request is made to display the input GUI20, the source code is read into the device's RAM and executed, and at the same time, images of stool shape, stool volume, and urine volume are read from the browser cache or the designated folder and displayed in their respective positions.

[0033] Furthermore, each of the selection blocks selected by tapping—the urine selection block 221, the leak / abnormality selection block 231, and the ID selection block 241—is assigned a character corresponding to its respective index. However, the character corresponding to the stool selection block 213, which is arranged in a matrix, has a different character than the other selection blocks. That is, it does not directly correspond to the index of the stool selection block 213, but rather to the index of the row header 211 in the same row and the column header 212 in the same column. Therefore, when any of the stool selection blocks 213 are selected, two characters will be selected: one assigned to the row header 211 in the same row and another assigned to the same column.

[0034] In the example in Figure 4, the character corresponding to the row heading "Regular Mail" and the character corresponding to the column heading "One Banana" are selected. When the confirmation button 26 is tapped, a command is executed and the data for these characters is registered in a table (not shown) along with the date and time. This table is created using HTML, and each time the confirmation button 26 is tapped, the character data and the date and time data are accumulated. The data stored in the table is designed to be editable, and a link button (not shown) can be provided on the input GUI 20 screen to display it. This allows caregivers to correct data they have entered incorrectly later. The table should be created in a designated folder on the terminal or in a database on the network. An API can be used to display the table in the network database.

[0035] Figure 5 shows the difference between the conventional example shown in Figures 11 and 12 and this embodiment shown in Figures 3 and 4 by comparing flowcharts. 30 is the flowchart of this embodiment, and 40 is the flowchart of the conventional example. Both flowcharts depict the steps up to confirming the selection. In flowchart 30, selection confirmation is the process 31 of tapping the confirmation button 26, and in flowchart 40, selection confirmation is the process 41 of tapping the confirmation button 93. That is, flowchart 30 depicts the steps up to process 31, and flowchart 40 depicts the steps up to process 41. As is clear from this figure, this embodiment is completed in 4 steps, while the conventional example requires 6 steps.

[0036] As described above, this embodiment displays the stool input area 21 as a matrix, allowing for intuitive selection by caregivers. Furthermore, the shape and amount of stool can be selected with a single tap, reducing input time. In addition, urine volume, other conditions, and the care recipient ID are also displayed on a single screen, allowing for an overview of all matters related to excretion care, improving overall readability. Moreover, row headers 211 are accompanied by images showing stool shape, column headers 212 by images showing stool volume, and urine selection blocks 221 by images showing urine volume. These visual aids help to eliminate skill differences among care facility staff and facilitate standardization. In this embodiment, examples of selecting elements in the stool input area 21 and urine input area 22 are shown, but it is also possible to record that there was no defecation or urination by not selecting any elements.

[0037] <Second Embodiment> In the first embodiment, when the confirmation button 26 is tapped, the data is registered in a table, and the contents of that table can be checked later. In the second embodiment, the data is temporarily stored in a predetermined folder on the terminal, and then the caregiver is shown whether the selection is correct or not. Figure 6 shows a GUI for confirming the registered contents, which is provided for this confirmation. The confirmation GUI 50 is displayed when a predetermined command is executed and the screen changes when the confirmation button 26 is tapped, with the selection item column 51 on the left and the character display column 52 on the right. The selection item column 51 displays the care recipient's name 511, defecation information 512, urination information 513, fecal incontinence / urinary incontinence information 514, and abnormal stool / abnormal urine information 515 in an orderly fashion, and correspondingly the character display column 52 displays characters 521 in an orderly fashion.

[0038] The defecation information displays characters corresponding to the stool shape and volume selected in the stool input area of ​​Figure 4, and the urination information displays characters corresponding to the urine volume selected in the urine input area of ​​Figure 4. Next to the characters displayed in the defecation and urination information, the corresponding image 522 is displayed together to further enhance visibility. The character 521 is displayed in a transparent frame field by reading temporarily stored character data from a designated folder on the terminal. This eliminates discrepancies between the input GUI 20 and the confirmation GUI 50. The image 522 is displayed in a separate field from the character 521, and the image corresponding to the character displayed in the character 521 field is read from a designated folder on the terminal by a predetermined command.

[0039] The characters 521 displayed here correspond to the stool shape, stool volume, urine volume, leakage / abnormality, and care recipient ID selected in Figure 4. The character for stool shape is the same as the string "Normal stool" displayed in the column header, and the character for stool volume is the same as the string "One banana" displayed in the row header. The characters for urine volume and other items are also the same as the strings displayed in the selected selection block. This allows caregivers to confirm whether their selected stool shape, stool volume, urine volume, leakage / abnormality, and care recipient ID are correct in a different format. While the input GUI 20 also allows for confirmation of whether the selection is correct, after caring for many care recipients in a day, the caregiver's eyes may become accustomed to the format, and they may fail to notice a selection error. Therefore, by allowing confirmation in a different format from Figure 4, as shown in Figure 6, the caregiver's focus can be changed, and they may become aware of selection errors.

[0040] After the caregiver confirms that the information displayed on the confirmation GUI 50 is correct, they can tap the send button 53 (fourth element) to execute a command that registers the character data 521 and the date and time data, which were temporarily stored in a designated folder on the terminal, into a table formed in a database (not shown). While it is possible to run the web application simply by creating a table in a designated folder on the terminal and saving the data there, it is more practical to save the data in a network database considering that the data will accumulate chronologically. This database can be built on a server. Alternatively, instead of temporarily storing the data, a table identical to the database can be created on the terminal and used as a backup.

[0041] On the other hand, tapping the cancel button 54 located below the send button 53 deletes the temporarily stored character data, transitions to the initial input screen shown in Figure 3, and requires the user to restart the selection of various selection blocks from the beginning. These send button 53 and cancel button 54, along with the care recipient's name 511, defecation information 512, urination information 513, fecal / urinary incontinence information 514, abnormal stool / abnormal urine information 515, and character 521, can be created and / or placed using HTML and CSS. Commands that enable marking by tapping or cursor hovering, and registration of character data and date and time into the database can be implemented using JavaScript. These source codes, along with various images, are saved in a designated folder on the terminal during the installation of the web application and are read and executed when a display request is made.

[0042] Figure 7 is a flowchart of this embodiment. Steps up to S4 are the same as in the first embodiment. The difference from the first embodiment is from step S5 onwards, that is, from the point of transitioning to the registration screen (confirmation GUI 50) in Figure 6. This will be explained in order. When the confirmation button 26 (Figure 4) is tapped in step S4, the character data corresponding to the selected block is temporarily stored, and the user transitions to the registration screen in step S5. In step 6, the temporarily stored character data is retrieved and displayed on the registration screen as character 521. Next, if the terminal confirms that the cancel button 54 was tapped in step 7, the character data registered in the table is deleted, and the input GUI 20 in step S1 is displayed. If the send button 53 is tapped in step 8 without tapping the cancel button 54, the temporarily stored character data and the date and time displayed in field 25 are registered to the server on the network.

[0043] As explained above, this embodiment displays a confirmation GUI in addition to the input GUI, allowing caregivers to notice input errors that might otherwise be overlooked due to visual acclimatization. Furthermore, since character data and other information registered in the table in response to input are registered in a network database, reliability is improved, and a web application that can be used even in large-scale care facilities can be constructed.

[0044] <About the analysis function> The following describes the analysis function of a web application equipped with a GUI according to the first or second embodiment. As described above, in either embodiment, the excretion-related data selected and entered in the GUI is stored in a table as characters, etc., so that the data can later be retrieved using a predetermined data visualization library to create maps and graphs. Figure 8 shows a heat map as an example. The vertical axis is the care recipient ID, and the horizontal axis is time, and the number of excretions per time period is aggregated cumulatively over one month. Defecation and urination are each represented by the same series of colors, with different gradations depending on the frequency of excretion. For example, defecation is represented by a brown color, and urination by a blue color. The gradation is set so that the higher the frequency, the lower the gradation and the darker the color. In the illustrated example, the darkest color is used when there is fecal leakage or urinary leakage. However, for leakage, a different series of colors may be used instead of the same series. Such heatmaps allow caregivers to intuitively recognize the excretory patterns of each care recipient, such as when they defecate or urinate, or when they are more likely to experience fecal or urinary incontinence, making it easier to create care plans for each care recipient unit.

[0045] Figure 9 is a bar graph showing the number of bowel movements per time of day, using cumulative data for one month for each individual care recipient. The data is color-coded by type of excretion (defecation and urination, or defecation and urination). This allows for the identification of excretion patterns, such as when bowel movements or urination are most frequent, and helps determine the optimal diaper changing time for each individual care recipient.

[0046] Figure 10 is a bar graph showing the daily number of bowel movements using cumulative data for one month for each individual receiving care. In this graph, the types of excretion (defecation and urination, or defecation and urination) are color-coded. This makes it easy to see at a glance any excretion trends, such as fewer bowel movements or fewer urinations on different days, and allows for confirmation of whether there are any abnormalities in the individual receiving care.

[0047] As described above, the web application using the GUI according to the present invention can be configured to register characters, dates, and times in a table, allowing data to be read from the table and processed into heatmaps and bar graphs. This makes it easy to check excretion trends, which can be used to formulate care plans for care recipient units, determine when to change diapers for individual care recipients, and even detect abnormalities in individual care recipients. Therefore, it becomes possible to improve the quality of life for both care recipients and caregivers and to create a well-being environment.

[0048] While embodiments of the present invention have been described above, various modifications are possible based on the spirit of the invention. For example, in the above embodiments, the row and column headings of the elements arranged in a matrix represented the shape and quantity of stool, but these can be replaced with the quality and quantity of different types of excrement. For example, the row headings can be replaced with the color of urine, and the column headings with the quantity of urine. Specifically, the urine colors may be "colorless and transparent," "transparent and slightly yellow," "yellow," "turbid urine," "fluorescent," "yellowish-brown," and "brown," and the urine quantities may be "over 400ml," "300-400ml," "200-300ml," "100-200ml," and "less than 100ml." To allow caregivers to visually confirm these urine colors, images showing the actual urine colors may be displayed alongside the above text. In addition, the urine quantity may also be displayed along with the text by adding images indicating urine volume levels, such as the urine selection block 221 shown in Figures 3 and 4.

[0049] In the case of care recipients who have a urinary catheter, the color of the urine can be checked from the urine collection bag or catheter, and the amount of urine collected in the bag can be easily measured. However, if the color and amount of urine are to be estimated from the diffusion area of ​​the urine soaked into the diaper, further consideration is needed. In other words, it is essential to measure in advance how much urine will be collected based on the diffusion area of ​​urine for each size of diaper or incontinence pad, and to create a guideline chart.

[0050] Furthermore, in the above embodiment, the urine volume level was represented by the colored part of the image, but it may also be represented by hatching or smudging instead of color, or by changing the hue, tone, or gradation of the background color. Furthermore, in the above embodiment, by selecting elements arranged in a matrix, the selected element, the row header in the same row as the element, the column header in the same column as the element, all elements between the element and the row header, and all elements between the element and the column header were marked. However, visibility can also be provided by marking at least a part of the row header and the column header (for example, the outer frame).

[0051] Furthermore, while HTML, CSS, and JavaScript were used as examples of computer languages ​​for constructing the GUI in the above embodiment, it goes without saying that other computer languages ​​may also be used.

[0052] Furthermore, in the above embodiment, the care recipient IDs belonging to the unit were displayed in a list, but it is also possible to register master data of care recipient IDs in a database and select a care recipient ID from a combo box or list box.

[0053] Furthermore, in the second embodiment described above, the temporarily stored character data is deleted when the cancel button 54 is selected, and the system transitions to the initial input screen shown in Figure 3. However, the system may also be configured to leave the temporarily stored character data as is, transition to the screen shown in Figure 4, and allow the caregiver to correct the selection of each element. [Explanation of Symbols]

[0054] 10 Electronic Device Environment 110 Network 111 Server 1110 System Bus 1111 processor 1112 ROM 1113 RAM 1114 Storage device 1115 Communication equipment 121 Tablet devices 1210 System Bus 1211 CPU 1212 ROM 1213 RAM 1214 Storage device 1216 displays 1217 Communication equipment 122 Smartphones 123 PCs within the facility 124, 125 Off-site PC 20 Input GUI 21 Flight Input Area 211 row headings 212 Column Headings 213 Flight Selection Block 214 Checkmark image 22 Urine input area 221 Urine selection block 23. Leak / Anomaly Input Area 231 Leak / Anomaly Selection Block 24. Care Recipient ID Input Area 241 ID Selection Block 25 Fields 26 Confirm button Flowcharts for 30, 40, and 60 31, 41 Processing 50 Confirmation GUI 51 Selection Item Column 511 Caregiver's name 512 Bowel movement information 513 Urination information 514 Information on fecal incontinence and urinary incontinence 515 Abnormal stool / abnormal urine information 52-character display column 521 characters 522 images 53 Send button 54 Cancel button 91 Stool volume input field 911 Stool volume input button 92. Input field for characteristics 921 Characteristic Input Button 93 Confirm button 94 Cancel button S1-S9 Steps

Claims

1. It is displayed on the terminal's screen and comprises a plurality of first elements arranged in a matrix, one second element, row headers arranged for each row of the plurality of first elements, and column headers arranged for each column of the plurality of first elements. Either the row header or the column header is accompanied by an image showing the quantity of the excrement, and the other is accompanied by an image showing the quality of the excrement. In response to the selection of one of the plurality of first elements, at least a portion of the row headers in the same row as the element and at least a portion of the column headers in the same column as the element are marked. Each of the row headers and column headers mentioned above is assigned a different character. A graphical user interface for inputting vital sign data, characterized in that, upon selection of the second element, a command is executed to retrieve the characters assigned to the row header and column header of the selected element, and to register them in a table along with the date and time.

2. The graphical user interface for inputting vital sign data according to claim 1, characterized in that the excrement is feces, and the image showing the quality of the excrement is the shape of the feces.

3. The graphical user interface for inputting vital sign data according to claim 1, characterized in that the excrement is urine, and the image showing the quality of the excrement is the color of the urine.

4. It also includes multiple third elements, Each of the aforementioned third elements is accompanied by a string of characters and an image indicating a different urine volume level, and is also assigned a different character. A graphical user interface for inputting vital sign data according to claim 2, characterized in that, upon selection of the second element, a command is executed to acquire the character assigned to the third element and register it in the table.

5. Instead of executing a command to acquire the character and register it in the table along with the date and time as a result of the selection of the second element, a command is executed to temporarily store the character and display a confirmation screen. The aforementioned confirmation screen displays the temporarily stored character. The aforementioned confirmation screen further comprises a fourth element, A graphical user interface for inputting vital sign data according to any one of claims 1 to 4, characterized in that the temporarily stored character is registered in the table along with the date and time by the selection of the fourth element.

6. The characters and dates and times registered in the table are visualized in a heatmap or bar graph that displays the number of excretions over time using a predetermined data visualization library. The graphical user interface for inputting vital sign data according to any one of claims 1 to 4, characterized in that the heatmap or bar graph is used to analyze the excretion tendencies of a care recipient unit or an individual care recipient.

7. The characters and dates and times registered in the table are visualized in a heatmap or bar graph that displays the number of excretions over time using a predetermined data visualization library. The graphical user interface for inputting vital sign data according to claim 5, characterized in that the heatmap or bar graph is used to analyze the excretion tendencies of a care recipient unit or an individual care recipient.

Images