Information processing device, and processing method, program thereof, system and processing method thereof

The system automates the recording of headache symptoms and provides personalized countermeasures, addressing the challenge of timely documentation and management of sudden headaches.

JP2024166003APending Publication Date: 2024-11-28CANON MARKETING JAPAN INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023110525
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-07-05
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

Existing systems struggle to accurately record and manage headaches and other physical discomforts due to their sudden onset and the difficulty in remembering to document symptoms promptly.

Method used

A system comprising an information processing device and a server that uses cameras and a recording application to automatically log initial headache data and prompts users to input detailed information, with AI-assisted analysis to provide personalized countermeasures.

Benefits of technology

Enhances the management of headache records by reducing the burden of immediate documentation and providing timely, appropriate responses to headaches through automated and guided recording processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166003000001_ABST
    Figure 2024166003000001_ABST
Patent Text Reader

Abstract

To provide a mechanism capable of further appropriately managing a record of disorders such as a headache.SOLUTION: An information processing system includes: receiving a record relating to a user's disorder by an instruction to a first instruction receiving part or a second instruction receiving part; executing notification of prompting the user to record the disorder; and differentiating content of the notification by the notification means based on presence / absence of the record by receiving the instruction to the first instruction reception part, and an input state of detailed information relating to the disorder to be received when the instruction to the second instruction reception part is received.SELECTED DRAWING: Figure 11
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device for managing physical condition, a processing method and program thereof, and a system and a processing method thereof. [Background technology]

[0002] There are many people who suffer from chronic headaches (headache sufferers), and as it is a common symptom, many of those who suffer from headaches end up taking painkillers as a countermeasure.

[0003] In addition, because there are so many ways to improve headaches, it can be difficult to know which one is best suited for you and to choose the best option.

[0004] As a mechanism for alleviating pain, there are smartphone applications that allow users to record their physical condition. Patent Document 1 discloses a technology that "presents to the user information that contributes to the alleviation of symptoms such as stiff shoulders, back pain, and headaches, and to the reduction of the user's stress." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-40513 A DISCLOSURE OF THEINVENTION [Problem to be solved by the invention]

[0006] However, for example, pain such as headaches can occur suddenly without warning, making it difficult to record symptoms at the time they occur. Even if you try to record symptoms after the fact, you may forget to record them in the first place, or forget what symptoms you had after a long time has passed.

[0007] Therefore, an object of the present invention is to provide a mechanism for more appropriately managing records of ailments such as headaches. [Means for solving the problem]

[0008] A receiving means for receiving a record of a user's illness by issuing an instruction to the first instruction receiving unit or the second instruction receiving unit; A notification means for notifying the user to record information about the illness; A control means for changing the content of the notification by the notification means based on the presence or absence of a record of the receipt of an instruction to the first instruction receiving unit and an input status of detailed information regarding the malfunction received when an instruction to the second instruction receiving unit is received; The present invention is characterized by comprising: Effect of the Invention

[0009] According to the present invention, it is possible to more appropriately manage records of ailments such as headaches. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration in the present embodiment. [Diagram 2] 1 is a block diagram showing an example of the hardware configuration of an information processing device 100 and a server 102 in the present embodiment. [Diagram 3] 13 is a flowchart showing an example of registering pain information using a help button in this embodiment. [Figure 4] 13 is a flowchart showing an example of registering pain information using a record button in this embodiment. [Diagram 5] 2 is a diagram showing an example of management information managed by a server 102 in the present embodiment. FIG. [Figure 6] FIG. 2 is a diagram showing an example of a top screen displayed on information processing device 100 in this embodiment. [Figure 7] FIG. 11 is a diagram showing an example of a screen displayed on information processing device 100 when a help button is pressed in this embodiment. [Figure 8] FIG. 2 is a diagram showing an example of a recording instruction screen displayed on the information processing device 100 in this embodiment. [Figure 9] FIG. 2 is a diagram showing an example of a pain information input screen displayed on the information processing device 100 in this embodiment. [Figure 10] 11 is an example of a flowchart showing an overview of a process related to a reminder notification in the present embodiment. [Figure 11] 11A to 11C are diagrams illustrating an example of a reminder notification, a solution screen, and a message after input is completed in the present embodiment. [Figure 12] FIG. 13 is a diagram showing an example of an effect button in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The present embodiment will be described in detail below with reference to the drawings. Fig. 1 is a diagram showing an example of the configuration of a headache management system in the present embodiment.

[0012] Although this embodiment is a headache management system that includes recording of headaches, it may also be a system that records and manages cases of physical ailments other than headaches (e.g., lower back pain, neuralgia, dizziness, tinnitus, fatigue, etc.).

[0013] 1, the headache management system is configured by a server 102 and an information processing device 100 (specific examples of information processing devices include personal computer A, personal computer B, and mobile terminals such as smartphones and tablet terminals) that are communicatively connected via a network 101. The following description will be given taking a mobile terminal as a specific example of an information processing device.

[0014] As shown in Fig. 1, the mobile terminal may be a wearable terminal, or the mobile terminal and the wearable terminal may be connected to each other so that they can communicate with each other. In this case, if the wearable terminal has a display screen, it can be controlled in the same way as the mobile terminal. The wearable terminal may also function as a terminal that acquires physical information such as blood pressure and heart rate and inputs the acquired physical information to a mobile terminal such as a smartphone.

[0015] The information processing device 100 as a mobile terminal is a mobile terminal (tablet, smartphone, etc.) equipped with a camera function and a touch panel function (operation unit), and has a recording application installed therein that can record ailments such as headaches.

[0016] In this embodiment, a headache will be used as a specific example of a disorder.

[0017] The information processing device 100 will be described as having two cameras. The two cameras are an in-camera (a first camera such as a front camera) provided on the liquid crystal display side, and an out-camera (a second camera such as a rear camera) provided on the opposite side to the liquid crystal display (the rear surface of the information processing device 100). Note that, although the present embodiment will be described as a built-in camera, a camera connected via USB may also be used.

[0018] In response to an operation from the user on the information processing device 100 (for example, in response to an instruction to input / send logged-in user information), the information processing device 100 logs in to the server 102, obtains information about the user, and displays it using a headache record application of the information processing device 100. Then, the information input on the information processing device 100 is transmitted to the server 102, and the results of analysis in accordance with the input are displayed on the information processing device 100.

[0019] Here, it is assumed that the information processing device 100 communicates with the server 102 via a network 101 (wireless LAN or a public communication line and communication method (4G, 5G, etc.)).

[0020] The server 102 is a device that holds records of information for managing headaches and user information. The server 102 also holds weather information used for headache management in cooperation with an external system, and an AI held by the server 102 may analyze the information inputted to the information processing device 100 and output information suited to the user. Note that, without using AI, the inputted information may be quantified, and information suited to the user may be determined from the tendency of the numerical values ​​and outputted.

[0021] It should be noted that the server 102 is a server in a cloud environment, but when implemented within a company, it may be installed on a company network.

[0022] In this embodiment, a configuration is described as a system in which the information processing device 100 communicates with the server 102, but the configuration may also be such that the information processing device 100 (specifically, a recording application installed on a smartphone, etc.) executes the processing to be performed by the server 102 without communicating with the server 102.

[0023] Next, the hardware configuration of a mobile terminal serving as the information processing device 100 shown in FIG. 1 will be described with reference to FIG.

[0024] FIG. 2A is a block diagram showing a hardware configuration of a mobile terminal serving as the information processing device 100 shown in FIG.

[0025] 2, a CPU 201 performs overall control of each device and controller connected to a system bus 204. In addition, a ROM 202 or an external memory 211 stores a BIOS (Basic Input / Output System) which is a control program for the CPU 201, an operating system program (hereinafter, OS), and various programs (to be described later) required to realize the functions executed by each server or each PC.

[0026] The RAM 203 functions as a main memory, a work area, etc., of the CPU 201. The CPU 201 loads programs and the like required for executing processing from the ROM 202 or the external memory 211 into the RAM 203, and executes the loaded programs to realize various operations.

[0027] Furthermore, the display controller 205 controls input from the touch panel 209 and display (output) to the touch panel 209. Although not shown, the device may also include a controller that accepts input from hard keys provided on the device.

[0028] The memory controller 207 controls access to an external memory 211 such as a hard disk (HD) that stores boot programs, various applications, font data, user files, edited files, various data, etc., and an SD card connected to a card slot via an adapter.

[0029] The communication I / F controller 208 connects to and communicates with external devices via a network (such as the LAN / WAN shown in FIG. 1) and executes communication control processing on the network. For example, communication using TCP / IP is possible.

[0030] The first camera (front camera) 212 and the second camera (rear camera) 213 are cameras built into the mobile terminal, and are controlled by the camera controller 206. In addition, the camera to be used can be controlled (switched) by a command from an application on the mobile terminal. That is, it is possible to switch between the in-camera and the out-camera.

[0031] Various programs for implementing the present invention, which will be described later, are recorded in the external memory 211, and are executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information used when executing the above programs are also stored in the external memory 211 (they may be appropriately obtained from the server 102 and stored in the RAM).

[0032] FIG. 2B is a block diagram showing the hardware configuration of the server 102 shown in FIG.

[0033] The CPU 221 comprehensively controls each device and controller connected to a system bus 224 .

[0034] The ROM 222 or the external memory 231 (storage) stores a BIOS (Basic Input / Output System) which is a control program of the CPU 221, an operating system program (hereinafter, OS), and various programs necessary to realize the function of executing the server. The external memory 231 also includes a database. The RAM 223 functions as the main memory, work area, etc. of the CPU 221.

[0035] The CPU 221 loads programs and the like required for executing processes into the RAM 223, and executes the programs to realize various operations.

[0036] Furthermore, an input controller (input C) 225 controls input from a keyboard 229 or a pointing device such as a mouse (not shown).

[0037] A video controller (VC) 226 controls display on a display device such as a display 230. The display 230 is a liquid crystal display or the like, and is used by an administrator as necessary.

[0038] The memory controller (MC) 227 controls access to an external memory 231, such as a hard disk (HD), a floppy disk (registered trademark FD), or a card-type memory connected to a PCMCIA card slot via an adapter, which stores a boot program, browser software, various applications, font data, user files, edited files, various data, etc.

[0039] A communication I / F controller (communication I / FC) 228 connects to and communicates with external devices via a network, and executes communication control processing on the network. For example, Internet communication using TCP / IP is possible.

[0040] The CPU 221 enables display on the display 230 by, for example, executing a process of expanding (rasterizing) an outline font in a display information area in the RAM 223. The CPU 221 also enables a user to give instructions using a mouse cursor (not shown) or the like on the display 230.

[0041] Next, the flow of processing when registering pain information by pressing the help button in the headache record in this embodiment will be described with reference to Fig. 3. Note that each step is executed by the CPU of the information processing device 100 or the server 102. When an instruction to execute a headache record application is given in the information processing device 100, the processing in Fig. 3 is started.

[0042] In step S301, the CPU 201 of the information processing device 100 accepts input of user information for managing headaches using the headache record application. This is to be input once when the headache record application is launched for the first time, but can be changed from the settings of the headache record application even after input. Specifically, a user name, password, email address, an image representing the user (a normal display image and an image to be displayed when there is a headache), etc. are registered.

[0043] In step S302, the server 102 receives the user information inputted in the information processing device 100 and registers it in the external memory 231. The user information may also be managed on the headache record application side. An example of user information registered in the external memory 231 is the user management information 501 in FIG. 5.

[0044] Here, the user management information 501 in Fig. 5 will be described. As the user management information, a user name, a password, an email address, and the like, which are input and transmitted by the information processing device 100, are stored. In addition, basic physical information is stored as physical and lifestyle information, and an image showing the user (an image for normal display is called user image 1, and an image displayed when the user has a headache is called user image 2) is stored and managed. The information to be managed is not limited to the items shown in the user management information 501.

[0045] In step S303, the CPU 201 of the information processing device 100 receives an instruction to display the top screen of the headache record application in the information processing device 100 in response to a user operation, etc. In response to the reception of the instruction to display the top screen, communication is performed with the server 102. When the headache record application is launched for the first time, the top screen is displayed as soon as the user information input in step S301 is completed, and when the headache record application is launched for the second time or later, the process equivalent to an instruction to display the top screen is that the headache record application is launched and login is completed.

[0046] In step S304, the server 102 acquires the record information (pain information recorded due to headache) of the logged-in user managed in the external memory 231, and transmits it to the information processing device 100. An example of the record information (pain information recorded due to headache) stored in the external memory 231 is pain information 511 in FIG. 5.

[0047] Here, a description will be given of the pain information 511 in Fig. 5. Corresponding to the users managed in the user management information 501, various information is managed in a database or the like.

[0048] The pain information stored includes headache records inputted into the information processing device 100 in the process shown in the flow chart described below, and the results of analysis of the records (e.g., countermeasures). Information indicating the date and time when the headache occurred (or the date and time when it was recorded), the intensity of the headache, the type of pain, the part of the body where the pain occurred, and whether medication was taken is stored.

[0049] Examples of each type of information include date and time, pain intensity on a scale of 10 (for example, a number from 1 (weak) to 10 (strong)), and type of pain such as "pain when moving," "pain when lowering head," "throbbing pain," "tightening pain," and "stabbing pain." Also, areas of the body include "temporal region (temples, above and sides of ears)," "forehead (forehead, around eyebrows)," "occipital region, occipital region (from base of neck to neck and shoulders)," "behind the eyes," and "around the temporomandibular joint" (including information on left and right, if applicable). Medication includes "not taken," "taken (over-the-counter medication)," and "taken (prescription medication)."

[0050] The weather information is stored as "weather," "barometric pressure," "temperature," and other information (such as values ​​at the time of headache onset and trends of change) obtained from services that provide weather information. The location of the headache is stored as location information obtained from the mobile device's GPS information or map designation. Note that instead of latitude and longitude location information, names such as "workplace" or "home" may be stored.

[0051] The presented remedy stores the presented headache remedy suitable for the user when the help button is pressed. The effectiveness stores "effective" or "ineffective" according to the input of information indicating that the remedy was effective after the help button is pressed. The help registration stores a flag indicating that the help button was pressed and registration was performed.

[0052] In addition to the information shown as pain information 511 in FIG. 5, menstrual information (information indicating premenstrual / menstrual (date) / not menstruating), stress level, and warning signs (eye irritation, stiff shoulders), etc. may also be stored.

[0053] In step S305, the CPU 201 of the information processing device 100 judges whether the record information received from the server 102 contains any records in which detailed information has not been entered (hereinafter, referred to as "unentered records"). Specifically, it judges whether there are any records in which help registration is "present" (i.e., records made by pressing the help button) and there are any items that have not been entered. Note that the server 102 may be configured to transmit only information on unentered records to the information processing device 100. In that case, the judgment may be made based on whether unentered record information has been received. Alternatively, the server 102 may judge whether there is an unentered record and transmit a message to the information processing device 100 that there is an unentered record.

[0054] If it is determined that there is an uninputted record, the process proceeds to step S307, and if it is determined that there is no uninputted record, the process proceeds to step S306.

[0055] In step S306, the CPU 201 of the information processing device 100 displays a normal top screen 601 (FIG. 6) on the display 230 (note that all display destinations in the steps described below are assumed to be the display 230). The normal top screen 601 displays an icon image of the user and a button for recording in the display area 602. In this embodiment, a help button 603 is provided to facilitate recording of sudden pain such as headache. Also, a record button 604 is provided to record the headache at any timing. The help button 603 is a first instruction receiving section for presenting a method of dealing with the pain, and is also a first instruction receiving section for automatic recording. The record button 604 (second instruction receiving section) can be pressed even before recording with the help button 603, and the contents of the headache can be recorded as appropriate. That is, it controls the display of the first instruction receiving section and the second instruction receiving section.

[0056] In step S307, a no-entry notification top screen 611 (FIG. 6) is displayed to indicate that there is a no-entry record. The no-entry notification top screen 611 displays an icon image of the user and also displays a button for recording in the display area 612. It also has a record button 614 (second instruction receiving unit) for automatically recording (simple recording so as not to forget) immediately on the spot with the help button, and then recording detailed information later. If there is a no-entry record, a notification mark 615 (also displays the number of no-entry records) for indicating a no-entry record (simple recording by the help button) is displayed on the record button 614. The help button 613 (first instruction receiving unit) is controlled in the same way as the normal top screen 601. That is, the process of displaying the notification mark 615 (also displays the number of no-entry records) for indicating a no-entry record (simple recording by the help button) is a process of notifying that the first information recorded by pressing the help button (information indicating the date or date and time related to the instruction as a record indicating that there was an illness) is stored. This can eliminate the situation in which it was difficult to manage headaches by encouraging no-entry records.

[0057] In step S308, CPU 201 of information processing device 100 determines whether or not help button 603 or help button 613 has been pressed. If the help button (first instruction unit) has been pressed, the process proceeds to step S309, and if record button 604 or record button 614 has been pressed, the process proceeds to Fig. 4. The process in Fig. 4 will be described later.

[0058] In step S309, the CPU 201 of the information processing device 100 displays the pain input screen 701 and acquires the pain information input by the user. When the help button is pressed, the date and time (time) when the help button was pressed are acquired as a record of the occurrence of a headache, along with a notice that the record was made by pressing the help button. Note that in addition to the date and time (time), the location and the "intensity of pain" and "type of pain" input by the user may also be acquired. The acquired information is then recorded in the headache management application.

[0059] Here, the operation when the help button is pressed will be described with reference to Fig. 7. A pain input screen 701 is an example of a screen indicating that the help button has been pressed and the date and time (time) and location have been recorded.

[0060] The recorded message 702 displays information indicating that recording has been made and the recorded contents (date, time, location). In this embodiment, it is desirable to store the date, time, and location, but since there are cases where location information cannot be obtained, at least the date and time information is stored and displayed. In other words, this is a process for controlling the storage of first information including at least the date or time related to the instruction as a record indicating that there was an illness. In this embodiment, the date and time of the headache record is the date and time acquired by the information processing device 100, but it may also be configured to request the server 102 and use the date and time of the server 102.

[0061] At this time, communication may be performed with server 102, and the date, time, and location may be stored in server 102, and in a step described below, the "date, time, and location," "intensity of pain," and "type of pain" may be transmitted as a record of the occurrence of a headache.

[0062] In the pain input screen 701, the pain intensity 703 and the type of pain 704 are input as information for presenting a method of dealing with the pain. In other words, this is a process for accepting input of information related to illness. By pressing the help button, headaches can be automatically and easily recorded, reducing the burden on the user of recording headaches. In particular, when a headache occurs, making detailed records due to the illness is a heavy burden, making it difficult to manage the headache, but by being able to simply record the headache with the help button as in this embodiment, it is possible to continue managing the headache (including recording).

[0063] Incidentally, when the help button 603 or the help button 613 is pressed, recording is performed automatically. However, it goes without saying that a confirmation screen may be displayed before automatic recording so that the user can confirm before recording.

[0064] Also, although the system is configured to accept input of pain intensity and type of pain, when recording by pressing the help button, it is expected that the pain (severe discomfort) is so severe that details cannot be recorded, so the pain intensity may be set in advance as a predetermined value (for example, 7 on a 10-point scale) and that value may be registered automatically. Also, the system may be configured to record the type of pain without accepting input.

[0065] In step S310, the CPU 201 of the information processing device 100 transmits the pain information acquired in step S309 to the server 102. That is, this is a process of controlling the storage of the first information including at least the date or date and time related to the instruction. As described above, information on the time and place related to the headache occurrence may be transmitted in this process.

[0066] Since the type of pain 704 is a question for distinguishing between "migraine" and "tension-type headache," it is desirable to have the user input it (a configuration in which options are presented and a selection is accepted) but if the server 102 can identify "migraine" from the user's past headache records, the date and time and location of the current headache, weather information, and basic information of the user (identified using analysis by AI), then it may be configured not to require input. Also, if the intensity of pain can be determined based on the user's tendency value, then it is possible to configure the information processing device 100 so that the user does not input it.

[0067] In addition, when recording by pressing the help button, it is assumed that the pain (severe discomfort) is so severe that it is not possible to record the details, so the intensity of the pain can be set in advance to a predetermined value (for example, 7 on a scale of 10) and this value can be automatically registered.

[0068] Also, it may be configured so that the intensity and type of pain can be recorded without receiving input. In this case, by recording that the recording was made by pressing the help button, it is possible to understand that the situation was such that detailed recording was not possible, rather than that the details were simply forgotten. In that case, it is desirable to display the contents of the countermeasure display screen 711 together with the recording message 702.

[0069] In step S311, the CPU 221 of the server 102 receives the information transmitted from the information processing device 100 and registers it in the pain information 511. When the help button is pressed, at least the date and time of headache onset is registered, and a flag indicating help registration (Yes) is stored. As described above, when the intensity and type of pain are identified by AI, they may be automatically provisionally registered. In this case, the information is to be corrected when the record button 614 is pressed.

[0070] In step S312, the CPU 221 of the server 102 determines a countermeasure based on the registered pain information 511, and acquires the determined countermeasure information. The countermeasure is determined based on the intensity and type of pain. Although not shown in detail, a table is held in which a countermeasure is determined according to the intensity of pain for each type of pain, and the countermeasure is determined based on this table.

[0071] Examples of measures include "pressing the pain-relieving acupoint (Hegu)" and "taking Chinese herbal medicine such as Goshuyuto", and "explanation" for each measure is also managed by the server 102. If there is a measure that the user finds effective, that measure may be presented. Furthermore, if that measure does not work this time, another measure may be presented based on the pain information.

[0072] Also, physical information (blood pressure, heart rate, etc.) acquired from the wearable device may be used to determine a countermeasure.

[0073] In step S313, the CPU 201 of the information processing device 100 acquires the countermeasure information received from the server .

[0074] In step S314, the CPU 201 of the information processing device 100 displays the acquired remedy information in the headache record application. An example of the display is the remedy display screen 711 in FIG. 7. The remedy display screen 711 displays the remedy and its explanation (including images). In this way, by pressing the help button, a headache can be recorded and the remedy that is appropriate at that time is displayed, making it easier to record headaches and to self-control headaches, and eliminating situations in which headaches were difficult to manage. By providing simple records and the remedy at the appropriate time, it becomes possible for the user to continue managing their headaches, which was previously difficult.

[0075] In this embodiment, a configuration has been described in which a notification is given so that the user can recognize that there is a record that has not yet been entered when the top screen is displayed, but the timing of the notification is not limited to this. For example, a push notification may be sent from the headache record application when a predetermined time has elapsed since the user pressed the help button to start recording, or at a predetermined time (e.g., 8:00 p.m.) every day. By sending a push notification in this way, it is possible to further reduce forgetting to record, or to record symptoms before they are forgotten.

[0076] Next, the flow of processing when registering pain information by pressing the record button in the headache record in this embodiment will be described with reference to Fig. 4. Note that each step is assumed to be executed by the CPU of the information processing device 100 or the server 102.

[0077] In step S401, CPU 201 of information processing device 100 determines whether there is an uninputted record. If there is an uninputted record (i.e., record button 614 on uninputted notification top screen 611 in FIG. 6 is pressed), the process proceeds to step S402, and if there is no uninputted record (i.e., record button 604 on uninputted notification top screen 611 in FIG. 6 is pressed), the process proceeds to step S403.

[0078] In step S402, the CPU 201 of the information processing device 100 displays the record selection screen 801 of FIG. 8. Specifically, in addition to the normal record button 802, a no-input record button 803 is displayed to record an additional no-input record (a simple record state record by pressing the help button). That is, this is a process for selecting whether to input detailed information (second information) regarding the record of the malfunction related to the first information by pressing the no-input record button 803, or to input a record (new input) indicating that a new malfunction has occurred by pressing the normal record button 802. As described above, the first information is information indicating the date or date and time related to the instruction to record the malfunction by pressing the help button, and the second information is detailed information (information related to items other than the first information) regarding the record of the malfunction related to the first information.

[0079] In step S403, since there is no uninputted record, the CPU 201 of the information processing device 100 displays the normal record button 802. In this case, the uninputted record button 803 may be displayed in an unselectable state.

[0080] In step S404, the CPU 201 of the information processing device 100 determines whether the NO INPUT RECORD button or the RECORD button has been pressed on the record selection screen 801. If the NO INPUT RECORD button 803 has been pressed, the process proceeds to step S405, and if the NORMAL RECORD button 802 has been pressed, the process proceeds to step S406.

[0081] In step S405, the CPU 201 of the information processing device 100 displays a calendar screen 811 showing uninputted recording days. The calendar screen 811 displays a calendar for each month in a display area 812, and also displays a recording mark 813 on the recording day and a help recording mark 815 on the HELP recording day based on the recording information acquired in step S304.

[0082] In step S406, the CPU 201 of the information processing device 100 displays a pain information input screen 901 shown in Fig. 9. The pain information input screen 901 is a screen for inputting details of information related to pain. For example, the date and time when the headache started / ended, the type of pain, the level of pain, medication information, information 902 regarding the effectiveness of measures to deal with the pain, other information regarding measures to treat the pain, and other information that may be triggers of the pain can be input. In addition, the screen is provided with a NO HEADACHE button 903 for leaving a record that there was no headache, and a SAVE button 904.

[0083] In step S407, the CPU 201 of the information processing device 100 accepts the selection of an uninputted recording date from the calendar screen 811. Specifically, an instruction to select the help recording mark 815 is accepted.

[0084] In step S408, the CPU 221 of the server 102 receives the date information from the information processing device 100, and the server 102 acquires the record information for the selected day from the pain information 511. The acquired record information (recorded information) is transmitted to the information processing device 100.

[0085] In step S409, the CPU 201 of the information processing device 100 acquires the recorded information received from the server 102. Note that if all the recorded information has been acquired in step S303, reception from the server 102 is omitted.

[0086] In step S410, the CPU 201 of the information processing device 100 displays a pain information input screen 901 reflecting the acquired pain information. In addition, the pain information input screen 901 reflecting the pain information accepts the selection of the degree of pain after trying the countermeasure from information 902 relating to the effectiveness of the countermeasure, in order to register whether or not the countermeasure presented in step S314 was effective. That is, this is a process of controlling the storage of information relating to the effectiveness of the countermeasure.

[0087] In addition, rather than allowing the user to select the degree of pain, a check box or a value indicating the level of effectiveness may be registered.

[0088] Also, a screen may be displayed (not shown) for inputting other additional information that needs to be recorded, such as menstrual information, stress level, warning signs, etc. (i.e., second information related to the illness record related to the first information).

[0089] In step S411, the CPU 201 of the information processing device 100 accepts input of pain information according to the displayed screen, and transmits it to the server 102. That is, steps S410 and S411 are processes for controlling the storage of second information on the illness record related to the first information.

[0090] In step S412, CPU 201 of information processing device 100 determines whether or not pressing of save button 904 has been accepted. If accepted, the process proceeds to step S413, and if not, the process proceeds to step S414.

[0091] In step S413, when the CPU 221 of the server 102 accepts pressing of the save button 904, it stores the content inputted into the pain information input screen 901 as having been saved.

[0092] In step S414, the CPU 221 of the server 102 stores the contents input on the pain information input screen 901. For example, the input contents are transmitted to the server when the app is terminated. Note that the server 102 may constantly monitor each item on the pain information input screen 901, so that the input contents are constantly transmitted to the server 102. Alternatively, the input contents may be stored in the ROM 202 or the external memory 211 of the information processing device 100 without communicating with the server 102.

[0093] Next, a process related to a reminder notification in this embodiment will be described with reference to Fig. 10. Note that each step is assumed to be executed by the CPU of the information processing device 100 or the server 102.

[0094] The time to send the reminder is set in advance, and when the set time arrives, the process of Fig. 10 starts. In order to reduce forgetting to record on the pain information input screen 901, or to record the content before it is forgotten, a setting is accepted to send a reminder at a specified time. The reminder may be sent by any method, such as by displaying it on the startup screen or banner of the mobile terminal, or by voice.

[0095] In step S1001, the CPU 221 of the server 102 determines whether the current time is the set time or not. If it is the set time, the process proceeds to step S1002, and if not, the process waits until the set time arrives.

[0096] In step S1002, the CPU 221 of the server 102 determines whether there is a record of pressing the help button 603. If there is a help record, the process proceeds to step S1003, and if not, the process proceeds to step S1004. Specifically, when the help button 603 is pressed, at least the user information, date and time, and whether or not help has been registered are stored in the pain information 511 in step S311, and the help registration status is checked to determine whether there is a record of pressing the help button 603.

[0097] In step S1003, the CPU 221 of the server 102 stores the information that help has been recorded. Information relating to this process is used in controlling the notification content in step S1008.

[0098] In step S1004, the CPU 221 of the server 102 accepts pressing of the save button in step S412, and in step S413 determines whether the contents of the pain information input screen 901 have been saved. If saved, the process proceeds to step S1005, and if not, the process proceeds to step S1006. Specifically, if pain information 511 has been stored on the same day as the day the reminder was notified and the contents have been saved, the process proceeds to step S1005.

[0099] In step S1005, the CPU 221 of the server 102 stores the information as having been saved. Information relating to this process is used in controlling the notification content in step S1008.

[0100] In step S1006, the CPU 221 of the server 102 determines whether or not the pain information 511 recorded in step S414 on the pain information input screen 901 is stored. If there is a record, the process proceeds to step S1007, and if not, the process proceeds to step S1008.

[0101] Specifically, if it is determined in step S1004 that the pain information has not been saved, it is determined in step S414 whether or not there is a record of the pain information 511 entered in each item on the pain information input screen 901. The user information and date and time stored in the pain information 511 are compared with the date and time when the reminder was notified to determine whether or not there is a record of the pain information 511 for that day. If pain information 511 has been recorded, proceed to step S1007.

[0102] In step S1007, CPU 221 of server 102 stores the information indicating that detailed recording is performed. Information related to this process is used in controlling the notification content in step S1008.

[0103] In step S1008, CPU 221 of server 102 controls the contents of the reminder notification by referring to each of the conditions of whether or not there is a help record in step S1003, whether or not it has been saved in step S1005, and whether or not there is a detailed record in step S1007.

[0104] Specifically, the content of the reminder notification will be changed depending on whether or not there is a help record. The following patterns are possible for each condition, and the content of the reminder notification will be changed depending on each pattern.

[0105] (Pattern A) Help record available Detailed record available Saved

[0106] (Pattern B) Help record available Detailed record available Uninsured

[0107] (Pattern C) Help record included Detailed record not included

[0108] (Pattern D) No help record, detailed record, saved

[0109] (Pattern E) No help record, detailed record, uninsured

[0110] (Pattern F) No help records No detailed records For example, in the case of (Pattern A), the message may be consolation for the pain being so severe that the help function was used (so that the user would want to know immediately how to deal with it), and a notification may be given regarding confirmation as to whether to edit the pain information input screen 901. In the case of (Pattern B), the message may be consolation for the pain being so severe that the help function was used (so that the user would want to know immediately how to deal with it), and a notification may be given urging the user to make an addition to the pain information input screen 901. In the case of (Pattern C), the message may be consolation for the pain being so severe that the help function was used (so that the user would want to know immediately how to deal with it), and a notification may be given urging the user to make a record in the pain information input screen 901.

[0111] In the case of (Pattern D), a message is displayed on the pain information input screen 901 praising the user for recording the headache, and a notification is displayed to confirm whether any additions or corrections are necessary. In the case of (Pattern E), a message is displayed on the pain information input screen 901 praising the user for recording the headache, and a notification is displayed encouraging the user to record in blank fields. In the case of (Pattern F), a message is displayed to confirm whether the user had a headache that day, and if a headache occurred, a notification is displayed encouraging the user to enter information on the pain information input screen 901.

[0112] The contents of the notification may be different depending on whether the input of the detailed information has been completed or not. The state in which the input is completed refers to, for example, the state in which the save button has been pressed, the state in which all items have been input, the state in which items set as required items have been input, etc. When the input of the detailed information is completed, a notification is issued praising the completion of the recording. On the other hand, when the above does not apply, a notification is issued indicating that the input is incomplete and prompting input to the pain information input screen 901.

[0113] By varying the notification content according to the conditions, the user can reconfirm whether or not he or she had a headache that day, and if he or she had a headache, can recall whether or not the pain was severe enough to press the help button. This allows the user to recall memories of when the headache occurred, and record more accurate information when recording the situation. In addition, the user can know from the reminder notification whether or not the content has been saved. In addition, by changing the notification content, it is expected that the user's motivation to record headaches will increase. Note that the message content is just an example, and the content will vary depending on the pattern, such as notifying the user if the headache has subsided or sending a caring message or encouraging them when there is a help record, and any message content that fits the pattern may be used.

[0114] In step S1009, the CPU 201 of the information processing device 100 displays the contents controlled in S1008 on the touch panel 209. FIG. 11(a) shows an example of the reminder notification. In the reminder notification, a message 1101 according to the condition in S1008 and an image 1102 of a person registered in the headache record application are displayed. For example, an image of a person that the user likes, or an image of a family member or friend, etc. can be registered. By registering an image of a person that the user likes or an image of a close person and notifying the user together with the image of that person, it is possible to make the user feel as if the person is urging him or her to record, and therefore it is expected that the user's motivation for recording about headaches will be improved. Note that the registered image is not limited to a face image of a person, and any image such as an icon image or a landscape image may be registered.

[0115] In step S1010, the CPU 201 of the information processing device 100 determines whether or not a selection for the reminder notification has been accepted. If a selection has been accepted, the process proceeds to step S1011, and if not, the process ends. The method of selecting the reminder notification includes, for example, tapping, swiping, or long pressing the reminder notification.

[0116] In step S1011, the CPU 221 of the server 102 determines whether or not there is a help record in step S1003. If there is a help record, the process proceeds to step S1012, and if not, the process proceeds to step S1015.

[0117] In step S1012, the CPU 221 of the server 102 transmits a related solution to the information processing device 100. Specifically, the CPU 221 identifies the solution displayed when the help button was pressed, that is, the solution displayed in step S314, and transmits it to the information processing device 100.

[0118] In step S1013, the CPU 201 of the information processing device 100 receives the solution transmitted in step S1012, and displays it on the touch panel 209. An example of a solution confirmation screen 1110 is shown in FIG.

[0119] The remedy confirmation screen 1110 accepts selection of post-headache pain condition 1111, selection of a "Try it" button 1112, and selection of a "record headache" button 1113.

[0120] In the selection of the post-headache pain state 1111, for example, a selection from "none", "mild", "moderate", and "severe" is accepted with respect to the pain state two hours after the onset of the headache. In addition, the countermeasure display area displays the countermeasure presented in step S314, a "tried" button 1112 for accepting a selection of whether or not the countermeasure has been tried, and a detailed explanation of the countermeasure. When the "tried" button 1112 is pressed, information that the countermeasure presented in the pain information 511 has been tried is stored. Depending on whether or not the "tried" button 1112 is pressed, the input items of the pain information input screen 901 may be changed. For example, when the "tried" button 1112 is pressed, the pain information input screen 901 displays an input item of whether or not the presented countermeasure was effective. When the "headache record" button 1113 is selected, the screen transitions to the pain information input screen 901.

[0121] If there is a help record, the remedy is displayed again, reminding the user of what remedy was displayed when the user had a headache. This allows accurate recording of whether the presented remedy was tried and whether the remedy was effective. If the presented remedy was ineffective, control can be performed so that the remedy is not displayed the next time the help button 603 is pressed.

[0122] 12 may be displayed instead of the Tried button 1112. When the Effective button 1201 is pressed, "Effective" is stored in the "How it worked" information of the pain information 511. When the Effective button 1201 is not pressed and the headache record button 1113 is selected, "Not effective" is stored (or the field is left blank). When the headache record button 1113 is selected, the screen transitions to the pain information input screen 901.

[0123] In step S1014, the CPU 201 of the information processing device 100 determines whether or not it has accepted pressing of the headache record button 1113. If it has been accepted, the process proceeds to step S1015, and if not, the remedy confirmation screen 1110 is kept displayed.

[0124] In step S1015, the CPU 221 of the server 102 transmits a related pain information input screen 901 to the information processing device 100. Specifically, the pain information input screen 901 including the pain information 511 stored on the same day as the day the reminder was notified is transmitted to the information processing device 100. If there is no corresponding pain information input screen 901, a new pain information input screen 901 is transmitted.

[0125] In step S1016, the CPU 201 of the information processing device 100 displays the received pain information input screen 901 on the touch panel 209. It is not necessary to input all items on the pain information input screen 901, and pressing of the save button 904 can be accepted even if there are items that have not been input. Note that required items (for example, items such as date and time, type of pain, and degree of pain) and optional items may be prepared. Also, in the case of (Pattern F), by accepting pressing of the No Headache button 903 without accepting input of each item, it is possible to store that there was no headache on that day. Note that, in the case where there is a help record in step S1003 or a detailed record in step S1007, it is also possible to control so that pressing of the No Headache button 903 cannot be accepted, for example, by not displaying the No Headache button 903 or by graying it out.

[0126] In step S1017, the CPU 201 of the information processing device 100 determines whether or not pressing of the save button 904 has been accepted. If it has been accepted, the process proceeds to step S1018, and if not, the pain information input screen 901 is kept displayed.

[0127] In step S1018, the CPU 221 of the server 102 stores the content entered on the pain information entry screen 901 as saved pain information 511.

[0128] In step S1019, CPU 221 of server 102 transmits a message to information processing device 100 after input is completed.

[0129] In step S1020, the CPU 201 of the information processing device 100 displays the received post-input completion message 1120 on the touch panel 209. An example of the post-input completion message is shown in Fig. 11(c). The post-input completion message 1120 displays the content that the input has been completed and a message containing a hope such as "I hope you don't have a headache tomorrow."

[0130] As described above, according to this embodiment, it is possible to more appropriately manage records of ailments such as headaches.

[0131] In this embodiment, the pressing instruction by the user operation may be a selection operation from a touch panel, an operation of an external device, or an operation by a gesture. Also, the information processing device 100 and the server 102 may communicate with each other every time information is input, and may transmit and receive information.

[0132] In this embodiment, the information processing device 100 and the server 102 communicate with each other, but the information processing device 100 may be the only device that performs the operations. That is, the processes that are executed by the server 102 may be executed by the information processing device 100 instead. For example, in this embodiment, the pain information 511 is stored in the server 102, but it may be stored in the ROM 202 or the external memory 211 of the information processing device 100. This allows the headache record application to be executed without the need for a separate server 102.

[0133] In addition, this embodiment may also be embodied as, for example, a system, an apparatus, a method, a program, or a storage medium, and specifically, may be applied to a system consisting of multiple devices, or may be applied to an apparatus consisting of a single device.

[0134] The present invention also includes a case where a software program for realizing the functions of the above-described embodiments is supplied to a system or device directly or remotely, and the present invention also includes a case where the computer of the system or device reads and executes the supplied program code to achieve the functions.

[0135] Therefore, the program code installed in a computer to realize the functional processing of the present invention also realizes the present invention, that is, the present invention includes the computer program itself for realizing the functional processing of the present invention.

[0136] Examples of recording media for supplying the program include flexible disks, hard disks, optical disks, magneto-optical disks, MOs, CD-ROMs, CD-Rs, CD-RWs, etc. In addition, there are magnetic tapes, non-volatile memory cards, ROMs, DVDs (DVD-ROMs, DVD-Rs), etc.

[0137] Another method of supplying the program is to connect to a homepage on the Internet using a browser on a client computer, and then download the computer program of the present invention itself, or a compressed file including an automatic installation function, from the homepage to a recording medium such as a hard disk.

[0138] It is also possible to realize the present invention by dividing the program code constituting the program of the present invention into multiple files and downloading each file from a different homepage. In other words, the present invention also includes a WWW server that allows multiple users to download program files for implementing the functional processing of the present invention on a computer.

[0139] It is also possible to encrypt the program of the present invention, store it on a storage medium such as a CD-ROM, and distribute it to users, and have users who meet certain conditions download key information for decrypting the program from a website via the Internet.Then, it is possible to execute the encrypted program using the downloaded key information and install it on a computer.

[0140] The functions of the above-mentioned embodiments are realized by the computer executing the read program. In addition, the functions of the above-mentioned embodiments can also be realized by the OS running on the computer performing part or all of the actual processing based on the instructions of the program.

[0141] Furthermore, the program read from the recording medium is written into a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Then, based on instructions from the program, a CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing, and the functions of the above-mentioned embodiment are also realized by this processing.

[0142] The above-mentioned embodiments are merely examples of the embodiment of the present invention, and the technical scope of the present invention is not limited to these. In other words, the present invention can be embodied in various forms without departing from its technical concept or main features. For example, the present invention can be embodied in applications other than headaches. [Explanation of symbols]

[0143] 100 Information processing device (mobile terminal, etc.) 101 Network 102 Server 201 CPU 202 ROM 203 RAM 209 Touch Panel 211 External Memory

Claims

1. A receiving unit receives a record of a user's illness by issuing an instruction to the first instruction receiving unit or the second instruction receiving unit; A notification means for notifying the user to record information about the illness; a control means for changing the content of the notification by the notification means based on the presence or absence of a record of the receipt of an instruction to the first instruction receiving unit and an input status of detailed information regarding the malfunction received when an instruction to the second instruction receiving unit is received; An information processing system comprising:

2. The information processing system according to claim 1, characterized in that when there is a record of an instruction being received by the first instruction receiving unit, the control means changes the content of the notification by the notification means to include a message to comfort a user who has experienced an illness.

3. The information processing system according to claim 2, characterized in that, when the detailed information has not been input, the control means changes the content of the notification by the notification means to include a message prompting the input of detailed information.

4. The information processing system according to claim 1, characterized in that, when the input of the detailed information is incomplete, the control means changes the content of the notification by the notification means to include a message urging the input of the detailed information.

5. The information processing system according to claim 1, characterized in that, when the input of the detailed information has been completed, the control means changes the content of the notification by the notification means to include a message praising the completion of recording.

6. The information processing system according to claim 1, characterized in that when there is no record of the receipt of an instruction to the first instruction receiving unit and no input of the detailed information, the control means changes the content of the notification by the notification means to include a message to check whether or not a malfunction has occurred.

7. 2. The information processing system according to claim 1, further comprising a display control means for controlling, when an operation in response to the notification is accepted, to display a screen for accepting input of the detailed information.

8. The information processing system described in claim 7, characterized in that when there is a record of receiving an instruction to the first instruction receiving unit and an operation is received in response to the notification, the display control means controls to display a screen that accepts an evaluation of the method of dealing with the malfunction that was notified to the user in response to receiving the instruction to the first instruction receiving unit, and then displays a screen that accepts input of detailed information.

9. The information processing system according to claim 8, characterized in that when there is no record of receiving an instruction to the first instruction receiving unit and an operation is received in response to the notification, the display control means controls to display a screen for accepting input of detailed information without displaying a screen for accepting an evaluation of the countermeasure.

10. The information processing system according to claim 8, characterized in that the display control means controls to display a reception section that accepts instructions to record information that no malfunction has occurred when there is no recording due to the reception of an instruction to the first instruction reception section and no input of the detailed information, and when an operation is received in response to the notification.

11. The information processing system according to claim 1, characterized in that the notification means notifies a message indicating that input has been completed when it receives an instruction to the reception unit to save the information entered on the screen that accepts input of the detailed information.

12. 2. The information processing system according to claim 1, wherein the notification means issues a notification prompting the user to record the malfunction at a time preset by the user.

13. 2. The information processing system according to claim 1, wherein said notification means issues said notification together with a face image of the person.

14. The information processing system according to claim 1, characterized in that when the reception means receives an instruction for the first instruction reception unit, the reception means controls the display of ways to deal with the malfunction to the user without displaying a screen for receiving detailed information regarding the user's malfunction.

15. 2. The information processing system according to claim 1, wherein when the receiving means receives an instruction for the second instruction receiving unit, the information processing system controls so as to display a screen for receiving input of detailed information.

16. 16. The information processing system according to claim 1, wherein the discomfort includes at least one of headache, lower back pain, neuralgia, dizziness, tinnitus, and fatigue.

17. A receiving step of receiving a record of a user's illness by an instruction to a first instruction receiving unit or a second instruction receiving unit; A notification step of notifying the user to record the malfunction; a control step of changing the content of the notification by the notification step based on the presence or absence of a record resulting from the receipt of an instruction to the first instruction receiving unit and an input status of detailed information regarding the malfunction received when an instruction to the second instruction receiving unit is received; A method for controlling an information processing system comprising:

18. A program for causing at least one computer to function as each of the means of the information processing system according to any one of claims 1 to 15.

Citation Information

Patent Citations

  • Image display device and television device

    JP2019040513A