JP2015060509A - Medication management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for allowing a user to make simple, autonomous medication management.SOLUTION: A medication management system 2 described in the present specification is a medication management system for rare disease medical products. The medication management system 2 includes: a management device 60; and a user terminal 10 communicable with the management system 60. The user terminal 10 includes: an operation unit 12 that enable a user to input at least medication history information on an appointed day indicating whether the user took a medical product on the appointed day; and a control unit 16 that transmits the input medication history information on the appointed day to the management device 60 in response to the input medication history information on the appointed day. Upon acquisition of the medication history information on the appointed day from the user terminal 10, a CPU 62 of the management device 60 stores the acquired medication history information on the appointed day in a memory 64, generates calendar data displaying a list of user's medication statuses on the basis of medication history information on one or more days stored in the memory 64, and transmits the generated calendar data to the user terminal 10.

Description

  The technology disclosed in the present specification relates to a medication management system.

  2. Description of the Related Art A medication management system that manages what a user takes is known. For example, the medication management system disclosed in Patent Literature 1 includes a management device and a terminal device for a user that can communicate with the management device. In the management device, a scheduled time at which the user should complete the medication is registered. When the administration device does not receive a medication completion report from the terminal device within the first predetermined period after the scheduled time elapses, the management device transmits a notification instruction to notify the user to the terminal device. The terminal device performs a notification operation according to the notification instruction. When the management device does not receive a medication completion report from the terminal device within a second predetermined period longer than the first predetermined period after the scheduled time elapses, the management device transmits a notification to the administrator who manages the user's medication. .

JP 2009-163534 A

  According to the technique of Patent Document 1, the user needs to register the scheduled time of taking medicine in the management device in advance. However, it is troublesome for the user to register the scheduled medication time. In particular, rare diseases (for example, diseases in which the number of patients is 1% or less of the national population) are often refractory, and medications (medicines) used for the treatment are often taken for a long time. For this reason, even if it is going to perform medication management using the technique of patent document 1, it is difficult for a user to utilize for a long period of time. Moreover, according to the technique of patent document 1, since a medication is promoted by the notification operation of the terminal device, etc., the user's consciousness of managing his / her medication status is reduced. As described above, since the period for taking medicine for rare diseases is long, it is difficult to continue taking medicine unless the user voluntarily manages his / her own medication situation.

  In the present specification, a technique is provided in which a user can easily perform independent medication management.

  The medication management system disclosed in this specification is a medication management system for orphan drugs used for the treatment of rare diseases (for example, diseases in which the number of patients is 1% or less of the national population). The medication management system includes a management device and a user terminal that can communicate with the management device. The user terminal is capable of inputting at least medication information on the day indicating whether or not the user has taken medicine on the day, and when the medication information on the day is entered, the medication information entered on the day Transmitting means for transmitting to the management device. When the management device acquires the medication information for the current day from the user terminal, the storage control means for storing the acquired medication information for the day in the memory, and the medication information for one day or more stored in the memory, the user Generating means for generating first output data related to the medication status of the patient. The user terminal can access the first output data.

  According to the medication management system described above, the user inputs his / her medication information to the user terminal, and thereafter accesses the first output data using the user terminal, thereby grasping his / her medication status. can do. Since the user only has to input medication information, it is not necessary to register in advance the scheduled time for taking the medication as in the conventional system. Further, unlike the conventional system, the user is not prompted to take medication by the notification operation of the terminal device, so the user must voluntarily take the medication. Therefore, according to the above medication management system, the user can perform independent medication management over a long period of time more easily than in the past.

  Here, the term “orphan drug” can be restated as, for example, a drug used for the treatment of a disease whose target patient number is less than 50,000 in Japan based on the Pharmaceutical Affairs Law. The “first output data related to the user's medication status” is generated, for example, with medication history information that records whether or not the user has taken medication, body condition information that records the user's physical status, and medication. In other words, the information includes at least one of the side effect information in which the content of the side effect is recorded.

The figure which shows typically the structure of the medication management system of an Example. The sequence diagram in the case of changing the medication basic information from the main screen is shown. An example of the main screen is shown. The example of a medication basic information change screen is shown. The sequence diagram in the case of inputting medication history information from the main screen is shown. The example of a medication information input screen is shown. The example of a general side effect screen is shown. The example of a side effect input screen is shown. An example of a body measurement value input screen is shown. The sequence diagram in the case of inputting physical condition information from the main screen is shown. The sequence diagram in the case of shifting from the main screen to the medication calendar screen is shown. An example of a medication calendar screen is shown. The sequence diagram in the case of changing the profile from the main screen is shown. The sequence diagram in the case of shifting from the main screen to the correlation diagram screen is shown. An example of a correlation diagram screen is shown. The sequence diagram in the case of shifting from the main screen to the scheduled visit date input is shown. The sequence diagram when shifting from the list screen to the individual screen is shown. An example of the list screen is shown. An example of an individual screen is shown.

  The main features of the embodiments described below are listed. In addition, the technical elements shown below are independent technical elements and exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. .

(Characteristic 1) The input means further allows the user to input medication information on the previous day indicating whether he / she has taken the medicine one day before the day, while the user himself / herself is more than two days before the day. It may not be possible to input medication information two days or more before indicating whether or not the medication has been taken. When the medication information for the previous day is input, the transmission unit may transmit the input medication information for the previous day to the management device. When the storage control unit acquires the medication information for the previous day from the user terminal, the storage control unit may store the acquired medication information for the previous day in the memory.

  The previous day's medication information has a high possibility that the user has accurately memorized whether or not the medicine has been taken, so the content is likely to be accurate. On the other hand, the medication information for two days or more may be ambiguous in the user's memory and may be inaccurate. According to said structure, even if it is a case where a user forgets the input of the medication information on the previous day, the user can input the medication information on the previous day with the high possibility that the content is accurate. On the other hand, the user cannot input medication information two or more days before that the content may be inaccurate. Therefore, the accuracy of the medication information stored in the memory of the management device can be ensured. That is, according to the above configuration, the medication information of the previous day forgotten to be input can be retroactively stored in the memory, and the accuracy of the medication information in the memory of the management device can be ensured.

(Feature 2) The storage control means may not be able to change the content of the medication information once stored in the memory.

  According to this configuration, the contents of the medication information cannot be modified after the user or other person once stored in the memory. The accuracy of medication information in the memory of the management device can be ensured.

(Characteristic 3) The input means may further allow the user to input state information on the day related to his / her physical state on the day. When the status information of the current day is input, the transmission unit may transmit the input status information of the current date to the management device. When the storage control means acquires the status information of the current day from the user terminal, the storage control means may store the acquired status information of the current date in the memory. The generation means may generate first output data based on medication information for one day or more and state information for one day or more stored in the memory.

  According to this structure, the user can access the 1st output data produced | generated based on the medication information for 1 day or more and the status information for 1 day or more using a user terminal. By viewing the first output data, the user can grasp his / her physical condition in addition to his / her medication status. Therefore, the user can grasp the relationship between the medication status and the physical condition. The user can manage his / her medication situation more appropriately. “State information” includes vital information related to the user's physical condition and side effect information related to side effects associated with medication.

(Feature 4) The management apparatus may further include a notification unit. The input means may further allow the user to input schedule date information indicating his / her next scheduled visit date. When the scheduled date information is input, the transmission unit may transmit the input scheduled date information to the management device. When the storage control unit acquires the scheduled date information from the user terminal, the storage control unit may store the acquired scheduled date information in the memory. The notification means may transmit notification information for notifying the user's next scheduled visit date to the user terminal before the scheduled date indicated by the scheduled date information stored in the memory.

  According to this configuration, the user can remember the next scheduled visit date when the user terminal receives the notification information. Occurrence of a situation where the user forgets the scheduled hospital visit date can be suppressed.

(Feature 5) The medication management system may further include an external institution terminal that is communicable with the management apparatus and is a terminal different from the user terminal. The generation means may further generate second output data related to the user's medication status based on medication information for one day or more stored in the memory. The second output data is data different from the first output data, and is data that can be accessed by the external institution terminal and does not include the user's personal information.

  The above external organization terminals include terminals used by various medical drug related organizations such as medical institutions and drug development institutions. According to this configuration, the external organization can grasp the user's medication status by accessing the second output data using the external organization terminal, and can use it for analysis or the like. Since the second output data does not include the user's personal information, the user's personal information is not leaked. The “personal information” may be paraphrased as information that can identify the user. The “second output data related to the user's medication status” includes medication history information that records whether or not the user has taken medication, physical status information that records the user's physical condition, and details of side effects that have occurred with medication. Is information including at least one of the side effect information recorded.

(Configuration of medication management system 2; FIG. 1)
The medication management system 2 shown in FIG. 1 is a system for managing the medication status of a user (patient), and in particular, is a system for managing the medication status of a user who is taking orphan drug. As a user whose medication status is managed by the medication management system 2, a patient with a rare disease is scheduled. Here, the “orphan drug” includes a drug used for treating a disease (rare disease) whose number of patients is 1% or less of the national population. In addition, based on the Pharmaceutical Affairs Law, it can be paraphrased as a drug used for the treatment of a disease whose target patient number is less than 50,000 in Japan. In general, rare diseases are often refractory, and medicines used for the treatment are often taken for a long time. The medication management system 2 is a system for a patient who takes such an orphan drug to perform his / her medication management easily and voluntarily.

  The medication management system 2 includes user terminals 10 and 20, a medical institution terminal 30, a manufacturer terminal 50, and a management device 60. The user terminal 10, the medical institution terminal 30, and the manufacturer terminal 50 can communicate with the management device 60 via the Internet (not shown).

(User terminals 10 and 20)
The user terminal 10 is a terminal device possessed by a user (that is, a patient). The user can independently manage his / her medication status by accessing the management device 60 using the user terminal 10 and performing various processes. In this embodiment, the user terminal 10 is a portable terminal such as a mobile phone (for example, a smartphone), a PDA, a notebook PC, a tablet PC, a portable music playback device, a portable video playback device, and the like. In a modification, the user terminal 10 may be a stationary terminal such as a desktop PC, for example.

  The user terminal 10 includes an operation unit 12, a display unit 14, and a control unit 16. The operation unit 12 includes a plurality of keys. The user can input various instructions to the user terminal 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. In the modified example, the user terminal 10 may include a touch panel in which the operation unit 12 and the display unit 14 are integrally configured. The control unit 16 includes a CPU and a memory (not shown). The CPU of the control unit 16 executes various processes according to programs stored in the memory. Below, the process which CPU of the control part 16 performs according to the program stored in memory may be demonstrated as a process which the user terminal 10 performs. In this example, the user ID for identifying the user of the user terminal 10 is “P1”.

  The user terminal 20 has the same configuration as the user terminal 10. The user terminal 20 is possessed by a user different from the user of the user terminal 10 (user ID “P1”). In this example, the user ID for identifying the user of the user terminal 20 is “P2”.

  Although only the user terminals 10 and 20 are illustrated in FIG. 1, the medication management system 2 is not limited to the user terminals 10 and 20 but may be one or more other possessed by other users (that is, patients). User terminal (not shown).

(Medical institution terminal 30)
The medical institution terminal 30 is, for example, a terminal device installed in a medical institution such as a hospital to which a user visits. A user (for example, a doctor) of the medical institution terminal 30 can grasp the medication status of each user by accessing the management apparatus 60 using the medical institution terminal 30 and performing various processes. In FIG. 1, only the medical institution terminal 30 is illustrated, but the medication management system 2 is not limited to the medical institution terminal 30, but one or more other medical institution terminals ( (Not shown). In this embodiment, the medical institution terminal 30 is a stationary terminal such as a desktop PC.

  The medical institution terminal 30 also includes an operation unit 32, a display unit 34, and a control unit 36. The operation unit 32 includes a plurality of keys. A user of the medical institution terminal 30 can input various instructions to the medical institution terminal 30 by operating the operation unit 32. The display unit 34 is a display for displaying various information. The control unit 36 includes a CPU and a memory (not shown). The CPU of the control unit 36 executes various processes in accordance with programs stored in the memory. Below, the process which CPU of the control part 36 performs according to the program stored in memory may be demonstrated as a process which the medical institution terminal 30 performs. In this example, the medical institution ID for identifying the medical institution in which the medical institution terminal 30 is installed is “H1”.

(Manufacturer terminal 50)
The maker terminal 50 is, for example, a terminal device installed in a manufacturer of a rare disease drug that a user takes. A user of the maker terminal 50 (for example, an employee of the manufacturer) can access the management device 60 using the maker terminal 50 and perform various processes to grasp the medication status of each user. . Although only the manufacturer terminal 50 is illustrated in FIG. 1, the medication management system 2 has one or more other manufacturer terminals (not shown) installed in other manufacturers in addition to the manufacturer terminal 50. doing. In the present embodiment, the manufacturer terminal 50 is a stationary terminal such as a desktop PC. The manufacturer terminal 50 has the same configuration as the medical institution terminal 30 described above. In this example, the manufacturer ID for identifying the manufacturer in which the manufacturer terminal 50 is installed is “M1”.

(Management device 60)
The management device 60 is a server installed by the provider of the medication management system 2. The management device 60 includes a CPU 62 and a memory 64. The CPU 62 executes various processes according to the program stored in the memory 64. Hereinafter, in the present specification, processing executed by the CPU 62 of the management device 60 according to the system program 68 stored in the memory 64 may be described as processing executed by the management device 60. The memory 64 stores a system program 68, user data 70 and 80, medical institution data 90, and manufacturer data 95. The system program 68 is a computer program for providing the system of this embodiment, and includes various system data. The user data 70 and 80 are data indicating the medication situation for each user. More specifically, the user data 70 and 80 are data indicating the medication status for each user ID (“P1”, “P2”, etc.).

  User data 70 includes ID 71, basic information 72, medication history information 74, side effect information 76, and body condition information 78. ID 71 indicates an ID (“P1”) registered by the user of the user terminal 10. That is, the user data 70 is data indicating the medication status of the user of the user terminal 10. The basic information 72 includes basic information such as the user's name, occupation, contact information (address, telephone number, e-mail address), date of birth, physical data, and type of medicine to be taken. The medication history information 74 includes information indicating whether the user has taken medication for each date. The side effect information 76 includes information indicating a side effect that has occurred in the user's body when the user takes the medicine for each date. The physical condition information 78 includes information indicating the physical condition (for example, weight, body temperature, blood pressure, pulse rate, etc.) of the user for each date.

  Similarly to the user data 70, the user data 80 also includes an ID 81 (“P2”), basic information 82, medication history information 84, side effect information 86, and physical condition information 88. That is, the user data 80 is data indicating the medication status of the user (user ID “P2”).

  The medical institution data 90 is data indicating basic information (password, contact information, etc.) for each medical institution ID (such as “H1”). Similarly, the manufacturer data 95 is data indicating basic information (password, contact information, etc.) for each manufacturer ID (such as “M1”).

  As shown in FIG. 1, the management device 60 transmits system data to the user terminal 10 according to a system program 68. The user terminal 10 displays various screens on the display unit 14 according to the received system data. The user terminal 10 transmits information indicating a selection result or an input result (that is, an operation result) input by the user via the operation unit 12 to the management device 60. The management device 60 transmits system data corresponding to the received operation result to the user terminal 10. In the system of the present embodiment, the management device 60 and the user terminal 10 repeatedly execute the transmission and reception of the operation result and the transmission and reception of the system data as described above. Although not shown in FIG. 1, the management device 60 and the user terminal 20 also repeatedly execute transmission and reception of operation results and transmission and reception of system data as described above.

  Similarly, as illustrated in FIG. 1, the management device 60 transmits system data to the medical institution terminal 30 according to the system program 68. The medical institution terminal 30 displays various screens on the display unit 34 according to the received system data. The medical institution terminal 30 transmits information indicating a selection result or an input result (that is, an operation result) input by the user via the operation unit 32 to the management device 60. The management device 60 transmits system data corresponding to the received operation result to the medical institution terminal 30. In the system of the present embodiment, the management device 60 and the medical institution terminal 30 also repeatedly execute the transmission and reception of operations and the transmission and reception of system data as described above. Although not shown in FIG. 1, the management device 60 and the manufacturer terminal 50 also repeatedly execute the transmission and reception of operation results and the transmission and reception of system data as described above.

(Example of operating this user system by operating the user terminal 10; FIGS. 2 to 16)
Next, a case where the user of the user terminal 10 operates the user terminal 10 to use this system will be described. When the user of the user terminal 10 operates the user terminal 10 to use this system, the user needs to perform user registration in advance. Specifically, first, the user terminal 10 accesses the management device 60 in accordance with a user operation. At this time, the user terminal 10 accesses the management apparatus 60 using the URL of the user web page provided by the management apparatus 60 as a connection destination. The management device 60 transmits predetermined new user registration screen data to the user terminal 10. The user terminal 10 displays a new user registration screen (not shown) on the display unit 14 according to the new user registration screen data. The user operates the operation unit 12 and inputs his / her own user ID (“P1”), login password, name, contact information, occupation, date of birth, name of medicine to be taken, and the like. The user can select a desired user ID and password. The user terminal 10 transmits the input basic information to the management device 60. When receiving the basic information, the management device 60 stores the received basic information in the memory 64. As a result, the user data 70 corresponding to the ID “P1” is generated in the memory 64, and the user registration is completed. The user data 70 includes the received basic information 72. When the user who has been registered subsequently accesses the management device 60, he or she uses the system provided by the management device 60 by performing predetermined authentication (ie, login) using the registered user ID and password. can do.

(When shifting from the main screen to changing medication basic information; Figs. 2 to 4)
As shown in FIG. 2, when the user terminal 10 accesses the management device 60 and executes predetermined authentication by the operation of the user (ID “P1”), provision of the system for the user is started. First, the management device 60 reads the user data 70 including the user ID “P1” from the memory 64, generates main screen data, and transmits it to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 shown in FIG.

(Main screen; Fig. 3)
The main screen 100 will be described with reference to FIG. The main screen 100 is also called a “menu page” in the present system. The main screen 100 is a basic screen that is displayed as needed during the provision of the system. The main screen 100 includes a medication basic information change link 102, a medication information input link 104, a body measurement value input link 106, a medication calendar link 108, a profile change link 110, a correlation diagram link 112, and a scheduled visit date input link 114. Is provided. The main screen 100 is also provided with a logout button 116.

  The medication basic information change link 102 is a link for changing a medicine registered as a medicine taken by the user (hereinafter referred to as “registered medicine”). The medication information input link 104 is a link for inputting medication history information indicating whether or not the user has taken a registered medicine on the current day or the previous day. The body measurement value input link 106 is a link for the user to input physical condition information (weight, body temperature, blood pressure, pulse rate, etc.) related to his / her physical condition on that day. The physical condition information is also called “vital information” in the system. The medication calendar link 108 is a link for displaying a medication calendar screen (see FIG. 12) that displays a list of medication histories of users every month. The profile change link 110 is a link for the user to change basic information (name, contact information, occupation, etc.) of the user stored in the memory 64 in advance. The correlation diagram link 112 is a link for displaying a correlation diagram screen (see FIG. 15) showing the correlation between the user's medication history and the body condition information. The scheduled visit date input link 114 is a link for the user to input scheduled date information indicating his / her next scheduled visit date. The logout button 116 is a button for logging out.

  As shown in FIG. 2, when the medication basic information change link 102 is selected by a user operation while the main screen 100 is displayed, the user terminal 10 indicates the selection result (medication basic information change). Information is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 transmits the medication basic information change screen data to the user terminal 10. Upon receiving the medication basic information change screen data, the user terminal 10 displays the medication basic information change screen 120 shown in FIG. 4 on the display unit 14.

(Drug basic information change screen; Fig. 4)
As shown in FIG. 4, the medication basic information change screen 120 includes a medication mode selection field 122, a row selection field 123, a medicine name selection field 124, an OK button 126, and a return button 128. The medication mode selection field 122 is a selection field for selecting a medication mode (that is, internal use, external use, injection) of a medicine taken by the user. The row selection column 123 is a selection column for selecting a row of initials (A line to Wa line) of medicines that the user takes. The medicine name selection field 124 is a selection field for the user to select a medicine name to be taken. In the medicine name selection field 124, each medicine corresponding to the medication mode (for example, “internal use”) selected in the medication mode selection field 122 and the row (for example, “A line”) selected in the line selection field 123 is displayed. The name is included in the choice. For example, the user can select “Aptexin Capsule 150 mg” in the medicine name selection column 124 by selecting “internal use” in the dosing mode selection column 122 and “A row” in the row selection column 123.

  When the user selects each information in each column 122 to 124 and presses an OK button 126, the user terminal 10 transmits the information selected in each column 122 to 124 to the management device 60.

  When receiving the selected information, the management device 60 updates the basic information 72 of the user data 70 in the memory 64 according to the selected information. When the update is completed, the management device 60 transmits main screen data to the user terminal 10.

  When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14 again.

(When shifting from the main screen to taking medication history information; FIGS. 5 to 9)
Next, a case where the medication history information is input from the state where the main screen 100 is displayed on the display unit 14 will be described. As shown in FIG. 5, the process from the authentication to the display of the main screen 100 on the display unit 14 of the user terminal 10 is the same as that in FIG.

  As shown in FIG. 5, when the medication information input link 104 (see FIG. 3) is selected by a user operation while the main screen 100 is displayed, the user terminal 10 displays the selection result (medicine information Information) is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 transmits the current day / previous day selection screen data to the user terminal 10.

  When receiving the current day / previous day selection screen data, the user terminal 10 causes the display unit 14 to display an unillustrated current day / previous day selection screen. While the current day / previous day selection screen is displayed, the user selects whether to input medication history information for the current day (ie, “current day”) or medication history information for the previous day (ie, “previous day”). can do. It is not possible to select to input medication history information two days or more before. That is, in this embodiment, the user cannot input medication history information that is two days or more before.

  In the example of FIG. 5, the user has selected “current day”. The user terminal 10 transmits information indicating the selection result (current day) to the management device 60. Note that the processing of the user terminal 10 and the management device 60 when the user selects “Previous Day” is basically the same as the subsequent processing when “Today” is selected. A process in the case where is selected will be described. When receiving the information indicating the selection result (the current day), the management device 60 refers to the medication history information 74 in the user data 70 and determines whether the medication history information for the day has already been input. When it is determined that the medication history information for the day has not been entered (YES in S10 of FIG. 5), the management device 60 transmits medication information input screen data to the user terminal 10. Upon receiving the medication information input screen data, the user terminal 10 displays the medication information input screen 140 shown in FIG.

  On the other hand, when it is determined that the medication history information for the day has already been input (NO in S10 of FIG. 5), the management device 60 transmits error data to the user terminal 10. When receiving error data, the user terminal 10 displays an error message (not shown) on the display unit 14. Although not shown in FIG. 5, if the user performs a predetermined confirmation operation while the error message is displayed, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14 again.

(Medication information input screen; Fig. 6)
As shown in FIG. 6, the medication information input screen 140 displays a medication button 142, a non-medicine button 144, and a return button 146, together with a date for entering medication history information and a registered medication name. The dose button 142 is a button for inputting information indicating that the user has taken medicine on the displayed date. On the other hand, the non-taking button 144 is a button for inputting information indicating that the user has not taken a medicine on the displayed date. Hereinafter, the process will be described separately when the user presses the dosing button 142 and when the user presses the non-dosing button 144.

(When dose button 142 is pressed)
When the user presses the dose button 142 (selects “I have taken”) while the medication information input screen 140 is displayed, the user terminal 10 displays information indicating the selection result (taken) in the management device 60. Send to. When the management device 60 receives the selection result (taking) (YES in S20 of FIG. 5), it updates the medication history information 74 of the user data 70 in the memory 64. Specifically, “take” is newly stored for the day. When the update is completed, the management device 60 subsequently transmits the side effect screen data to the user terminal 10. The side effect screen data includes data for displaying the general side effect screen 150 (see FIG. 7) and data for displaying the side effect input screen 160 (see FIG. 8).

  When acquiring the side effect screen data, the user terminal 10 displays the general side effect screen 150 shown in FIG.

(General side effect screen; Fig. 7)
As shown in FIG. 7, the general side effect screen 150 displays side effect information unique to the registered medicine. By viewing the general side effect screen 150, the user can know side effects unique to the registered medicine. Further, the general side effect screen 150 includes an OK button 152. When the user performs an operation of pressing the OK button 152, the user terminal 10 causes the display unit 14 to display a side effect input screen 160 shown in FIG. 8 instead of the general side effect screen 150.

(Side effect input screen; Fig. 8)
As shown in FIG. 8, the side effect input screen 160 includes check item groups 162, 164, and 166 for selecting side effects that have occurred as a result of taking the day. The check item group 162 is a selection item group of side effects related to skin symptoms. The check item group 164 is a selection item group of side effects related to gastrointestinal symptoms. The check item group 166 is a selection item group of other side effects. The user can check one or more applicable items among the item groups 162 to 166. Although not shown in FIG. 8, the side effect input screen 160 further includes a check item group for selecting side effects related to the state of meal, defecation, and limbs. Furthermore, at the bottom of the side effect input screen 160, a comment input field 168 for the user to input an arbitrary comment is provided. Further, an OK button 170 is provided on the side effect input screen 160. The user can check an applicable item from the check item groups 162 to 166 and press the OK button 170 in a state where a desired comment is input in the comment input field 168.

  When the OK button 170 is pressed, as illustrated in FIG. 5, the user terminal 10 transmits the side effect information input in each column of the side effect input screen 160 to the management device 60. When receiving the side effect information, the management device 60 updates the side effect information 76 of the user data 70 in the memory 64. Specifically, the side effect information for the day is newly stored. When the update is completed, the management device 60 subsequently transmits body measurement value input screen data to the user terminal 10.

  When the user terminal 10 receives the body measurement value input screen data, the user terminal 10 displays the body measurement value input screen 180 shown in FIG. 9 on the display unit 14.

(Body measured value input screen; Fig. 9)
As shown in FIG. 9, the body measurement value input screen 180 includes a body weight input unit 182 for inputting the user's body weight on the day, a body temperature input unit 184 for inputting body temperature, and a blood pressure input unit for inputting blood pressure. 186 has a pulse rate input unit 188 for inputting a pulse rate per minute. The body measurement value input screen 180 further has an OK button 190. The user can press the OK button 190 in a state where his / her body weight, body temperature, blood pressure, and pulse rate (that is, body state information) are input to the input units 182 to 188.

  When the OK button 190 is pressed, as shown in FIG. 5, the user terminal 10 transmits the body state information input to each input unit of the body measurement value input screen 180 to the management device 60. When receiving the physical condition information, the management device 60 updates the physical condition information 78 of the user data 70 in the memory 64. That is, the physical condition information of the day is newly stored. When the update is completed, the management device 60 transmits main screen data to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14.

  As described above, in this embodiment, the user can continuously input the side effect information and body condition information on the day after inputting the medication history information (taking) on the day. Since each information can be input without returning to the main screen, the user can easily input each information.

(When non-dosing button 144 is pressed)
On the other hand, when the user presses the non-dosing button 144 (selects “I did not take”) while the medication information input screen 140 (FIG. 6) is displayed in FIG. 5, the user terminal 10 The medication history information indicating the selection result (non-medication) is transmitted to the management device 60. When the management device 60 receives the selection result (not taken) (NO in S20 of FIG. 5), it updates the medication history information 74 of the user data 70 in the memory 64. That is, “not taking” is newly stored for the day. When the update is completed, the management device 60 subsequently transmits body measurement value input screen data to the user terminal 10. Note that the management device 60 does not transmit the side effect screen data to the user terminal 10 when the non-dosing button 144 is pressed on the medication information input screen 140.

  Upon receiving the body measurement value input screen data, the user terminal 10 displays the body measurement value input screen 180 (FIG. 9) on the display unit 14. Since the content of each process after that is the same as the process when the dosing button 142 is pressed, detailed description is omitted.

(When shifting from the main screen to inputting physical condition information; FIG. 10)
Next, a case where body state information is input from the state where the main screen 100 is displayed on the display unit 14 will be described. As shown in FIG. 10, the processing until the main screen 100 is displayed on the display unit 14 of the user terminal 10 is the same as that in FIG.

  As shown in FIG. 10, when the body measurement value input link 106 (see FIG. 3) is selected by a user operation while the main screen 100 is displayed, the user terminal 10 displays the selection result (body). Information indicating measurement value input) is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 transmits the body measurement value input screen data to the user terminal 10. Upon receiving the body measurement value input screen data, the user terminal 10 displays the body measurement value input screen 180 (FIG. 9) on the display unit 14. Here, the body measurement value input screen 180 displayed on the display unit 14 is a screen for inputting the physical condition information of the user on the day.

  The user can press the OK button 190 in a state where his / her body weight, body temperature, blood pressure, and pulse rate (that is, body state information) are input to the input units 182 to 188 of the body measurement value input screen 180.

  When the OK button 190 is pressed, the user terminal 10 transmits the physical state information input to each input unit of the body measurement value input screen 180 to the management device 60. When receiving the physical condition information, the management device 60 updates the physical condition information 78 of the user data 70 in the memory 64. Specifically, the physical condition information for the day is newly stored. When the update is completed, the management device 60 transmits main screen data to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14.

(When shifting from the main screen to the medication calendar screen display; FIGS. 11 and 12)
Next, a case will be described where the main screen 100 is displayed on the display unit 14 and the state is shifted to a state in which a medication calendar screen (see FIG. 12) is displayed. As shown in FIG. 11, when the medication calendar link 108 (see FIG. 3) is selected by the user's operation while the main screen 100 is displayed on the display unit 14 of the user terminal 10, the user terminal 10 Information indicating the selection result (medication calendar) is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 generates calendar data based on the user data 70 and transmits the generated calendar data to the user terminal 10. The calendar data includes data for displaying the medication calendar screen 200 (FIG. 12) and data for displaying the menu screen 220 (FIG. 12).

  When receiving the calendar data, the user terminal 10 displays the medication calendar screen 200 shown in FIG. 12 on the display unit 14.

(Medication calendar screen; Fig. 12)
As shown in FIG. 12, the medication calendar screen 200 displays a list of medication history information for each user's month. FIG. 12 shows a medication calendar screen 200 showing medication history information for August 2013 as of August 27, 2013.

  Next to each date prior to the current day (27th), a mark “◯” or “X” is added. There is no mark next to each date after that date. The mark “◯” indicates that the user has taken medicine on that day (that is, the user has registered medication history information indicating “taken”). The “x” mark indicates that the user did not take the medicine on that day (that is, the user has registered medication history information indicating “not taking”), or the user has taken the medication history for that day. Indicates that no information is registered. The user can check his / her medication history in units of one month by looking at the medication calendar screen 200.

  A link selectable by the user is formed on the mark 202 (◯) on the current day (27th) and the mark 204 (◯) on the previous day (26th). In addition, a link that can be selected by the user is not formed in the mark two days ago (before 25 days). If the previous day's medication history information has not been entered, the character (26) of the previous day's date is displayed in red and is distinguished from other characters. The user can recognize that the previous day's medication history information has not been entered by looking at the red date.

  The medication calendar screen 200 also displays a switching link 206 for changing the display month. An end button 208 for ending the display of the medication calendar screen 200 is also displayed.

  When the user selects the mark 202 (◯) on the current day (27th) or the mark 204 (◯) on the previous day (26th), a menu screen 220 for inputting each information on the selected date is displayed. On the menu screen 220, medication history information input link 222, side effect information input link 224, and physical condition information input link 226 are displayed. In the example of FIG. 11, the user selects the current day mark 202. The user terminal 10 causes the display unit 14 to display a menu screen 220 for inputting information on the day. The process when the user selects the mark 204 of the previous day is substantially the same as the process when the mark 202 of the current day is selected, and therefore only the case where the mark 202 of the current day is selected will be described below.

  When the user selects the medication history information input link 222 while the menu screen 220 is displayed, the user terminal 10 transmits information indicating the selection result (medicine history information input) to the management device 60. Each process between the user terminal 10 and the management apparatus 60 after the management apparatus 60 receives the selection result (medicine history information input) is the same as each process after the portion A in FIG. Omitted.

  When the user selects the side effect information input link 224 while the menu screen 220 is displayed, the user terminal 10 transmits information indicating the selection result (side effect information input) to the management device 60. Each process between the user terminal 10 and the management apparatus 60 after the management apparatus 60 receives the selection result (input of side effect information) is the same as each process after the portion B in FIG. To do.

  When the user selects the physical condition information input link 226 while the menu screen 220 is displayed, the user terminal 10 transmits information indicating the selection result (physical condition information input) to the management device 60. Since each process between the user terminal 10 and the management apparatus 60 after the management apparatus 60 receives the selection result (input of side effect information) is the same as each process after the portion C in FIG. To do.

  On the other hand, in FIG. 11, when the user presses the end button 208 while the medication calendar screen 200 is displayed, the user terminal 10 transmits information indicating the selection result (end) to the management device 60. When receiving the selection result, the management device 60 transmits main screen data to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14.

(When shifting from the main screen to profile change; Fig. 13)
Next, a case where the content of the basic information (name, contact information, occupation, date of birth, etc.) of a registered user is changed from the state in which the main screen 100 is displayed on the display unit 14 will be described. As shown in FIG. 13, when the profile change link 110 (see FIG. 3) is selected by a user operation while the main screen 100 is displayed, the user terminal 10 displays the selection result (profile change). Is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 transmits the profile change screen data to the user terminal 10.

  When receiving the profile change screen data, the user terminal 10 displays a profile change screen (not shown) on the display unit 14. The profile change screen is provided with a plurality of input fields for inputting basic information of the user (namely, name, contact information, date of birth, etc.) and an OK button. The user can input the changed user basic information in each input field and press the OK button.

  When the OK button is pressed, as illustrated in FIG. 13, the user terminal 10 transmits the changed basic information of the user input in each input field to the management device 60. When receiving the basic information, the management device 60 updates the basic information 72 of the user data 70. Specifically, the received basic information is newly stored. When the update is completed, subsequently, the management device 60 transmits main screen data to the user terminal 10.

  When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14 again.

(When shifting from the main screen to the correlation diagram screen display; FIGS. 14 and 15)
Next, a case where the main screen 100 is displayed on the display unit 14 and the state where the correlation diagram screen (see FIG. 15) is displayed will be described. As shown in FIG. 14, when the correlation diagram link 112 (see FIG. 3) is selected by a user operation while the main screen 100 is displayed, the user terminal 10 displays the selection result (correlation diagram). Is transmitted to the management device 60. When receiving the information indicating the selection result, the management device 60 generates correlation diagram screen data based on the user data 70 and transmits the generated correlation diagram screen data to the user terminal 10.

  When the user terminal 10 receives the correlation diagram screen data, the user terminal 10 displays the correlation diagram screen 240 shown in FIG. 15 on the display unit 14.

(Correlation diagram screen; Fig. 15)
As shown in FIG. 15, on the correlation diagram screen 240, the user's monthly weight, body temperature, blood pressure (upper), blood pressure (lower), and pulse rate are each represented by a line graph. The horizontal axis of the graph represents the date. Below each date, a mark “◯” or “X” is marked. A mark “◯” indicates that the user took a medicine on that day. The mark “x” indicates that the user did not take medicine on that day, or that the user did not register medication history information. By viewing the correlation diagram screen 240, the user grasps the relationship between changes in his / her state (weight, body temperature, blood pressure (up), blood pressure (down), pulse rate) and medication history in one month units. be able to.

  In addition, an end button 242 for ending the display of the correlation diagram screen 240 is also displayed on the correlation diagram screen 240.

  When the user presses the end button 242 while the correlation diagram screen 240 is displayed, the user terminal 10 transmits information indicating the operation result (end) to the management device 60. Upon receiving the operation result, the management device 60 transmits main screen data to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14.

(When moving from the main screen to entering the scheduled visit date; Fig. 16)
Next, a case where the user's next scheduled visit date is input from the state where the main screen 100 is displayed on the display unit 14 will be described. As shown in FIG. 16, when the scheduled visit date input link 114 (see FIG. 3) is selected by a user operation while the main screen 100 is displayed on the display unit 14, the user terminal 10 Information indicating the selection result (input scheduled hospital visit date) is transmitted to the management device 60. When the management device 60 receives the information indicating the selection result, the management device 60 transmits the scheduled visit date input screen data to the user terminal 10.

  Upon receiving the scheduled visit date input screen data, the user terminal 10 causes the display unit 14 to display a scheduled visit date input screen (not shown). The scheduled visit date input screen is provided with an input field for the user to enter a scheduled date for the next visit and an OK button. The user can enter the next scheduled visit date in the input field and press the OK button.

  When the OK button is pressed, as shown in FIG. 16, the user terminal 10 transmits to the management device 60 scheduled visit date information indicating the scheduled visit date that has been input in the input field. When the management device 60 receives the scheduled visit date information, it updates the basic information 72 of the user data 70 in the memory 64. Specifically, the received scheduled visit date information is newly stored. When the update is completed, the management device 60 transmits main screen data to the user terminal 10. When receiving the main screen data, the user terminal 10 displays the main screen 100 (FIG. 3) on the display unit 14 again.

  Moreover, as shown in FIG. 16, the management apparatus 60 will monitor that a predetermined notification timing comes, if hospital visit date information is memorize | stored. In this embodiment, the predetermined notification timing is 8:00 am seven days before the scheduled visit date and 8:00 am the day before the scheduled visit date.

  When the management device 60 detects that a predetermined notification timing has arrived, the management device 60 generates an e-mail based on the user data 70 and transmits the generated e-mail to the user terminal 10.

  When receiving the electronic mail, the user terminal 10 performs a notification operation. When the user performs an operation to open the e-mail, the text of the e-mail is displayed on the display unit 14. The text includes a message notifying that the scheduled hospital visit date is near. The user can remember the next scheduled visit date by looking at the email sent from the management device 60.

  In the above, each process when the user of the user terminal 10 operates the user terminal 10 to use the system has been described. Each process when the user of the user terminal 20 operates the user terminal 20 to use this system is the same as described above.

(Example of using this system by operating the medical institution terminal 30; FIGS. 17 to 19)
Next, a case where the user of the medical institution terminal 30 operates the medical institution terminal 30 to use this system will be described. When a user of a medical institution terminal uses the system by operating the medical institution terminal 30, the user needs to perform user registration in advance. Specifically, first, the medical institution terminal 30 accesses the management apparatus 60 in accordance with a user operation. At this time, the medical institution terminal 30 accesses the management apparatus 60 using the URL of the institution web page provided by the management apparatus 60 as a connection destination. The URL of the engine web page is different from the URL of the user web page. The management device 60 transmits predetermined new user registration screen data to the medical institution terminal 30. The new user registration screen data is different from the new user registration screen data for the user terminal 10 described above. The medical institution terminal 30 displays a new user registration screen (not shown) on the display unit 14 in accordance with the new user registration screen data. The user operates the operation unit 32 to input basic information such as a medical institution ID (“H1”), a login password, and a contact address of the medical institution. The user can select a desired medical institution ID and password. The medical institution terminal 30 transmits the input basic information to the management device 60. When receiving the basic information, the management device 60 stores the received basic information in the memory 64. As a result, the medical institution data 90 corresponding to the ID “H1” is generated in the memory 64, and the user registration is completed. When the medical institution that has been registered by the user subsequently accesses the management apparatus 60, the authentication provided by the management apparatus 60 is performed by performing predetermined authentication (that is, login) using the registered medical institution ID and password. The system can be used.

(When shifting from the list screen to the display of individual screens; FIGS. 17 to 19)
As shown in FIG. 17, when the medical institution terminal 30 accesses the management device 60 and executes predetermined authentication in accordance with the operation of the user of the medical institution terminal 30, provision of the present system for the medical institution is started. First, the management device 60 reads the user data 70 and 80 of each user with reference to the memory 64, generates list screen data, and transmits it to the medical institution terminal 30. When receiving the list screen data, the medical institution terminal 30 displays the list screen 300 shown in FIG.

(List screen; Fig. 18)
As shown in FIG. 18, the list screen 300 includes combination information 310 to 318 related to each of a plurality of users whose user data (70, 80, etc. in FIG. 1) is stored in the memory 64 of the management apparatus 60. . Each combination information 310 to 318 includes a number, a user ID, a gender, an area, and a job. The number is a serial number in the list screen 300. The user ID is an ID (for example, P1, P2, etc.) registered by the user at the time of user registration. The sex, area, and job indicate the gender of the user, the prefecture where the user resides, and the occupation of the user, respectively. Personal information such as the name, telephone number, and detailed address of each user is not displayed on the list screen 300. For example, the combination information 310 includes a number “55”, a user ID “P1”, a gender “male”, an area “Gifu Prefecture”, and a job “company employee”. Therefore, the combination information 310 indicates the user (user ID “P1”) of the user terminal 10 in FIG. The user of the medical institution terminal 30 can grasp what kind of user exists by looking at the list screen 300.

  While the list screen 300 is displayed on the display unit 34, the user of the medical institution terminal 30 may select any one combination information among the combination information 310 to 318 included in the list screen 300. it can. Hereinafter, a case where the user selects the combination information 310 corresponding to the user ID “P1” will be described.

  When the combination information 310 (user ID “P1”) is selected, the medical institution terminal 30 transmits information indicating the selection result (combination information 310) to the management apparatus 60, as shown in FIG. Upon receiving the selection result, the management device 60 generates individual screen data related to the user ID “P1” based on the user data 70 corresponding to the user ID “P1” in the memory 64, and the generated individual screen data is Transmit to the medical institution terminal 30.

  When acquiring the individual screen data, the medical institution terminal 30 displays the individual screen 330 shown in FIG.

(Individual screen; Fig. 19)
As illustrated in FIG. 19, the individual screen 330 displays a list of medication history, side effects, and physical state of the user with the user ID “P1”. In addition to the user ID (P1), the individual screen 330 displays gender (male), region (Gifu Prefecture), and age (34). The individual screen 330 also does not display personal information that can identify the user, such as the user's name. The individual screen 330 further includes, for each date, a medication history (“○” or “x”) indicating whether or not the user has taken the medicine, the user status (weight, blood pressure, heart rate, body temperature), side effects. Is displayed. The user of the medical institution terminal 30 can grasp the medication history, side effects, physical condition, etc. of the user with the user ID “P1” by looking at the individual screen 330.

  The user of the medical institution terminal 30 can perform a predetermined display end operation while the individual screen 330 is displayed. When the display end operation is performed, the medical institution terminal 30 transmits the operation result (display end) to the management device 60. When receiving the operation result, the management device 60 transmits the list screen data to the medical institution terminal 30. When receiving the list screen data, the medical institution terminal 30 displays the list screen 300 (FIG. 18) on the display unit 34 again.

  In the above, each process when the user of the medical institution terminal 30 operates the medical institution terminal 30 to use the system has been described. Each process when the user of the manufacturer terminal 50 operates the manufacturer terminal 50 to use the system is the same as described above.

(Effect of this embodiment)
The medication management system 2 of the present embodiment has been described above. In this embodiment, if the user of the user terminal 10 inputs his / her medication history information (medication / non-medication) through the medication information input screen 140 of FIG. 6, then the medication calendar screen 200 (FIG. 12) is displayed. You can see your medication history by looking at it. Since the user only needs to select whether or not he / she has taken medicine while the medication information input screen 140 of FIG. 6 is displayed, the scheduled time for taking the medicine can be set as in the conventional system. There is no need to perform registration work in advance. Further, unlike the conventional system, the user is not prompted to take medication by the notification operation of the terminal, and thus the user must voluntarily take the medication. Therefore, according to the medication management system 2 of the present embodiment, the user can perform independent medication management over a long period of time more easily than in the past.

  Further, in this embodiment, the user can select the current day and day from the medication information input screen 140 in FIG. 6, the side effect input screen 160 in FIG. 8, the body measurement value input screen 180 in FIG. 9, or the medication calendar screen 200 in FIG. It is possible to input the previous day's information. However, the user cannot input information two days ago. The information on the previous day is highly likely to be accurate because it is highly likely that the user has accurately stored whether or not the medicine has been taken. On the other hand, information stored more than two days ago may cause the user's memory to be ambiguous, and the content may be inaccurate. In the present embodiment, even if the user forgets to input the previous day's information, the user can input the previous day's information that is highly likely to be accurate. On the other hand, the user cannot input medication information two or more days before that the content may be inaccurate. Therefore, the accuracy of the information stored in the memory 64 of the management device 60 can be ensured.

  In the present embodiment, as shown in FIG. 5, when it is determined that the medication history information for the day has already been input (NO in S <b> 10 of FIG. 5), the management device 60 sends error data to the user terminal 10. Send to. That is, the user cannot change the content of the medication history information once stored in the memory 64. Therefore, the medication history information once stored in the memory cannot be modified by the user or any other person. The accuracy of the medication history information in the management device 60 can be ensured.

  The user looks at the correlation diagram screen 240 in FIG. 15, and the relationship between changes in his / her state (weight, body temperature, blood pressure (upper), blood pressure (lower), pulse rate) and medication history in one month units. Can be grasped. The user can appropriately manage his / her medication situation.

  Also, as shown in FIG. 16, the user can receive an e-mail from the management device 60 each time a predetermined notification timing arrives by registering the next scheduled hospital visit date. The user can remember the next scheduled visit date by looking at the email sent from the management device 60. It is possible to suppress the user from forgetting the scheduled visit date.

  As shown in FIGS. 17 to 19, the user of the medical institution terminal 30 can grasp what kind of user exists by looking at the list screen 300 (FIG. 18). Further, the user of the medical institution terminal 30 can grasp the medication history, side effects, physical condition, etc. of each user by looking at the individual screen 330 (FIG. 19). The medical institution can analyze the user's medication situation. In addition, since the personal information of the user is not included in the list screen 300 or the individual screen 330, the personal information of the user does not leak out.

(Correspondence)
The operation unit 12 and the control unit 16 are examples of “input means” and “transmission means”, the CPU 62 is an example of “storage control means” and “generation means”, the medication history information is an example of “medication information”, the body condition information and The side effect information is an example of “status information”, the calendar data in FIG. 11, the correlation diagram screen data in FIG. 14 is an example of “first output data”, the list screen data and the individual screen data in FIG. 17 are “second output”. It is an example of “data”.

  As mentioned above, although one Example of the technique disclosed by this specification was described in detail, these are only illustrations and do not limit a claim. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modifications may be included.

(Modification 1) In the above embodiment, as shown in FIG. 5, when the medication history information (medication) is input from the medication information input screen 140 in FIG. 6, the display unit 14 displays the side effect input screen 160 in FIG. Then, the body measurement value input screen 180 of FIG. 9 is continuously displayed, and the user can continuously input the side effect information of the day without returning to the main screen 100 (FIG. 3). Instead, after receiving the medication history information, the management device 60 transmits the side effect screen data to the user terminal 10 only when the user desires to continuously input the side effect information for the day. Also good. If the user does not wish to continuously input the side effect information for the day, the main screen data may be transmitted to the user terminal 10 instead of the side effect screen data. Similarly, after receiving the side effect information, the management device 60 transmits the body measurement value input screen data to the user terminal 10 only when the user desires to continuously input the physical condition information of the day. May be. When the user does not wish to continuously input the physical condition information of the day, the main screen data may be transmitted to the user terminal 10 instead of the body measurement value input screen data.

(Modification 2) The correlation diagram screen 240 of FIG. 15 displays a line graph in which the medication history information and the body state information are associated with each other. On the correlation diagram screen, the present invention is not limited to this, and in addition to the medication history information and the body state information, side effect information may be displayed in further association. In this case, the display mode of each information on the correlation diagram screen is not limited to the line graph as shown in FIG. According to this modification, the user can grasp his / her medication situation more appropriately.

(Modification 3) In the above embodiment, as shown in FIG. 16, when the management device 60 stores the scheduled visit date information, it monitors whether a predetermined notification timing has arrived. The predetermined notification timing is 8:00 am seven days before the scheduled hospital visit date and 8:00 am the day before the scheduled hospital visit date. The predetermined notification timing is not limited to the above timing, and can be any timing as long as it is a timing before the day of the scheduled date of hospital visit.

  The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

2: medication management system, 10: user terminal, 12: operation unit, 14: display unit, 16: control unit, 20: user terminal, 30: medical institution terminal, 32: operation unit, 34: display unit, 36: control 50: manufacturer terminal, 60: management device, 62: CPU 62, 64: memory, 68: system program, 70: user data, 72: basic information, 74: medication history information, 76: side effect information, 78: physical condition Information: 80: User data, 82: Basic information, 84: Medication history information, 86: Side effect information, 88: Body condition information, 90: Medical institution data, 95: Manufacturer data, 100: Main screen, 120: Basic medication information Change screen, 140: medication information input screen, 150: general side effect screen, 160: side effect input screen, 180: measurement value input screen, 200: medication calendar screen, 220 Menu screen 240: correlation diagram screen 300: list screen, 330: individual frame

Claims (6)

A medication management system for orphan drugs used to treat rare diseases,
A management device and a user terminal capable of communicating with the management device;
User terminal
An input means by which the user can input at least medication information on the day indicating whether he / she has taken the medicine on the day;
When the medication information on the day is input, it has a transmission means for transmitting the medication information entered on the day to the management device,
The management device
When acquiring the medication information of the day from the user terminal, storage control means for storing the acquired medication information of the day in the memory,
Generating means for generating first output data related to the user's medication information based on the medication information for one day or more stored in the memory,
The user terminal is allowed to access the first output data;
Medication management system. The input means further allows the user to input medication information on the previous day indicating whether he / she took the medicine one day before that day, or whether he / she took the medicine more than two days before the day. It is impossible to enter medication information more than 2 days ago indicating whether or not
When the medication information for the previous day is input, the transmission means transmits the medication information for the previous day to the management device.
2. The medication management system according to claim 1, wherein the storage control means stores the acquired medication information of the previous day in a memory when the medication information of the previous day is acquired from the user terminal.   The medication management system according to claim 1 or 2, wherein the storage control means cannot change the content of medication information once stored in the memory. The input means further allows the user to input the status information of the day related to his / her physical condition of the day,
When the status information of the day is input, the transmission means transmits the status information of the input to the management device,
When the storage control means acquires the status information of the current day from the user terminal, the storage control means stores the acquired status information of the current date in the memory,
The medication unit according to any one of claims 1 to 3, wherein the generation unit generates first output data based on medication information for one day or more and state information for one day or more stored in a memory. Management system. The management device further comprises a notification means,
Further, the input means allows the user to input schedule date information indicating his / her next scheduled visit date,
When the scheduled date information is input, the transmission means transmits the input scheduled date information to the management device,
The storage control means, when acquiring the scheduled date information from the user terminal, stores the acquired scheduled date information in the memory,
The notification means transmits notification information for notifying a user's next hospital scheduled date to the user terminal before the scheduled date indicated by the scheduled date information stored in the memory. Medication management system. The medication management system further includes an external institution terminal that can communicate with the management device and is a terminal different from the user terminal,
The generation means further generates second output data related to the user's medication status based on the medication information for one day or more stored in the memory,
The second output data is data different from the first output data, is accessible from an external institution terminal, and is data that does not include user personal information. Medication management system.

Images