WO2015025482A1 - Medical treatment assistance system, medical treatment assistance method, and medical treatment assistance program - Google Patents

Abstract

A medical treatment assistance system (100) comprises a medical treatment device (1) which a first user manipulates, a control device (21) which acquires information on the usage of the medical treatment device (1) by a first user, a display device (22) which is controlled by the control device (21), and a server (3) which is capable of being connected to the control device (21) and which acquires the information on the usage of the medical treatment device (1) by the first user. The control device (21) acquires information on the usage of the medical treatment device (1) by a second user from a server (3) and causes the display device (22) to display the information on the usage of the medical device (1) by the second user, thereby increasing the motivation of the user to continue using the medical treatment device (1).

Description

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

The present invention relates to a medical support system including a medical device such as a drug injection device for injecting a drug such as insulin or growth hormone, and a communication device.

Conventional medical support systems of this type include medical devices used by users and related parties (hereinafter simply referred to as users), portable communication devices that obtain usage information of the medical devices, and portable communication devices. And a server to which the usage information of the medical device is transmitted (for example, Patent Document 1 below is given as a similar prior document).

JP 2006-271863 A

In the above conventional example, the medical device usage information (usage date, user information, etc.) used by the user is transmitted to the server via the mobile communication device, for example, the doctor confirms the usage information from the server. In addition, medical advice is given to users.
In such a system, a doctor gives medical advice to the user based on the usage information of the medical device obtained from the server. However, the advice from the doctor tends to be a so-called command or instruction for the patient, and the user's awareness of continuous use may not be enhanced.
For example, if the user does not use the medical device properly and continuously, the advice from the doctor is also an expression that condemns it. Such advice does not increase the user's awareness of continuous use.

As described above, the conventional medical support system does not include a configuration for improving the consciousness of the user to use the medical device appropriately and continuously, in addition to the advice from the doctor.
Therefore, the present disclosure is intended to provide a medical support system, a medical support method, and a medical support program that are configured to improve the user's awareness of continuous use of medical devices.

A medical support system according to the present disclosure is connectable to a medical device operated by a first user, a control device that acquires usage information of the first user's medical device, a display device controlled by the control device, and a control device And a server that acquires usage information on the medical device of the first user.
The control device acquires the usage information of the second user's medical device from the server, and causes the display device to display the usage information of the second user's medical device.

The medical support system, medical support method, and medical support program according to the present disclosure are effective for improving the user's awareness of continuous use of medical devices.

Schematic configuration diagram of a medical support system according to Embodiment 1 Perspective view of medical equipment of the medical support system Perspective view of the medical device Cross section of the medical device Control block diagram of the medical device Control block diagram of portable communication device of medical support system according to embodiment 1 Control block diagram of server of the medical support system The figure which shows the screen transition of the display part of the portable communication apparatus which concerns on Embodiment 1. FIG. Operation flowchart of medical device according to embodiment 1 Operational Flowchart Between Mobile Communication Device and Server According to Embodiment 1 Operational flow chart between medical device and portable communication device according to Embodiment 1 Operational Flowchart Between Mobile Communication Device and Server According to Embodiment 1 Schematic configuration diagram of a medical support system according to Embodiment 2 Cross-sectional view of the medical device of the medical support system Control block diagram of the medical device Operational flow chart between medical device and server according to Embodiment 2 Operation flowchart of the medical device Operation flowchart between the medical device and the server The figure which shows the screen transition of the display part of the medical device The figure which shows the screen transition of the display part of the portable communication apparatus in the medical assistance system which concerns on Embodiment 3. The figure which shows the screen transition of the display part of the portable communication equipment The figure which shows the screen transition of the display part of the portable communication equipment The figure which shows the screen transition of the display part of the portable communication equipment Operational flow chart between portable communication device and server according to Embodiment 3 Operation flowchart between the portable communication device and the server Operation flowchart between the portable communication device and the server Operation flowchart between the portable communication device and the server Operation flowchart between medical device and portable communication device according to Embodiment 3 Operational flow chart between portable communication device and server according to Embodiment 3

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
(Embodiment 1)
[1-1. Constitution]
FIG. 1 shows an example of a medical support system 100 including a medical device used by a user according to the first embodiment. The medical support system 100 includes a drug injection device 1 (an example of a medical device) that is a medical device, a mobile communication device 2 (an example of a mobile communication device) that obtains usage information of the drug injection device 1, and the mobile communication device. 2 includes a server 3 (an example of a server) to which usage information of the medicine injection device 1 is transmitted.
[1-1-1. Configuration of drug injection device]
With reference to FIGS. 2 to 5, the configuration of the pharmaceutical injection device 1 will be described. 2 and 3 schematically show the appearance of the drug injection device 1. FIG. 4 schematically shows an internal configuration of the drug injection device 1. FIG. 5 shows a functional configuration of the drug injection device 1.

As shown in FIGS. 2 to 4, the drug injection device 1 includes a main body case 4, a lid 5 provided in a part of the main body case 4, a piston 7 mounted inside, a power switch 9, a drug, And an injection switch 10 that is operated when performing an injection operation. The drug injection device 1 is also equipped with a short-range communication unit 17 configured by an NFC IC and performing short-range wireless communication, a battery 19, a display unit 34 including a liquid crystal, an organic EL display, and the like, and a preparation syringe 6 And a needle detection switch 35 for detecting the attachment of the injection needle 8.
As shown in FIGS. 2 and 3, the pharmaceutical injection device 1 is opened with the lid 5 of the main body case 4 and the preparation syringe 6 is attached. When the drug injection device 1 is used, the injection needle 8 is attached to the tip of the preparation syringe 6 as shown in FIG. By pushing the piston 7 into the preparation syringe 6, the preparation can be injected into the human body from the injection needle 8.

The preparation stored in the preparation syringe 6 is, for example, insulin that a diabetic patient injects into the human body.
The drug injection device 1 includes an injection switch 10 in addition to the power switch 9 in order to perform such an insulin injection operation. The power switch 9 and the injection switch 10 are controlled as shown in FIG. Connected to the unit 11.
The control unit 11 is configured by a processor such as a CPU. A drive motor 12 for driving the piston 7 is connected to the control unit 11 via a motor drive circuit 13. Further, a current detection circuit 14 is connected to the motor drive circuit 13, and this current detection circuit 14 is also connected to the control unit 11. The drive motor 12 is connected to an encoder 15 that detects the rotational speed of the drive motor 12. The encoder 15 is also connected to the control unit 11.

The operation of the piston 7 is executed by the drive motor 12 while checking the position information of the piston 7 by the encoder 15.
The control unit 11 is also connected to a memory 16 in which an operation program is stored.
Furthermore, the control unit 11 is connected to the above-mentioned short-range communication unit 17 that performs short-range communication and a memory 18 that stores usage information of the drug injection device 1. The control unit 11 is connected to the power switch 9, the injection switch 10, the display unit 34 described above, the needle detection switch 35, and the syringe detection switch 33.
In addition, the code | symbol 19 of FIG. 5 points out the battery for performing operation | movement of each part.
[1-1-2. Configuration of mobile communication device]
Next, the configuration of the mobile communication device 2 shown in FIG. 1 will be described. The mobile communication device 2 is a communication device that can be carried by the user of the medical device 1, such as a smartphone, a mobile phone, and a PC.

As shown in FIG. 6, the mobile communication device 2 is connected to a control unit 21 (an example of a control device) configured by a processor such as a CPU and the control unit 21, and communicates with the server 3 or other network or telephone. And a communication unit 20 for performing communication. Furthermore, the mobile communication device 2 includes a display unit 22 (an example of a display device) configured by a liquid crystal display, an organic EL display, and the like, a touch panel 23 serving as an operation unit displayed in the display unit 22, a power switch 24, and a GPS. A configured position information detection unit 25 (an example of a position information detection unit), a sounder 26 that outputs sound, a memory 27 that stores an operation program for executing the operation of each unit, and a battery 28 for performing the operation of each unit. Are respectively connected to the control unit 21.
As shown in FIG. 6, the present embodiment is characterized in that the control unit 21 of the mobile communication device 2 includes a near-field communication unit 17 configured by an NFC IC or the like that performs near-field communication with the near-field communication unit 17 of the drug injection device 1. That is, the distance communication unit 29 is connected. That is, the usage information of the medicine injection device 1 is obtained by the short-range communication (executed by bringing them close to each other) between the short-range communication unit 17 of the medicine injection device 1 and the short-range communication unit 29 of the mobile communication device 2. It is transmitted to the mobile communication device 2.

[1-1-3. Server configuration]
Next, the configuration of the server 3 shown in FIG. 1 will be described. The server 3 is a computer device that is operated by software.
As shown in FIG. 7, the server 3 includes a communication unit 30 that communicates with the communication unit 20 of the mobile communication device 2, a control unit 31 that is connected to the communication unit 30 and includes a processor such as a CPU, And a storage unit 32 connected to the control unit 31. The storage unit 32 is configured by a semiconductor memory, a magnetic memory, or the like.
[1-2. Operation]
Hereinafter, the operation of the medical support system 100 in the present embodiment will be described. As shown in FIG. 8, the medical support system 100 according to the present embodiment is characterized in that it is in the same situation via the server 3 using the mobile communication device 2 registered by the user (patient or related party). It is to create a use environment of the pharmaceutical injection device 1 that can be sympathized with other users by making it possible to acquire usage information of the user. When the user uses the drug injection device 1 in such an environment, the user's awareness of continuous use of the drug injection device 1 can be improved.

That is, the medical support system 100 according to the present embodiment has many people on the display unit 22 of the mobile communication device 2 as shown in FIG. , Having a configuration that allows the user to confirm what those people have. By checking such information, the user can use the drug injection device 1 in a state of empathy with the efforts of the patient companions in the same situation.
[1-2-1. Screen operation]
Specifically, as shown in FIG. 8, the screen of the display unit 22 of the mobile communication device 2 changes from 122 (a) to 122 (b).
The screen 122 (a) is an initial screen when the application of the medical support system 100 is activated in the mobile communication device 2. By starting the application, communication between the mobile communication device 2 and the server 3 becomes possible as will be described later.

The screen 122 (b) displays a map of the country or region where the user resides. In the map, the distribution of users who have performed insulin injection is displayed today. Therefore, users (patients) can confirm at a glance that there are many people with the same circumstances as themselves, recognize the existence of many hard colleagues, and have empathy. it can.
The screen 122 (c) is used for data transmission / reception between the short-range communication unit 17 of the medicine injection device 1 (injector) and the short-range communication unit 29 of the portable communication device 2 after communication with the server 3 becomes possible. 4 is a screen that prompts the portable communication device 2 to be close to the medicine injection device 1. After the drug injection operation is performed by the drug injection device 1, the user holds the portable communication device 2 over the drug injection device 1 to transmit the drug injection data from the drug injection device 1 to the portable communication device 2 by short-range wireless communication. Is done.

Screen 122 (d) shows a message input screen. Here, a function is shown in which the user can input his / her current thoughts and concerns or a seasonal topic at the place of use as a message and send the message to the server 3. With this function, users can send their thoughts and concerns in the form of messages to patient peers in the same situation. For this reason, the user can usually send to the same patient companion that he / she is worried about himself / herself without being able to say to people around him (non-patients). . In this way, it is possible to interact with many patient friends and share each other's worries.
The screen 122 (e) is a screen indicating that the mobile communication device 2 is communicating with the server 3 and a message is being transmitted to the server 3.

The screen 122 (f) displays a message that has arrived unnamed from another patient or a related person of the patient. This is a function for causing the mobile communication device 2 of the user to receive a message sent from a patient patient who is registered in the same manner, and causing the display unit 22 to display the received message. This allows users to see messages from many other patient companions and be encouraged or sympathetic to having similar problems, along with many other patient companions. , I can raise awareness to continue working hard.
Therefore, the user can effectively raise the awareness of continuous use even for the implementation of the pharmaceutical injection device 1 that must be continued every day. Also, watching other patients' messages is one of the daily pleasures. To that end, they must send messages, and as a premise, they need to use their own drug injection device 1. It becomes.

The screen 122 (g) displays the case where the confirmation result (response) from the server 3 of the user registration information is NG after starting the application and starting the connection with the server 3. At this time, for example, a message such as “authentication failed” is displayed on the display unit 22.
[1-2-2. Drug injection operation]
Next, the operation of the pharmaceutical injection device 1 according to the present embodiment will be described along the flowchart of FIG. 9 based on the configuration of FIGS. FIG. 9 is a flowchart mainly showing a basic operation of the control unit 11 of the pharmaceutical injection device 1 which is an example of a medical device.
S1101: First, the user presses the power switch 9 of the medicine injection device 1.
S1102: When the power switch 9 is pressed, the control unit 11 displays an initial screen on the screen of the display unit 34 indicating that the power of the drug injection device 1 has been turned on.

S1103: When a predetermined time (for example, 3 seconds) has elapsed from the display of the initial screen, the control unit 11 detects the presence or absence of the preparation syringe 6 based on a signal from the syringe detection switch 33 that detects the preparation syringe 6 shown in FIG. .
S1104: When the preparation syringe 6 cannot be detected by the syringe detection switch 33, the control unit 11 displays a message prompting the user to attach the preparation syringe 6 on the screen of the display unit 34.
S1105: The user attaches the preparation syringe 6 to the drug injection device 1 according to the message displayed in S1104.
S1106: When detecting the preparation syringe 6 with the needle detection switch 35, the control unit 11 detects whether or not the injection needle 8 is attached based on a signal from the needle detection switch 35.

S1107: When the attachment of the injection needle 8 cannot be detected, the control unit 11 displays a message prompting the attachment of the injection needle 8 on the screen of the display unit 34.
S1108: The user wears the injection needle 8 according to the message displayed in S1107.
S1109: When the control unit 11 detects the injection needle 8 with the needle detection switch 35, the control unit 11 next displays a message for prompting the medicine injection device 1 to be idle (bleed out) on the screen of the display unit 34. This message is, for example, “please run empty”.
S1110: In this state, the user presses the injection switch 10.
S1111: The control unit 11 causes the screen of the display unit 34 to display a message indicating that it is idle.

S1112: The piston 7 is slightly moved by the drive motor 12 by the control unit 11, and the idle driving operation is thereby executed.
S <b> 1113: The control unit 11 records information on the execution of this idle shot in the memory 18 connected to the short-range communication unit 17.
S1114: Next, the control unit 11 causes the screen of the display unit 34 to display a message prompting injection (for example, “I can inject”).
S1115: In this state, the user inserts the injection needle 8 into the human body and presses the injection switch 10.
S1116: The control unit 11 displays a message indicating that the injection is being performed on the screen of the display unit 34.

S1117: The controller 11 drives the drive motor 12 by the motor drive circuit 13 to move the piston 7 in the direction of the injection needle 8. Thereby, the formulation in the formulation syringe 6 is injected into the human body and injection is performed.
S <b> 1118: The control unit 11 records the drug injection data (for example, including that the drug injection operation has been performed and the date and time thereof) in the memory 18 connected to the short-range communication unit 17.
S1119: When the injection is completed, the control unit 11 displays a message indicating that the injection is completed on the screen of the display unit 34.
S1120: When the user presses the power switch 9 again, the control unit 11 shuts off the power.
S1121: The control unit 11 causes the display unit 34 to display a message notifying that the power is turned off, such as “See You”, and ends the operation of the pharmaceutical injection device 1.

As described above, when the drug injection is completed, the drug injection data (including the drug injection operation and the date and time) is recorded in the memory 18 connected to the short-range communication unit 17, and then the mobile communication. It is transmitted to the device 2.
[1-2-3. Receiving usage information]
Next, the connection between the mobile communication device 2 and the server 3 and the reception of the usage information of other users will be described mainly with reference to FIG. 6, FIG. 7, and FIG.
S1201: First, in the mobile communication device 2, the control unit 21 selects and activates the application program of the medical support system according to the present embodiment, and, for example, on the display unit 22 as shown in a screen 122 (a) in FIG. An initial screen (for example, “Hello”) is displayed.
S1202: Thereafter, the control unit 21 of the mobile communication device 2 transmits user registration information to the server 3 via the communication unit 20.

S 1203: The control unit 31 of the server 3 receives user registration information from the mobile communication device 2 via the communication unit 30.
S1204: After that, the control unit 31 checks the received user registration information with the user registration information held by itself for authentication.
S1205: The control unit 31 transmits the authentication result (response) obtained in S1204 to the mobile communication device 2 via the communication unit 30.
S1206: The control unit 21 of the mobile communication device 2 receives the authentication result (response) from the server 3 via the communication unit 20.
S1207: The control unit 21 determines the authentication result.
S1208: If the authentication result is NG, control unit 21 causes display unit 22 to display a message indicating authentication failure. Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds), and terminates the processing if there is no new operation or the like.

S1209: On the other hand, if the authentication result (response) is OK, the control unit 21 transmits a use information acquisition request for another user to the server 3 via the communication unit 20.
S1210: On the server 3 side, a request for acquiring usage information of another user from the mobile communication device 2 is received.
S1211: The control unit 31 of the server 3 acquires usage information of other users stored in the storage unit 32.
S1212: The control unit 31 transmits this usage information to the mobile communication device 2 via the communication unit 30.
S 1213: On the mobile communication device 2 side, usage information of other users is received from the server 3.

S1214: The control unit 31 of the mobile communication device 2 causes the display unit 22 to display usage information (plot data) of other users. Here, as usage information of other users, for example, a screen 122 (b) in FIG. 8 is a map of the country or region in which the user resides, and the position distribution of other users who have performed drug injection on the same day Is displayed.
[1-2-4. Sending drug injection data]
Next, the operation proceeds to a transmission operation of drug injection data from the drug injection device 1 to the mobile communication device 2. Mainly referring to FIG. 5, FIG. 6, and FIG.
S1301: The user selects an “injection data acquisition” button (screen 122 (b) in FIG. 8) provided on the touch panel 23 of the display unit 22 of the mobile communication device 2.

S1302: The control unit 21 of the mobile communication device 2, for example, as shown in the screen 122 (c) of FIG. 8, instructs the mobile phone 2 to approach the medicine injection device 1 (injector) (for example, “hold the injector over the injector”). ”) Is displayed on the display unit 22.
S1303: Thereafter, the user holds the mobile communication device 2 over the medicine injection device 1.
S1304: The control unit 21 activates a near field communication unit 29 (NFC IC) that performs near field communication.
S1305: Similarly, on the drug injection device 1 side, the control unit 11 also activates the short-range communication unit 17 (NFC IC) that performs short-range communication.
S1306: Next, on the mobile communication device 2 side, the control unit 21 transmits a search command to the drug injection device 1 via the short-range communication unit 29.

S 1307: On the drug injection device 1 side, the control unit 11 receives the search command transmitted from the mobile communication device 2 via the short-range communication unit 17.
S1308: The control unit 11 analyzes the received search command.
S1309: The control unit 11 transmits the analysis result (response) in S1308.
S1310: On the mobile communication device 2 side, the control unit 21 receives the response transmitted from the medicine injection device 1.
S1311: When the response is not a response from the corresponding drug injection device 1 (injector), that is, when the response is NG, the control unit 21 returns to S1306 and transmits the search command again.
S1312, On the other hand, if the response is OK, the control unit 21 transmits a reading command for reading the drug injection data from the drug injection device 1 to the drug injection device 1.

S1313: On the drug injection device 1 side, the control unit 11 receives a command for reading the drug injection data.
S1314: The control unit 11 analyzes the received read command.
S1315: The control unit 11 acquires corresponding data (in this case, drug injection data) from the memory 18.
S1316: The control unit 11 transmits the acquired medicine injection data to the mobile communication device 2.
[1-2-5. Send and receive messages]
Next, the process proceeds to message transmission / reception between the mobile communication device 2 and the server 3. Message transmission / reception will be described mainly with reference to FIG. 6, FIG. 7, and FIG.
S1401: In the mobile communication device 2, the control unit 21 receives drug injection data.

S1402: Thereafter, the control unit 21 performs a display prompting message input on the display unit 22 (for example, the screen 122 (d) in FIG. 8). Here, the user inputs, as a message, his / her current thoughts and concerns or seasonal topics in the area.
S1403: Next, the control part 21 starts the position information detection part 25 comprised by GPS.
S1404: The control unit 21 acquires the current position information of the mobile communication device 2.
S1405: The control unit 21 stops the position information detection unit 25 after acquiring the position information.
S1406: Thereafter, the control unit 21 causes the display unit 22 to display that data is being transmitted to the server 3 as shown in a screen 122 (e) of FIG.
S1407: At the same time, the control unit 21 transmits the acquired drug injection data of the drug injection device 1, the current position information, and the message input in S1402 to the server 3 via the communication unit 20. .

S1408: The control unit 31 of the server 3 receives the drug injection data, the current position information, and the input message of the drug injection device 1 transmitted from the mobile communication device 2.
S1409: The control unit 31 stores the received data in the storage unit 32 of the server 3.
S1410: Thereafter, the server 3 transmits, to the mobile communication device 2, a random message from another user with no bearer among the messages already stored in the storage unit 32. This message may be selected at random, or may be selected from messages of other users having the same user age, residence, or the like.
S <b> 1411: On the mobile communication device 2 side, the control unit 21 receives a random message transmitted from the server 3.
S1412: The received random message is displayed on the control unit 21 and the display unit 22. The user can check the message received from the other patient or the related person of the other patient with his / her portable communication device 2.

Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds), and terminates the processing if there is no new operation or the like.
[1-3. Effect etc.]
The medical support system 100 according to the present embodiment includes a medical device (medicine injection device 1) operated by a first user and a control device (a control unit of the portable communication device 2) that acquires usage information of the first user's medical device. 21), a display device (the display unit 22) controlled by the control device, and a server (server 3) that can be connected to the control device and obtains use information of the medical device of the first user. The apparatus acquires the usage information on the medical device of the second user (other user) from the server, and causes the display device to display the usage information on the medical device of the second user.
For this reason, the medical support system 100 encourages the patient and users who are related to the patient to see messages from many other patient companions. To create an environment that can In addition, users will continue to work hard together with many other colleagues to continue using drugs. Therefore, it is possible to effectively increase the awareness of continuous use for the use of a medical device that must be continued every day.

In the medical support system 100 according to the present embodiment, the usage information of the medical device includes information indicating whether the user has used the medical device within a predetermined time from the present time, and a message between the first user and the second user. including. For this reason, the user can grasp that many other colleagues are in the same situation, can create an environment in which other users can easily feel empathy, and effective awareness of continued use of medical devices is effective. Can be enhanced. Furthermore, since the message provided by the server is anonymous, information relating to personal privacy is not disclosed. Therefore, the user can interact with other users with peace of mind.
In addition, the control device causes the display device to display a screen for the first user to input a message toward the second user, and uses the first user's medical device usage information including the input message as a server. Send to. For this reason, users can see other users' random messages as part of their daily enjoyment, and for that purpose they must send messages, and the premise is that their medical devices are used. Necessary. Therefore, the consciousness of continuous use can be raised effectively.

Furthermore, the medical support system 100 further includes a position information detection unit (position information detection unit 25) that is connected to the control device and detects position information of the control device, and the control device uses the first user's medical device usage information. At the same time, the position information is transmitted to the server. Further, the control device causes the display device to display a screen showing the position information of the plurality of second users before transmitting the usage information of the first user's medical device to the server. For this reason, the user can grasp that many other colleagues are in the same situation, can create an environment in which other users can easily feel empathy, and effective awareness of continued use of medical devices is effective. Can be enhanced.
(Embodiment 2)
Hereinafter, the medical support system according to the second embodiment will be described with reference to FIGS. 13 to 19. In addition, about the structure and function similar to Embodiment 1, the same code | symbol is attached | subjected and drawing and description are abbreviate | omitted.

[2-1. Constitution]
FIG. 13 schematically shows an overall configuration of a medical support system 200 according to the second embodiment. The medical support system 200 includes a drug injection device 201 (an example of a medical device) that is a medical device, and the server 3 to which data of the drug injection device 201 is transmitted from the drug injection device 201.
The medical support system 200 is different from the first embodiment in that it does not include a mobile communication device and the drug injection device 201 and the server 3 directly transmit and receive data.
[2-1-1. Configuration of drug injection device]
As shown in FIGS. 14 and 15, the drug injection device 201 includes position information detection configured by the communication unit 220 and GPS in addition to the configuration of the drug injection device 1 according to the first embodiment shown in FIGS. 2 to 5. A unit 225 and an input unit 231.

The communication unit 220 is connected to the control unit 11 (an example of a control device) and performs communication with the server 3. The position information detection unit 225 is connected to the control unit 11 and detects the position of the drug injection device 201. The input unit 231 is an input unit such as a key, a switch, and a button (for example, a left button, a right button, and an enter button), and is operated by a user.
Moreover, since the medicine injection device 201 according to the present embodiment does not need to perform short-range communication with the mobile communication device, the short-range communication unit 17 may not be provided as in the first embodiment.
Other configurations are the same as those of the pharmaceutical injection device 1 according to the first embodiment.
[2-1-2. Server configuration]
The configuration of the server (an example of a server) according to the present embodiment is the same as that of the first embodiment (FIG. 7).

[2-2. Operation]
Hereinafter, the operation of the medical support system 200 according to the second embodiment will be described with reference to FIGS. 15 to 19.
[2-2-1. Receiving usage information]
S2101: First, as shown in FIG. 16, the user presses the power switch 9 of the medicine injection device 201.
S2102: In the medicine injection device 201, the control unit 11 selects and activates the installed application program of the medical support system 200 according to the present embodiment, and displays the display unit 34 as shown in a screen 234 (a) in FIG. An initial screen (for example, “Hello”) is displayed on (an example of a display device).

S2103: Thereafter, the control unit 11 transmits user registration information to the server 3 via the communication unit 220.
S2104: The control unit 31 of the server 3 receives the user registration information from the mobile communication device 2 via the communication unit 30.
S2105: Thereafter, the control unit 31 checks the received user registration information with the user registration information held by itself for authentication.
S2106: The control unit 31 transmits the authentication result (response) obtained in S2104 to the drug injection device 201 via the communication unit 30.
S2107: The control unit 11 receives the authentication result (response) from the server 3 via the communication unit 220.

S2108: The control unit 11 determines an authentication result.
S2109: If the authentication result is NG, the control unit 11 causes the display unit 34 to display a message indicating an authentication failure as shown in a screen 234 (f) in FIG. Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds), and terminates the processing if there is no new operation or the like.
S2110: On the other hand, if the authentication result (response) is OK, the control unit 11 transmits a use information acquisition request for another user to the server 3 via the communication unit 220.
S2111: On the server 3 side, a usage information acquisition request for another user is received from the medicine injection device 201.
S2112: The control unit 31 of the server 3 acquires the usage information of other users stored in the storage unit 32.

S2113: The control unit 31 transmits this use information to the drug injection device 201 via the communication unit 30.
S2114: On the drug injection device 201 side, usage information of other users is received from the server 3 via the communication unit 220.
S2115: The control unit 11 of the pharmaceutical injection device 201 causes the display unit 34 to display usage information (plot data) of other users. Here, as the usage information of other users, for example, as shown in the screen 234 (b) of FIG. 19, the map of the country or region in which the user resides, and the distribution of other patients who performed the drug injection on the same day is shown. Is displayed.
S2116: The user selects the “Menu” button from the administration map screen on screen 234 (b) in FIG. Thereby, the control unit 11 of the medicine injection device 1 displays a menu screen on the display unit 34, for example, as a screen 234 (c) shown in FIG.

[2-2-2. Drug injection operation]
Next, the operation proceeds to a medicine injection operation. The drug injection operation of the drug injection device 201 will be described mainly with reference to FIGS. 15 and 17.
S2201: The user selects an “injection” button from the menu screen of screen 234 (c) in FIG.
S2202: The control unit 11 of the pharmaceutical injection device 201 detects the presence or absence of the preparation syringe 6 based on a signal from the syringe detection switch 33 that detects the preparation syringe 6 (FIG. 4).
S2203: The control part 11 displays the message which urges | wears the display part 34 with the preparation syringe 6 mounting | wearing, when the preparation syringe 6 cannot be detected with the syringe detection switch 33. FIG.
S2204: The user attaches the preparation syringe 6 to the drug injection device 201 in accordance with the message displayed in S2203.

S2205: When detecting the preparation syringe 6 with the syringe detection switch 33, the control unit 11 detects whether or not the injection needle 8 (FIG. 4) is attached based on a signal from the needle detection switch 35.
S2206: When the attachment of the injection needle 8 cannot be detected, the control unit 11 causes the display unit 34 to display a message prompting the attachment of the injection needle 8.
S2207: The user wears the injection needle 8 according to the message displayed in S2206.
S2208: When the control unit 11 detects the injection needle 8 with the needle detection switch 35, the control unit 11 next displays a message for prompting the medicine injection device 1 to be idle (bleed out) on the display unit 34. This message is, for example, “please run empty”.

S2209: In this state, the user presses the injection switch 10.
S2210: The control unit 11 causes the display unit 34 to display a message indicating that it is idle.
S2211: The piston 7 is slightly moved by the drive motor 12 by the control unit 11, whereby the idle driving operation is executed.
S 2212: The control unit 11 records this idle operation data in the memory 16.
S2213: Next, the control unit 11 causes the display unit 34 to display a message prompting injection (for example, “I can inject”).
S2214: In this state, the user inserts the injection needle 8 into the body and presses the injection switch 10.

S2215: The control unit 11 causes the display unit 34 to display a message indicating that injection is in progress.
S2216: The controller 11 drives the drive motor 12 by the motor drive circuit 13 to move the piston 7 in the direction of the injection needle 8. Thereby, the formulation in the formulation syringe 6 is injected into the human body and injection is performed.
S2217: When the injection is completed, the control unit 11 causes the display unit 34 to display a message indicating that the injection is completed.
S2218: The control unit 11 records the drug injection data (for example, including that the drug injection operation has been performed and the date and time thereof) in the memory 16.
[2-2-3. Sending drug injection data]
Next, the operation proceeds to an operation for transmitting drug injection data from the drug injection device 201 to the server 3. The transmission operation of the drug injection data of the drug injection device 201 will be described mainly with reference to FIGS. 15 and 18.

S2301: The control unit 11 of the medicine injection device 201 activates the position information detection unit 225 configured by GPS.
S2302: The control unit 11 acquires the current position information of the drug injection device 201.
S2303: The control unit 11 stops the position information detection unit 225 after acquiring the position information.
S2304: Thereafter, the control unit 11 causes the display unit 34 to display that data is being transmitted to the server 3 as shown in a screen 234 (d) in FIG.
S2305: At the same time, the control unit 11 transmits the acquired drug injection data of the drug injection device 201 and the current position information to the server 3 via the communication unit 220.
S2306: The control unit 31 of the server 3 receives the drug injection data of the drug injection device 201 and the current position information transmitted from the drug injection device 201.

S2307: The control unit 31 stores the received data in the storage unit 32 of the server 3.
S2308: The control unit 11 causes the display unit 34 to display a message indicating that the transmission of the drug injection data and the current position information has been completed, as in a screen 234 (e) in FIG.
S2309: The user depresses the power switch 9 to end the operation of the medicine injection device 1.
S2310: The control unit 11 displays a message notifying that the power is turned off, such as “See You” on the display unit 34, and ends the operation of the drug injection device 1 after a predetermined time (for example, 3 seconds) has elapsed.
[2-3. Effect etc.]
In the medical support system 200 according to the present embodiment, the control device (control unit 11) of the medical device (drug injection device 201) displays the usage information on the medical device of the second user (other user) as a display device (display unit). 34), the medicine injection operation is executed.

For this reason, in this embodiment, in addition to the effects of the first embodiment, the user sees the usage information of other users every time the medical device is activated. Awareness can be raised friendly. In other words, by viewing the usage information regarding other users via the server, it will continue to work hard together with many other patient colleagues to raise awareness of continued use of drug injection. Therefore, it is possible to effectively increase the awareness of continuous use for the use of a medical device that must be continued every day.
(Embodiment 3)
Hereinafter, the medical support system according to Embodiment 3 will be described with reference to FIGS. 20 to 29.
[3-1. Constitution]
The medical support system according to the present embodiment has the same configuration as the medical support system 100 of the first embodiment. The configurations of the drug injection device 1, the portable communication device 2, and the server 3 are also the same as those in the first embodiment. Therefore, description of these configurations will be omitted, and will be described with reference to the drawings (FIGS. 1 to 7) according to the first embodiment as necessary.

[3-2. Operation]
The medical support system 100 according to the third embodiment is different from the first embodiment in that friend registration is possible by user selection among other patients.
In the first embodiment, the user was able to obtain other patient information and an anonymous message. However, in this embodiment, the user can select and register a friend in advance among other patients. it can. The user can create a usage environment of the drug injection device 1 that is more easily sympathetic by continuously acquiring the usage information of a specific friend. Therefore, the user's awareness of continuous use of the pharmaceutical injection device 1 can be improved.
Hereinafter, the operation of the medical support system 100 according to the present embodiment will be described.
[3-2-1. Screen operation]
The transition of the screen of the mobile communication device 2 according to the present embodiment will be described with reference to FIGS.

A screen 322 (a) in FIG. 20 is an initial screen when the application of the medical support system 100 is activated in the mobile communication device 2. By starting the application, communication between the mobile communication device 2 and the server 3 becomes possible as will be described later. If the authentication fails when connecting to the server 3, a screen indicating that the authentication has failed is displayed as shown in a screen 322 (c).
A screen 322 (b) is a menu screen, and displays a “data collection” button, a “friend list” button, a “friend registration” button, and a “setting” button that can be selected by the user through a touch operation.
<Friend list screen>
When the user selects the “friend list” button, the screen transitions to a screen 322 (b) -list1 in FIG. A screen 322 (b) -list1 displays a list of friends currently registered by the user. In this friend list display, for example, friends who have been injected within 24 hours retroactively or friends who have not been injected within 24 hours are displayed in an identifiable manner. For example, an asterisk is placed next to the name of a user who has made an injection within 24 hours. If there is unconfirmed information (unread information), the user name is displayed so that it can be identified. For example, the button color is changed to another color.

The user can return the screen to the screen 322 (b) by selecting the menu button.
<Friend registration screen>
As shown in FIG. 21, when the user selects the “register friend” button on the menu screen of the screen 322 (b), the screen transitions to the screen 322 (b) -entry1.
Screen 322 (b) -entry1 is a screen prompting the user to input the ID of a friend who wants to register as a friend. When the friend ID is input, the screen changes to a screen 322 (b) -entry2.
A screen 322 (b) -entry2 is a display indicating that the input ID is being searched. When the input ID is searched, the screen changes to a screen 322 (b) -entry3.

A screen 322 (b) -entry3 is a screen for confirming whether or not to register the searched friend ID. When the “Yes” button is pressed, the searched friend ID is registered and added to the friend list, and the screen transits to a screen 322 (b) -entry4, and the completion of friend registration is displayed. Then return to the menu screen.
If the “No” button is pressed, the retrieved friend ID is not registered and the screen returns to the menu screen.
<ID registration screen>
As shown in FIG. 22, when the user selects the “SET” button on the menu screen of the screen 322 (b), the screen transitions to the screen 322 (b) -set1.
The screen 322 (b) -set1 is a screen that prompts the user to input and register his / her ID. A user can become a target to be registered as a friend by another user by registering his / her ID. When the user ID is input, the screen transitions to a screen 322 (b) -set2.

The screen 322 (b) -set2 is a display indicating that it is being confirmed whether or not the input ID is duplicated with other user IDs. When it is confirmed that the input ID can be registered, the screen changes to a screen 322 (b) -set3. When the input ID overlaps with another user ID, the screen transitions to a screen 322 (b) -set6.
The screen 322 (b) -set3 notifies that the ID can be registered. Next, the screen transits to FIG. 322 (b) -set4.
A screen 322 (b) -set4 is a screen that prompts the user to input a name. When the user inputs a name, the screen transitions to a screen 322 (b) -set5 and displays the completion of ID registration. Then return to the menu screen.
Screen 322 (b) -set6 is a screen for notifying that the user's input ID overlaps with other user IDs, and then returns to screen 322 (b) -set1 to enter another user ID. Encourage you to do.

<Data collection screen>
As shown in FIG. 23, when the user selects the “data collection” button on the menu screen of the screen 322 (b), the screen transitions to the screen 322 (b) -collect1.
The screen 322 (b) -collect1 displays the portable communication device 2 on the drug injection device 1 for data transmission / reception between the short-range communication unit 17 of the drug injection device 1 (injector) and the short-range communication unit 29 of the portable communication device 2. This is a screen that prompts them to come close The user holds the portable communication device 2 over the drug injection device 1 to transmit drug injection data from the drug injection device 1 to the portable communication device 2 by short-range wireless communication.
[3-2-2. Server connection]
Next, the connection between the mobile communication device 2 and the server 3 according to the present embodiment will be described mainly with reference to FIGS. 6, 7, and 24.

S3101: First, in the mobile communication device 2, the control unit 21 selects and activates an application program of the medical support system according to the present embodiment, and causes the display unit 22 to display an initial screen (for example, “Hello”).
S <b> 3102: Thereafter, the control unit 21 of the mobile communication device 2 transmits user registration information to the server 3 via the communication unit 20.
S3103: The control unit 31 of the server 3 receives the user registration information from the mobile communication device 2 via the communication unit 30.
S3104: Thereafter, the control unit 31 checks the received user registration information with the user registration information held by itself for authentication.
S3105: The control unit 31 transmits the authentication result (response) obtained in S3104 to the mobile communication device 2 via the communication unit 30.

S3106: The control unit 21 of the mobile communication device 2 receives the authentication result (response) from the server 3 via the communication unit 20.
S3107: The control unit 21 determines the authentication result.
S3108: If the authentication result is NG, the control unit 21 displays a message indicating authentication failure on the screen of the display unit 22. Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds), and terminates the processing if there is no new operation or the like.
S3109: On the other hand, if the authentication result (response) is OK, the control unit 21 causes the display unit 22 to display the menu screen of the screen 322 (b) of FIGS.
[3-2-3. Friend list display process]
Next, a friend list display process performed by the mobile communication device 2 according to the present embodiment will be described mainly with reference to FIGS. 6, 7, 20, and 25.

S3201: First, the user selects a “friend list” button on the menu screen (FIG. 20) of the screen 322 (b) displayed on the display unit 22 of the mobile communication device 2.
S3202: The control unit 21 of the mobile communication device 2 transmits an acquisition request for use information of the friend selected in S3201 to the server 3 via the communication unit 20.
S3203: The control unit 31 of the server 3 receives a request from the mobile communication device 2 via the communication unit 30.
S3204: The control part 31 acquires the usage information corresponding to applicable friend ID from the memory | storage part 32 according to the received request | requirement. The storage unit 32 stores friend usage information (such as the operation of the drug injection device and the date and time) acquired from other users.

S3205: The control unit 31 transmits the friend usage information obtained in S3204 to the mobile communication device 2 via the communication unit 30.
S3206: The control unit 21 of the mobile communication device 2 receives the friend usage information from the server 3 via the communication unit 20.
S3207: Control part 21 displays received friend use information. In this friend list display, as described above, for example, a friend who has made an injection within 24 hours and a friend who has not made an injection within 24 hours can be identified, or there is unconfirmed information (unread information). In this case, the user ID is displayed so that it can be identified.
S3208: The control unit 21 causes the display unit 22 to display the menu screen of the screen 322 (b).

[3-2-4. Friend registration process]
Next, a friend registration process performed by the mobile communication device 2 according to the present embodiment will be described mainly with reference to FIGS. 6, 7, 21, and 26. Here, the ID of a friend that the user wants to add to the friend list is added.
S3301: First, the user selects the “friend registration” button on the menu screen (FIG. 21) of the screen 322 (b) displayed on the display unit 22 of the mobile communication device 2.
S3302: The control unit 21 of the mobile communication device 2 displays the screen 322 (b) -entry1 of FIG. 21 on the display unit 22 and prompts the user to input the ID of a friend who wants to register as a friend.
S3303: The user inputs a friend's ID.
S3304: The control unit 21 displays the screen 322 (b) -entry2 of FIG. 21 on the display unit 22 and displays that the input ID is being searched.

S3305: The control unit 21 transmits the input friend ID and the search request to the server 3 via the communication unit 20.
S3306: The control unit 31 of the server 3 receives a request from the mobile communication device 2 via the communication unit 30.
S3307: The control unit 31 searches the storage unit 32 for a corresponding friend ID in response to the received request.
S3308: The control unit 31 transmits the search result of S3307 to the mobile communication device 2 via the communication unit 30.
S3309: The control unit 21 of the mobile communication device 2 receives the friend ID search result from the server 3 via the communication unit 20.

S3310: The control unit 21 displays the screen 322 (b) -entry3 of FIG. 21 on the display unit 22, and performs a display for confirming whether or not to register the searched friend ID.
S3311: If the user has selected to perform friend registration in S3310, the process proceeds to S3312.
S3312: The control unit 21 stores the searched friend ID in the memory 27.
S3313: The control unit 21 displays the screen 322 (b) -entry4 of FIG. 21 on the display unit 22 and displays the completion of friend registration.
Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds) to display the menu screen of the screen 322 (b) on the display unit 22.
[3-2-5. ID registration process]
Next, an ID registration process performed by the mobile communication device 2 according to the present embodiment will be described mainly with reference to FIGS. 6, 7, 22, and 27. Here, a process when a user registers his / her ID so as to be a friend registration target of another user will be described.

S3400: First, the user selects the “Setting” button on the menu screen (FIG. 22) of the screen 322 (b) displayed on the display unit 22 of the mobile communication device 2.
S3401: The control unit 21 of the mobile communication device 2 displays the screen 322 (b) -set1 of FIG. 22 on the display unit 22, and prompts the user to input an ID desired to be registered.
S3402: The user inputs an ID for which registration is desired.
S3403: The control unit 21 displays the screen 322 (b) -set2 in FIG. 22 on the display unit 22, and displays a display indicating that the input ID is being checked for duplication with other user IDs. Do.
S3404: The control unit 21 transmits the ID input in S3402 and the search request to the server 3 via the communication unit 20.

S3405: The control unit 31 of the server 3 receives a request from the mobile communication device 2 via the communication unit 30.
S3406: In response to the received request, the control unit 31 searches for the presence or absence of the same ID as the corresponding input ID from the storage unit 32. At this time, the presence / absence of a similar ID (one character difference or the like) may be searched.
S3407: The control unit 31 transmits the search result of S3406 to the mobile communication device 2 via the communication unit 30.
S3408: The control unit 21 of the mobile communication device 2 receives the ID search result from the server 3 via the communication unit 20.
S3409: Based on the received search result, the control unit 21 determines whether or not the input ID overlaps with an existing registration ID.

S3410: If there is an ID overlap, the control unit 21 displays the screen 322 (b) -set6 of FIG. 22 on the display unit 22 and displays a warning that the input ID has already been used. , The process returns to S3401.
S3411: When there is no duplication of ID, the control unit 21 displays the screen 322 (b) -set3 of FIG. 22 on the display unit 22, and displays that the input ID can be registered.
S3412: After a predetermined time (for example, 3 seconds) has elapsed, the control unit 21 displays the screen 322 (b) -set4 in FIG. 22 on the display unit 22 and prompts the user to input a name.
S3413: The user inputs his name.
S3414: The control unit 21 stores the input ID and name in the memory 27 and the like, and transmits them to the server 3 via the communication unit 20.

S3415: The control unit 31 of the server 3 receives the ID and name from the mobile communication device 2 via the communication unit 30.
S3416: The control unit 31 stores the received ID and name in the storage unit 32.
S3417: On the other hand, the control unit 21 of the mobile communication device 2 displays the screen 322 (b) -set5 of FIG. 22 on the display unit 22, and displays that the input ID is registered.
Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds) to display the menu screen of the screen 322 (b) on the display unit 22.
[3-2-6. Data collection process]
Next, data collection processing by the mobile communication device 2 according to the present embodiment will be described mainly with reference to FIGS. 6, 7, 23, 28, and 29. First, transfer of drug injection data from the drug injection device 1 shown in FIG. 28 to the mobile communication device 2 will be described. In addition, the power supply of the medicine injection device 1 is assumed to be ON.

S3501: First, the user selects a “data collection” button on the menu screen (FIG. 23) of the screen 322 (b) displayed on the display unit 22 of the mobile communication device 2.
S3502: The control unit 21 of the mobile communication device 2 displays the screen 322 (b) -collect1 of FIG. 22 on the display unit 22 and prompts the mobile communication device 2 to approach the mobile medicine injection device 1.
S3503: Thereafter, the user holds the mobile communication device 2 over the medicine injection device 1.
S3504: The control unit 21 activates the near field communication unit 29 (NFC IC) that performs near field communication.
S3505: Similarly, on the drug injection device 1 side, the control unit 11 also activates the short-range communication unit 17 (NFC IC) that performs short-range communication.
S3506: Next, on the mobile communication device 2 side, the control unit 21 transmits a search command to the drug injection device 1 via the short-range communication unit 29.

S3507: On the drug injection device 1 side, the control unit 11 receives the search command transmitted from the mobile communication device 2 via the short-range communication unit 17.
S3508: The control unit 11 analyzes the received search command.
S3509: The control unit 11 transmits the analysis result (response) of S3508.
S3510: On the mobile communication device 2 side, the control unit 21 receives a response transmitted from the medicine injection device 1.
S3511: When the response is not a response from the corresponding drug injection device 1 (injector), that is, when the response is NG, the control unit 21 returns to S3506 and transmits the search command again.
S3512: On the other hand, if the response is OK, the control unit 21 transmits a reading command for reading the drug injection data from the drug injection device 1 to the drug injection device 1.

S3513: On the drug injection device 1 side, the control unit 11 receives a command for reading the drug injection data.
S3514: The control unit 11 analyzes the received read command.
S3515: The control unit 11 acquires corresponding data (in this case, drug injection data) from the memory 18.
S3516: The control unit 11 transmits the acquired medicine injection data to the mobile communication device 2.
Next, the process proceeds to transmission of drug injection data from the mobile communication device 2 to the server 3. With reference to FIG. 29, transmission of the medicine injection data will be described.
S3601: In mobile communication device 2, control unit 21 receives drug injection data.
S3602: Next, the control unit 21 activates the position information detection unit 25 (GPS).

S3603: The control unit 21 acquires the current position information of the mobile communication device 2.
S3604: Control part 21 stops position information detecting part 25 after acquiring the position information.
S3605: Thereafter, the control unit 21 displays the screen 322 (b) -collect2 of FIG. 23 on the display unit 22 to indicate that data is being transferred.
S3606: At the same time, the control unit 21 transmits the acquired drug injection data of the drug injection device 1 and the current position information to the server 3 via the communication unit 20.
S3607: The control unit 31 of the server 3 receives the drug injection data and the current position information of the drug injection device 1 transmitted from the mobile communication device 2.
S3608: The control unit 31 stores the received data in the storage unit 32 of the server 3.
S3609: The control unit 31 transmits a response to the mobile communication device 2.

S3610: On the mobile communication device 2 side, the control unit 21 receives the response transmitted from the server 3.
S3611: The control unit 21 displays the screen 322 (b) -collect3 of FIG. 23 on the display unit 22 to indicate that the data transfer is completed.
Thereafter, the control unit 21 waits for a predetermined time (for example, 3 seconds) to display the menu screen of the screen 322 (b) on the display unit 22.
In addition, since the medicine injection operation according to the present embodiment is the same as that of Embodiment 1 (FIG. 9), description thereof is omitted.
[3-3. Modified example]
In the third embodiment, a message may be created or received for another user who is registered as a friend.

In this case, the friend use information received from the server 3 includes the message of the friend, and the control unit 21 of the mobile communication device 2 receives the message (S3206 in FIG. 25). Then, when the user selects a button of a desired user ID from the screen 322 (b) -list1 in FIG. 20 (S3207), the message of the other user may be displayed. The control unit 21 may display a message input screen on the display unit 22 so that the user himself / herself inputs a message for the friend and transmits the message to the server 3. The control part 31 of the server 3 memorize | stores this message in the memory | storage part 32 as friend use information, and the user of the friend can receive a message similarly using a friend list function.
[3-4. Effect etc.]
In the medical support system 100 according to the present embodiment, the control device (the control unit 21 of the mobile communication device 2) is a medical device (drug injection device 1) of a user having a specific ID among the second users (other users). ) Usage information is acquired from the server (server 3) and displayed on the display device (display unit 22 of the portable communication device), and the usage information on the medical device of the user having the specific ID is within a predetermined time from the present time. Information indicating whether a user having the specific ID has used a medical device is included.

For this reason, in this embodiment, in addition to the effects of the first embodiment and the like, it is possible to acquire the usage information of the user who made the friend registration from the users of the same circumstances, so for example, using SNS Create an environment where you can encourage each other and sympathize with friends who have the same problems, and continue to work hard to stimulate users' desire to use medical devices. Therefore, it is possible to effectively increase the awareness of continuous use for the use of a medical device that must be continued every day.
Further, the display device displays a menu screen, and the menu screen includes at least a first selection unit (“data collection button”) for transmitting medical device usage information of the first user to the server, A second selection unit (a “friend list” button) for acquiring medical device usage information of the second user from the server is included. Therefore, the user can see the usage information of other users as one of daily pleasures, and can effectively raise the awareness of continuous use.

(Other embodiments)
As described above, Embodiments 1 to 3 have been described as examples of the technology disclosed in the present application. However, the technology in the present disclosure is not limited to this, and can also be applied to embodiments in which changes, replacements, additions, omissions, and the like are appropriately performed.
Hereinafter, other embodiments will be exemplified.
[1]
It is possible to combine the functions described in the first to third embodiments to form a new embodiment.
For example, in the third embodiment, after selecting the “data collection” button from the menu screen 322 (b) (FIG. 23) of the display unit 22 of the mobile communication device 2, as shown in FIG. A screen 122 (b) for displaying a map of the country or region where the person resides is displayed, and the screen 122 (c) is changed to 122 (f). Thereby, the mobile communication device 2 may receive a random message of another user (who is not registered as a friend) or may create a random message for another user.

In addition, the function of the control unit 21 of the mobile communication device 2 according to the first embodiment or the third embodiment is provided in the control unit 11 of the drug injection device 1 according to the second embodiment, and the first embodiment or the first embodiment. The operation of the medical support system 100 according to 3 may be executed.
[2]
The execution order of the operation processing in each of the above embodiments is not necessarily limited to the description of the above embodiment, and the execution order can be changed without departing from the gist of the invention.
[3]
The present invention is not limited to being realized as the medical support system in the above-described embodiment, and is also realized as a medical support method or medical support program executed by the control unit of the medicine injection device 1 (201) or the portable communication device 2. Is possible.

The medical support system according to the present disclosure can be used as a medical support system using a drug injection device that injects a drug such as insulin or growth hormone.

DESCRIPTION OF SYMBOLS 1 Drug injection device 2 Portable communication apparatus 3 Server 4 Main body case 5 Lid 6 Preparation syringe 7 Piston 8 Injection needle 9 Power switch 10 Injection switch 11 Control part 12 Drive motor 13 Motor drive circuit 14 Current detection circuit 15 Encoder 16 Memory 17 Short distance Communication unit 18 Memory 19 Battery 20 Communication unit 21 Control unit 22 Display unit 23 Touch panel 24 Power switch 25 Position information detection unit 26 Sounder 27 Memory 28 Battery 29 Short-range communication unit 30 Communication unit 31 Control unit 32 Storage unit 33 Syringe detection switch 34 Display unit 35 Needle detection switch 100 Medical support system 122, 234, 322 Screen 200 Medical support system 201 Drug injection device 220 Communication unit 225 Position information detection unit 231 Input unit

Claims (15)

A medical device operated by a first user,
A control device for acquiring usage information of the medical device of the first user;
A display device that is controlled by the control device; and a server that is connectable to the control device and acquires usage information of the medical device of the first user;
With
The control device acquires the usage information of the second user's medical device from the server, and causes the display device to display the usage information of the second user's medical device.
Medical support system. The use information of the medical device includes information indicating whether the user has used the medical device within a predetermined time from the present time, and a message between the first user and the second user.
The medical support system according to claim 1. The control device causes the display device to display a screen for the first user to input a message toward the second user,
Transmitting usage information of the first user's medical device including the input message to the server;
The medical support system according to claim 2. The medical device is a drug injection device.
The medical assistance system in any one of Claim 1 to 3. A position information detector connected to the control device and detecting position information of the control device;
The control device transmits the position information to the server together with usage information of the medical device of the first user.
The medical assistance system in any one of Claim 1 to 4. The control device displays a screen showing position information of a plurality of second users on the display device before transmitting usage information of the medical device of the first user to the server.
The medical support system according to claim 1. A mobile communication device,
The portable communication device includes the control device and the display device,
The medical assistance system in any one of Claim 1 to 6. The controller is
The usage information of the medical device of the first user is transmitted to the server, and the usage information of the medical device of the second user is acquired from the server,
Displaying usage information of the second user's medical device on the display device;
The medical support system according to claim 7. The medical device includes the control device and the display device,
The control device executes a medicine injection operation.
The medical assistance system in any one of Claim 1 to 6. The control device displays the usage information of the medical device of the second user on the display device, and then executes the medicine injection operation.
The medical support system according to claim 9. The control device acquires medical device usage information of a user having a specific ID among the second users from the server, and causes the display device to display the usage information.
The usage information of the medical device of the user having the specific ID includes information indicating whether the user having the specific ID has used the medical device within a predetermined time from the present time.
The medical assistance system in any one of Claim 1 to 10. The control device accepts registration of a specific ID of the first user and sends it to the server;
The medical support system according to claim 11. The display device displays a menu screen,
The menu screen obtains at least a first selection unit for transmitting medical device usage information of the first user to the server and usage information of the second user medical device from the server. Including a second selector for,
The medical assistance system in any one of Claims 1-12. A medical device operated by a first user, a control device for acquiring usage information of the first user's medical device, a display device controlled by the control device, and the control device are connectable to the control device. The medical support method using the server which acquires the usage information of the medical device of 1 user,
Using the control device, the second user's medical device usage information is acquired from the server,
Displaying usage information of the second user's medical device on the display device;
Medical support method. A medical device operated by a first user, a control device for acquiring usage information of the first user's medical device, a display device controlled by the control device, and the control device are connectable to the control device. A medical support program executed by a server that acquires usage information of a medical device of one user,
Using the control device, the second user's medical device usage information is acquired from the server,
Displaying usage information of the second user's medical device on the display device;
Medical support program.

Images