Medical examination support device, medical examination support system, medical examination support method, and program

Abstract

To reduce a patient's feeling of aversion to medical examination.SOLUTION: A medical examination support device of an embodiment has an acquisition unit, a list creation unit, a provision unit, and a specification unit. The acquisition unit acquires patient basic information related to a target patient to be medically examined. The list creation unit sets a temporary medical examination flow for the target patient on the basis of the patient basic information, and creates an aversion target list that is a list of candidates for patient aversion points to which the target patient feels an aversion, from among medical examination situations related to medical examination acts included in the temporary medical examination flow. The provision unit provides virtual event information related to a virtual event for specifying the patient aversion points of the target patient on the basis of the created aversion target list. The specification unit specifies the patient aversion points of the target patient on the basis of the result of the virtual event executed by the target patient.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The embodiments disclosed in this specification and the drawings relate to a medical support device, a medical support system, a medical support method, and a program.

Background Art

[0002] A doctor who treats a patient creates a treatment plan, for example, and conducts medical treatment in accordance with the created treatment plan. The treatment plan is created including various medical items, but among the medical items, there are medical items that the patient may feel aversion to, for example, an injection that causes pain may be a medical item that the patient feels aversion to. In particular, when the patient is a child, cases where medical items that cause aversion are found are scattered. A patient who has a medical item that causes aversion may not be able to state the main complaint for reasons such as wanting to avoid the aversion. The inability to obtain the patient's main complaint becomes an obstacle when creating an efficient treatment plan.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the embodiments disclosed in this specification and the drawings is to reduce the patient's aversion in medical treatment. However, the problems to be solved by the embodiments disclosed in this specification and the drawings are not limited to the above problems. It is also possible to position the problems corresponding to the respective effects of each configuration shown in the embodiments described later as other problems.

Means for Solving the Problems

[0005] The medical support device according to the embodiment includes an acquisition unit, a list generation unit, a provision unit, and an identification unit. The acquisition unit acquires basic patient information regarding a target patient who is the subject of medical treatment. The list generation unit sets a provisional medical treatment flow for the target patient based on the basic patient information, and generates an aversion target list in which candidates for patient aversion points, which are the targets of aversion for the target patient, among the medical treatment situations regarding the medical treatment acts included in the provisional medical treatment flow, are listed. The provision unit provides virtual event information regarding a virtual event for identifying the patient aversion points of the target patient based on the generated aversion target list. The identification unit identifies the patient aversion points of the target patient based on the execution result of the virtual event by the target patient.

Brief Description of the Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Embodiments for Carrying Out the Invention

[0007] Hereinafter, a medical support device, a medical support system, a medical support method, and a program according to the embodiment will be described with reference to the drawings.

[0008] FIG. 1 is a block diagram showing an example of the configuration of the medical support system 1 according to the embodiment. The medical support system 1 according to the embodiment includes, for example, a patient terminal 10, a user terminal 20, a PHR (personal health record) management server 30, and a medical support device 100. The patient terminal 10, the user terminal 20, the PHR management server 30, and the medical support device 100 are communicable with each other via a network NW.

[0009] The patient terminal 10 is possessed by a patient or a guardian of the patient when the patient is a child or the like. The patient terminal 10 is, for example, a smartphone or a tablet terminal. The patient terminal 10 includes, for example, a transmission / reception interface 11, a touch panel 12, a control circuit 13, and a storage device 14.

[0010] The transmission / reception interface 11 transmits various types of information generated by the control circuit 13 to external devices, for example, the user terminal 20, the PHR management server 30, and the medical support device 100. The transmission / reception interface 11 receives various types of information transmitted by the external devices. The transmission / reception interface 11 outputs the received information to the control circuit 13 and the like.

[0011] The touch panel 12 functions as an input interface for a patient and his or her family (hereinafter, patients, etc.) to input information and an output interface for displaying input information and the like input by operations of patients, etc. The touch panel 12 displays, for example, a GUI (Graphical User Interface) or the like for receiving various input operations by patients, etc. The touch panel 12 transmits information corresponding to the received input operation to the control circuit 13.

[0012] The control circuit 13 includes a hardware processor that controls each device and the like in the patient terminal 10. The control circuit 13 performs display control for displaying a GUI on the touch panel 12, for example. Based on input information corresponding to an input operation received by the touch panel 12, the control circuit 13 controls each part in the patient terminal 10 or transmits the input information corresponding to the input operation to an external device using the transmission / reception interface 11.

[0013] The storage device 14 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, a hard disk, an optical disk, or the like. The storage device 14 stores basic patient information regarding the patient. The basic patient information includes information such as the patient's age, gender, symptoms, and medical history, for example. The control circuit 13 transmits the basic patient information stored in the storage device 14 in response to a request from the medical support device 100, for example.

[0014] The user terminal 20 includes, for example, a transmission / reception interface 21, an input interface 22, a control circuit 23, and a display device 24. The transmission / reception interface 21 transmits various types of information generated by the control circuit 23 to an external device, such as the patient terminal 10, the PHR management server 30, and the medical support device 100. The transmission / reception interface 21 receives various types of information transmitted by the external device. The transmission / reception interface 21 outputs the received information to the control circuit 23 and the like.

[0015] The input interface 22 receives various input operations by an operation of a user such as a doctor. The input interface 22 outputs information based on the received input operation to the control circuit 23. Note that in this specification, the input interface is not limited to only those having physical operation components such as a mouse and a keyboard. For example, an electric signal processing circuit that receives an electric signal corresponding to an input operation from an external input device provided separately from the device and outputs this electric signal to the control circuit is also included in the examples of the input interface.

[0016] The control circuit 23 includes a hardware processor that controls each device and the like in the user terminal 20. The control circuit 23 controls each part in the user terminal 20 based on input information corresponding to an input operation received by the input interface 22, for example. The control circuit 23 transmits, to an external device, input information corresponding to an input operation, for example, instruction information for giving an instruction to a location in the medical support device 100, using the transmission / reception interface 21. The control circuit 23 performs display control for causing the display device 24 to display various information, for example.

[0017] The display device 24 is, for example, a liquid crystal display, a CRT (Cathode Ray Tube), an organic EL (Electroluminescence) display, or the like. The display device 24 displays various information according to the control of the control circuit 23. The display device 24 may be a desktop type or a tablet terminal capable of wireless communication with the main body of the user terminal 20, for example.

[0018] The PHR management server 30 is a server that manages the PHRs of a plurality of patients. The PHR management server 30 stores an electronic medical record database (hereinafter referred to as DB) 31 including the PHRs of a plurality of patients. When the PHR of a patient is updated, the patient terminal 10 and the medical support device 100 transmit PHR information including the updated PHR information to the PHR management server 30. The PHR management server 30 updates or newly generates the electronic medical record DB 31 based on the transmitted PHR information. The PHR management server 30 transmits the electronic medical record included in the electronic medical record DB 31 in response to a request from the medical support device 100, for example.

[0019] The medical support device 100 includes, for example, an input interface 110, a display 120, a memory 130, a processing circuit 140, and a transmission / reception interface 150. The input interface 110 receives various input operations by an operation of an operator or the like. The input interface 110 outputs information based on the received input operation to the processing circuit 140.

[0020] The input interface 110 includes, for example, a mouse, a keyboard, a trackball, a switch, a button, a joystick, a touch panel, etc. The input interface 110 may be a user interface that accepts voice input such as a microphone. When the input interface 22 is a touch panel, the input interface 110 may also have the display function of the display 120.

[0021] The display 120 is, for example, a liquid crystal display, an organic EL display, or the like. The display 120 displays various information according to the control of the processing circuit 140. The display 120 may be a desktop type or a display device such as a tablet terminal capable of wireless communication with the main body of the medical support device 100.

[0022] The memory 130 is realized by, for example, semiconductor memory elements such as RAM and flash memory, hard disks, optical disks, etc. The memory 130 stores, for example, an aversion point candidate DB 131, a virtual event DB 132, and an aversion target list 133. The memory 130 also stores the basic patient information transmitted by the patient terminal 10.

[0023] FIG. 2 is a diagram showing an example of the content of the aversion point candidate DB 131. The aversion point candidate DB 131 is a DB that lists, as aversion point candidates, medical situations in which a patient may feel aversion among medical situations that may be incorporated into the medical process. The medical situations include the medical act itself and situations related to the medical act. Specifically, examples of the medical situations include "face-to-face examination by a doctor", "MRI examination", "injection", "taking medicine", "hospitalization", etc. The aversion point candidate DB 131 is a DB created in advance based on past history, statistics, etc.

[0024] FIG. 3 is a diagram showing an example of the content of the virtual event DB 132. The virtual event DB 132 is a DB of virtual events that requests a patient to execute when a medical situation that is a candidate for an aversion point is incorporated into the medical flow. The virtual event DB 132 further includes data on the reason why the patient dislikes the medical situation that becomes the aversion point (hereinafter referred to as the aversion reason) and countermeasures against the patient's aversion for each aversion reason. The virtual event DB 132 is a DB created in advance based on past history, statistics, and the like.

[0025] For example, when the aversion point is "face-to-face examination by a doctor", a virtual event called "Team Quest" becomes the virtual event requested to the patient. Similarly, when the aversion point candidates are "face-to-face examination by a doctor", "MRI examination", "injection", "taking medicine", and "hospitalization", virtual events called "Hide-and-Seek", "Endurance Quest", "Rotating Sushi Game", and "Dinosaur Park" become the virtual events requested to the patient.

[0026] "Team Quest" is a virtual event in which a team including a virtual child who becomes the patient's avatar and other characters challenges a quest. For example, the patient becomes a virtual child and challenges the quest. "Hide-and-Seek" is a virtual event in which members including a virtual child who becomes the patient's avatar and other characters play "hide-and-seek".

[0027] "Endurance Quest" is an event or quest to improve endurance. "Rotating Sushi Game" is a virtual event in which members including a virtual child who becomes the patient's avatar and other characters play "rotating sushi play". "Dinosaur Park" is a virtual event in which members including a virtual child who becomes the patient's avatar and other characters play "making a dinosaur park together by folding paper".

[0028] Furthermore, for example, when the aversion point is "face-to-face consultation with a doctor", reasons for aversion such as "difficulty in consultation" and "desire for encouragement" are assumed. The reason for aversion of "difficulty in consultation" is, for example, due to the patient having a personality that makes it difficult to consult a doctor about their worries or ask questions. Also, the reason for aversion of "desire for encouragement" is, for example, due to the patient having a personality that desires words of encouragement like a pat on the back.

[0029] Also, when the aversion point is "MRI examination", the reason for aversion of "enclosed space (sense of oppression)" is, for example, due to the patient having a feeling that makes them easily feel an enclosed space or a sense of oppression. The reason for aversion of "noise" is, for example, due to the patient being averse to loud noises.

[0030] Also, when the aversion point is "injection", the reason for aversion of "pain, fear of the needle tip" is, for example, due to the patient feeling pain or having needle phobia. The reason for aversion of "odor" is, for example, due to the patient being averse to the odor of drugs.

[0031] Also, when the aversion point is "taking medicine", the reason for aversion of "tactile sensation on the tongue" is, for example, due to the patient being averse to feeling powdery or syrupy. The reason for aversion of "taste" is, for example, due to the patient being averse to tastes such as sweet, bitter, or sour.

[0032] Also, when the aversion point is "hospitalization (hospital ward environment)", the reason for aversion of "only adults" is, for example, when the patient is a child, due to the patient disliking an environment where only adults are around. The reason for aversion of "desire for peers" is, for example, due to the patient preferring to be with only those of the same age. The reason for aversion of "private room" is, for example, due to the patient preferring to be alone.

[0033] A countermeasure plan for aversion is data that specifically specifies measures to reduce the aversion felt by the patient. Measures to reduce aversion include measures to avoid the medical examination items that cause aversion, and measures to minimize the aversion felt by the patient during the execution of the medical examination items while still performing the items themselves.

[0034] For example, when the aversion point is "face-to-face examination by a doctor" and the reason for aversion is "difficult to consult", as a countermeasure plan, the examination is carried out by a "virtual doctor". Also, when the reason for aversion is "hoping for encouragement", as a countermeasure plan, a "suitable doctor", for example, a doctor who gives a lot of encouraging words (real doctor), is specified.

[0035] Also, when the aversion point is "MRI examination" and the reason for aversion is "enclosed space (feeling of pressure)", as a countermeasure plan, an "open type" MRI device is used. Also, when the reason for aversion is "noise", as a countermeasure plan, "earplugs" are provided or "music viewing" is allowed during the examination.

[0036] Also, when the aversion point is "injection" and the reason for aversion is "pain, fear of the needle tip", as a countermeasure plan, measures such as "distracting attention" and "showing the patient something other than the needle" are taken. Also, when the reason for aversion is "odor", as a countermeasure plan, an "air purifier" is installed or ventilation is carried out sufficiently.

[0037] Also, when the aversion point is "taking medicine" and the reason for aversion is "taste on the tongue", as a countermeasure plan, the patient is made to take the medicine in a state where it is difficult to feel aversion by using "powder medicine, tablets, syrup, oblate", etc. Also, when the reason for aversion is "taste", as a countermeasure plan, a taste that the patient is "not bad at" is selected and used as a medicine.

[0038] Also, when the aversion point is "hospitalization (hospital ward environment)", if the reason for aversion is any of "only adults", "desire for the same age group", or "private room", a hospital ward that meets the patient's wishes shall be provided. For example, if the reason for aversion is "only adults", a ward with a mix of children and adults shall be provided; if the reason for aversion is "desire for the same age group", a ward for the same age group only shall be provided; and if the reason for aversion is "private room", a private room shall be provided.

[0039] Figure 4 is a diagram showing an example of the content of the aversion target list 133. The aversion target list is, for example, a list created in accordance with the creation of a treatment flow for a specific patient. The aversion target list 133 is a list that includes treatment items that are candidates for the aversion points of the target patient and countermeasures for the aversion point candidates. In the example shown in Figure 4, the items "face-to-face consultation by a doctor", "injection", "medication", and "hospitalization" are included as candidates for the aversion points of the target patient. The aversion target list 133 may not include countermeasures.

[0040] The processing circuit 140 includes, for example, an acquisition function 141, a list generation function 142, a provision function 143, a specification function 144, a presentation function 145, and a countermeasure generation function 146. The processing circuit 140 realizes these functions, for example, by a hardware processor executing a program stored in the memory 130 (storage device, storage circuit).

[0041] The hardware processor means, for example, a circuit such as a CPU (Central Processing Unit), GPU (Graphics Processing Unit), application specific integrated circuit (ASIC), programmable logic device (for example, simple programmable logic device (SPLD) or complex programmable logic device (CPLD), field programmable gate array (FPGA)).

[0042] Instead of storing the program in the memory 130, it may be configured to directly incorporate the program into the circuit of the hardware processor. In this case, the hardware processor realizes its functions by reading and executing the program incorporated in the circuit. The above program may be stored in the memory 130 in advance, or may be stored in a non-transitory storage medium such as a DVD or a CD-ROM, and may be installed from the non-transitory storage medium to the memory 130 when the non-transitory storage medium is mounted on a drive device (not shown) of the medical support device 100.

[0043] The hardware processor is not limited to being configured as a single circuit, and may be configured as one hardware processor by combining a plurality of independent circuits so as to realize each function. Also, a plurality of components may be integrated into one hardware processor to realize each function.

[0044] The acquisition function 141 acquires basic patient information regarding a target patient to be treated. The basic patient information of the patient is transmitted, for example, by the patient terminal 10. The acquisition function 141 stores the basic patient information transmitted by the patient terminal 10 in the memory 130. The acquisition function 141 may acquire basic patient information transmitted by an external device other than the patient terminal 10 such as the user terminal 20. The acquisition function 141 is an example of an acquisition unit.

[0045] Based on the basic patient information acquired by the acquisition function 141, the list generation function 142 sets a provisional medical treatment flow for the target patient. The list generation function 142 generates an aversion target list in which candidates for patient aversion points that are the aversion targets of the target patient are listed among the medical treatment statuses regarding the medical treatment acts included in the set provisional medical treatment flow. The list generation function 142 is an example of a list generation unit.

[0046] The providing function 143 determines virtual event information (hereinafter referred to as virtual event information) regarding a virtual event for specifying the patient aversion points of the target patient based on the aversion target list generated by the list generation function 142. The providing function 143 provides the determined virtual event information by transmitting it to the patient terminal 10. The providing function 143 is an example of a providing unit.

[0047] The target patient executes a virtual event according to the information transmitted to the patient terminal 10. The patient terminal 10 acquires the behavior information of the target patient when the virtual event is executed. The behavior information may be detected by the patient terminal 10, for example, or may be input to the patient terminal by the target patient or a guardian when the target patient is a child. The behavior information is an example of the execution result of the virtual event.

[0048] The patient terminal 10 transmits the acquired behavior information of the target patient to the medical support device 100. The specifying function 144 acquires the behavior information of the target patient transmitted by the patient terminal 10. The specifying function 144 specifies, based on the acquired behavior information of the target patient, among the aversion point candidates, the medical situation that becomes the patient aversion point of the target patient and the reason for aversion of the patient aversion point. The specifying function 144 is an example of a specifying unit.

[0049] The presenting function 145 presents the patient aversion points and reasons for aversion specified by the specifying function 144 by displaying them on the display 120. The user views the patient aversion points and reasons for aversion displayed on the display 120 and considers countermeasures, modifies or maintains the medical process. When the user creates a countermeasure, the user inputs the countermeasure through the input interface 110. The presenting function 145 is an example of a presenting unit.

[0050] The countermeasure generation function 146 refers to the virtual event DB 132 for the medical treatment situations and reasons for aversion that are the patient aversion points identified by the specific function 144, identifies countermeasures to avoid the patient aversion points of the target patient, and reduce the aversion feeling the patient remembers. The countermeasure generation function 146 obtains and identifies, for example, the countermeasures specified by the input operation of the user. The countermeasure generation function 146 is an example of a countermeasure generation unit. The presentation function 145 may display on the display 120 together with the medical treatment flow in which the countermeasures identified by the countermeasure generation function 146 are modified.

[0051] The transmission / reception interface 150 transmits various information generated by the processing circuit 140 to external devices such as the patient terminal 10, the user terminal 20, and the PHR management server 30. The transmission / reception interface 21 receives various information transmitted by the external device, for example, the basic patient information transmitted by the patient terminal 10 and the electronic medical record transmitted by the PHR management server 30, and outputs the received information to the processing circuit 140 and the like. The transmission / reception interface 150 is an example of a transmission / reception unit.

[0052] The transmission / reception interface 11 in the patient terminal 10 transmits, for example, the basic patient information to the medical treatment support device 100 and receives the virtual event information transmitted by the medical treatment support device. The transmission / reception interface 11 transmits the execution result of the virtual event to the medical treatment support device 100. The transmission / reception interface 11 is an example of a terminal transmission / reception unit.

[0053] The control circuit 13 in the patient terminal 10 causes the target patient to execute a virtual event according to the virtual event information transmitted by the medical treatment support device 100. The virtual event may be executed by the target patient operating the patient terminal 10, or may be implemented using a device other than the patient terminal 10, for example, a smartphone, a tablet, a VR (Virtual Reality) device, etc. other than the patient terminal 10. The control circuit 13 is an example of a control unit.

[0054] Next, the processing in the medical support device 100 will be described. FIG. 5 is a flowchart showing an example of the processing in the medical support device 100. The flowchart shown in FIG. 5 shows the processing of the medical support device 100 when a support flow is created by a user's operation.

[0055] First, according to an instruction based on an operation of the input interface 110 by an operator or an instruction transmitted by the user terminal 20, the acquisition function 141 of the medical support device 100 acquires basic patient information (step S101). The acquisition function 141 may acquire the basic patient information transmitted by the patient terminal 10, or may acquire the basic patient information stored in the storage unit 170.

[0056] Subsequently, according to an instruction based on an operation of the input interface 110 by an operator or an instruction transmitted by the user terminal 20, the acquisition function 141 requests the PHR management server 30 to transmit the electronic medical record of the target patient. The acquisition function 141 acquires the PHR of the target patient transmitted by the PHR management server 30 (step S103).

[0057] Subsequently, the list generation function 142 sets a provisional medical flow for treating the target patient based on the basic patient information acquired by the acquisition function 141 or the PHR information included in the electronic medical record (step S105). The list generation function 142 estimates the medical situation that the target patient will undergo from the current medical history and the like included in the basic patient information to generate a provisional medical flow, or directly generates a provisional medical flow from the PHR information.

[0058] The list generation function 142 refers to the medical items included in the generated provisional medical flow in the aversion point candidate DB 131, extracts and lists the patient aversion point candidates, and generates an aversion target list 133 (step S107). Subsequently, the provision function 143 determines virtual event information for requesting the target patient to execute based on the generated aversion target list (step S109).

[0059] Subsequently, the providing function 143 provides the determined virtual event information by transmitting it to the patient terminal 10 (step S111). The patient terminal 10 receives the virtual event information transmitted by the medical support device 100 and causes the virtual event indicated in the transmitted virtual event information to be executed on the target patient.

[0060] After the virtual event is executed, the patient terminal 10 acquires the action information of the target patient when the virtual event is executed and transmits the acquired action information to the medical support device 100. The medical support device 100 receives the action information transmitted by the patient terminal 10 through the transmission / reception interface 150 and acquires it through the specifying function 144 (step S113).

[0061] Based on the acquired action information, the specifying function 144 specifies the aversion points and reasons for aversion of the target patient (step S115). Subsequently, the presenting function 145 provides the aversion points and reasons for aversion of the target patient specified by the specifying function 144 to the user by displaying them on the display 120 (step S117).

[0062] Subsequently, the countermeasure generation function 146 generates countermeasures based on the aversion points and reasons for aversion of the target patient specified by the specifying function 144 (step S119). The countermeasures may be generated by referring to the virtual event DB 132 or may be generated according to the input operation of the user who has viewed the display 120. The presenting function 145 presents the countermeasures together with the aversion points and reasons for aversion of the target patient by displaying them on the display 120 (step S119). Thus, the medical support device 100 ends the process shown in FIG. 5.

[0063] Next, a specific example of identifying the aversion points of the patient to be treated will be described. In each of the following specific examples, it is assumed that the target patient is a child. First, the case where the aversion point is "face-to-face examination by a doctor" will be described as an example. When the aversion point is "face-to-face examination by a doctor", "Team Quest" is determined as the virtual event. "Team Quest" is, for example, a virtual event that is executed while the target patient views the image displayed on the patient terminal 10.

[0064] FIG. 6 is a diagram showing an example of an image displayed on the touch panel 12 of the patient terminal 10 when "Team Quest" is executed as a virtual event. When "Team Quest" is executed, the first character CA1 to the fourth character CA4 are displayed, and one of these characters becomes the avatar of the target patient. Here, it is assumed that the first character CA1 is the avatar of the target patient. In "Team Quest", an event is executed in which the first character CA1 to the fourth character CA4 form a team and challenge a quest (mission).

[0065] The reasons for aversion when the aversion point is "face-to-face examination by a doctor" include reasons such as "difficulty in consultation" and "hope for encouragement". The virtual event of "Team Quest" is an event for identifying an image of a trustworthy person, and by executing the virtual event of "Team Quest" by the target patient, the characteristics of a trustworthy person are extracted from the actions of the target patient.

[0066] In the virtual event of "Team Quest", first, the roles of each character are determined. For example, the first character CA1 is set as the "Warrior", the second character CA2 is set as the "Wizard", the third character CA3 is set as the "Healer", and the fourth character CA4 is set as the "Sage". There may be other characters, such as "Familiar".

[0067] While the virtual event of "Team Quest" is being held, observe the actions of the first character CA1. As a result, for example, if the subject patient often acts alone without acting together with other characters, extract the characteristic that the subject patient tends to think it is better to be alone.

[0068] Also, if the mission is often advanced while consulting with friends, extract the characteristic that the subject patient tends to think it is better to be with friends. At this time, the first character CA1 extracts the characteristics of a trustworthy person by differentiating the characteristics of the partner such as having a long explanation, being concise in explanation, praising, and encouraging. In addition, when the first character CA1 takes actions such as watching silently, leaving the action to other characters, or not acting until told by other characters, extract the characteristic that the subject patient tends to leave things to others.

[0069] Next, take the case where the aversion point is "hospitalization" as an example for explanation. When the aversion point is "hospitalization", "Dinosaur Park" is determined as the virtual event. "Dinosaur Park" is, for example, a virtual event in which the subject patient processes the origami image displayed on the patient terminal 10 into a dinosaur.

[0070] FIG. 7 is a diagram showing an example of a plurality of dinosaurs made of origami when the "Dinosaur Park" is executed as a virtual event. When the "Dinosaur Park" is executed, for example, a plurality of children including the patient enter the room, and each folds origami to make a dinosaur. The dinosaur park is formed by the dinosaurs made by the plurality of children.

[0071] In FIG. 7, the first dinosaur model MA1 to the seventh dinosaur model MA7 are shown as dinosaurs formed by folding a plurality of origami. For example, a plurality of operators each use their ingenuity to make a dinosaur. The dinosaur may be something that the terminal operator can create with their own ideas, or it may be something that can be made by following a pre-created procedure.

[0072] While creating a dinosaur park, children talk to each other and sing songs. While creating a dinosaur park, children may create dinosaurs or other things with building blocks or clay, or may participate in a cooking class or the like. While children are creating a dinosaur park, guardians observe the children's actions.

[0073] For example, guardians observe whether a child casually talks to other children of the same age, is not afraid of adults when there are adults around, is not afraid even if the guardian suddenly disappears, or is working silently alone. The guardian inputs the observed actions of the child, for example, the actions of the patient, into the patient terminal 10. The patient terminal 10 generates information regarding the input actions of the patient and transmits it to the medical support device 100. Based on the transmitted information regarding the actions of the patient, the medical support device 100 identifies the reason for aversion and creates an environment in the hospital room suitable for the patient at the time of hospitalization.

[0074] In the above embodiment, the countermeasure generated by the countermeasure generation function 146 is a measure to reduce the sense of aversion, but the countermeasure may also be a measure to give an incentive to the target patient to make the target patient forget the sense of aversion. The incentive may be, for example, a sticker, a card, origami, a medal, a stamp, etc. assuming that the target patient is a child. The incentive may be selected, for example, based on a questionnaire about things or activities that children are currently engrossed in and collected from a plurality of children.

[0075] According to at least one embodiment described above, an acquisition unit that acquires basic patient information regarding a target patient to be treated, sets a preliminary treatment flow for the target patient based on the basic patient information, and lists candidates for patient aversion points that are aversive targets for the target patient among the treatment statuses regarding treatment actions included in the preliminary treatment flow. A list generation unit that generates an aversion target list, a provision unit that provides virtual event information regarding a virtual event for specifying the patient aversion points of the target patient based on the generated aversion target list, and based on the execution result of the virtual event by the target patient A specifying unit that specifies the patient aversion points of the target patient can reduce the patient's aversion in medical treatment.

[0076] Although several embodiments have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, as well as in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0077] 1…Medical support system 10…Patient terminal 11, 21, 150…Transmission / reception interface 12…Touch panel 13…Control circuit 14…Storage device 20…User terminal 22, 110…Input interface 23…Control circuit 24…Display device 30…PHR management server 31…Electronic medical record DB 100…Medical support device 120…Display 130…Memory 131…Aversion point candidate DB 132... Virtual event DB 133... List of objects of aversion 140... Processing circuit 141... Acquisition function 142... List generation function 143... Provision function 144... Identification function 145... Presentation function 146... Countermeasure generation function 170... Memory unit CA1... First character CA2... Second character CA3... Third character CA4... Fourth character

Claims

1. An acquisition unit that acquires patient basic information regarding a target patient who is the subject of medical treatment; Based on the patient basic information, a preliminary medical treatment flow for the target patient is set, and a list generation unit that generates a list of candidates for patient aversion points that are the target of aversion of the target patient among the medical treatment statuses regarding the medical treatment acts included in the preliminary medical treatment flow; A provision unit that provides virtual event information regarding a virtual event for specifying the patient aversion points of the target patient based on the generated list of aversion targets; A specifying unit that specifies the patient aversion points of the target patient based on the execution result of the virtual event by the target patient, comprising a medical treatment support device. Medical treatment support device.

2. Further comprising a presentation unit that presents the specified patient aversion points, the medical treatment support device according to Claim 1. The medical treatment support device according to Claim 1.

3. The patient aversion points include at least one of face-to-face examination by a doctor, MRI examination, injection, taking medicine, or the environment of a specific hospital room, the medical treatment support device according to Claim 1. The medical treatment support device according to Claim 1.

4. Further comprising a countermeasure generation unit that generates countermeasures for avoiding the patient aversion points of the target patient, the medical treatment support device according to Claim 1. The medical treatment support device according to Claim 1.

5. The countermeasure generation unit generates countermeasures for reducing the aversion feeling of the target patient, the medical treatment support device according to Claim 4. The medical treatment support device according to Claim 4.

6. The countermeasure generation unit generates countermeasures for giving an incentive to the target patient to forget the aversion feeling of the target patient, the medical treatment support device according to Claim 4. The medical treatment support device according to Claim 4.

7. The medical treatment support device according to Claim 2, Including a patient terminal used by the target patient, The medical treatment support device, Further comprising a transmission / reception unit that receives the patient basic information transmitted by the patient terminal and transmits the generated virtual event information, The presentation unit presents the patient aversion points to the user, The patient terminal, A terminal transmission / reception unit that transmits the patient basic information to the medical treatment support device and receives the virtual event information transmitted by the medical treatment support device, And a control unit that causes the target patient to execute a virtual event according to the received virtual event information, The terminal transmission / reception unit transmits the execution result of the virtual event to the medical treatment support device that transmits it, Medical treatment support system.

8. A computer, Acquires patient basic information regarding a target patient who is the subject of medical treatment, Based on the patient's basic information, set a preliminary diagnosis flow for the target patient, and generate an aversion target list that lists candidates for patient aversion points that are the targets of aversion for the target patient among the medical treatment situations related to the medical treatment acts included in the preliminary diagnosis flow. Based on the generated aversion target list, provide virtual event information regarding a virtual event for identifying the patient aversion points of the target patient. Identify the patient aversion points of the target patient based on the execution result of the virtual event by the target patient. Medical support method.

9. On a computer, Obtain patient basic information regarding a target patient who is the subject of medical treatment. Based on the patient's basic information, set a preliminary diagnosis flow for the target patient, and generate an aversion target list that lists candidates for patient aversion points that are the targets of aversion for the target patient among the medical treatment situations related to the medical treatment acts included in the preliminary diagnosis flow. Based on the generated aversion target list, provide virtual event information regarding a virtual event for identifying the patient aversion points of the target patient. Cause the computer to identify the patient aversion points of the target patient based on the execution result of the virtual event by the target patient. Program.

Images