JP7419690B2 - Information management system and control program - Google Patents

Description

The present invention relates to an information management system and a control program. In particular, the present invention relates to an information management system and a control program that handle events that take place at a facility that provides care to a person receiving care.

In facilities that provide care for cared people (hereinafter referred to as nursing care facilities), staff not only care for cared people but are also busy with various miscellaneous tasks. This miscellaneous work involves telephone inquiries from the cared person's family regarding the cared person's situation. In response to such inquiries, you may have to stop your original work and look up the information you need to answer, or if you cannot interrupt your original work, call again after your work has temporarily ended. must be done. As a result, staff members are burdened with an increased burden of responding to inquiries. On the other hand, the family of the cared person is hesitant to make inquiries over the phone in order to avoid disturbing the staff, resulting in the problem of not being able to obtain the necessary information.

In recent years, chat services using mobile terminals such as smartphones have become popular. Further, in this chat service, there is a chatbot system that automatically responds using an automatic dialogue program using AI (for example, Patent Document 1).

By applying a chatbot system such as that disclosed in Patent Document 1, it is possible to solve problems related to inquiries from family members of cared for.

Japanese Patent Application Publication No. 2009-3533

Here, in facilities such as nursing care facilities, events are frequently held in order to promote interaction among residents of the facility, exercise, and improve physical abilities. In preparation for these events, staff will need to contact families to ensure that they are organizing the event and making preparations leading up to the event. Traditionally, this communication was often done by sending documents by mail. Preparations for mailing are necessary for this purpose. Additionally, families who receive mailed documents may lose them, and in such cases, staff have to respond to inquiries from families, which is time-consuming. In view of this situation, the present application aims to provide an information management system and a control program that allow families to be easily notified of events taking place at a facility.

The above object of the present invention is achieved by the following means.

(1) A reception section that accepts access via the network;
A second type of identification information of a person to be cared for in a facility, a first type of identification information used in the facility where the person to be cared for is present, and a family member of the person to be cared for associated with the second type of identification information. a storage unit that stores third type identification information regarding the information, and registers information received by the reception unit through access using the first type identification information;
a control unit;
comprising a transmitting section;
The reception unit receives event information regarding an event to be held at the facility and in which a plurality of care recipients at the facility participate, through access using the first type of identification information ;
The control unit registers the event information received by the reception unit in the storage unit, publishes the event information, and sends each of the second type identification information of the plurality of care recipients by the transmission unit. Notifying the event information to the user of the associated third type of identification information;
Information management system.
(2) The information management system according to (1) above, wherein the event is an event in which the care recipient participates and the care recipient's family does not participate.

( 3 ) The reception unit receives a public request for the event,
The information management system according to (1) or (2) above, wherein the control unit publishes the event information and issues the notification in response to receiving the disclosure request.

( 4 ) The event information includes information on the holding period of the event,
The information management system according to ( 3 ) above, wherein the control unit makes the event information private as the holding period of the event elapses.

( 5 ) The facility has multiple units to which multiple care recipients belong,
The event includes an overall event held in the entire facility and an individual event held in each unit,
When the reception unit receives the registration of the event information regarding the individual event, the control unit transmits the second type of identification of the care recipient belonging to the unit of the individual event by the transmission unit. The information management system according to any one of (1) to ( 4 ) above, wherein the event information is notified to a user of the third type of identification information associated with the information.

( 6 ) The person to be cared for is a cared person;
The event includes a level-based event in which participants differ depending on the level of support required and care required of the cared person,
When the reception unit receives the registration of the event information regarding the level-based event, the control unit causes the transmission unit to associate the event information with the second type of identification information of the participant according to the level. The information management system according to any one of (1) to ( 5 ) above, wherein the event information is notified to a user of the third type of identification information.

( 7 ) The event information includes information on the holding period of the event,
Any one of (1) to ( 6 ) above, wherein the control unit sends a reminder notification to the user of the third type identification information by the transmission unit a predetermined period before the event period. Information management system described in.

( 8) The notification is performed by a notification message to the user of the third type of identification information,
Any one of (1) to ( 7 ) above, wherein the control unit accepts a reservation for participation in the event by the user of the third type of identification information and a cancellation of the reservation for participation, in response to the notification message. Information management system described in.

( 9 ) The notification is performed by a notification message to the user of the third type of identification information,
In response to the notification message, the control unit makes a reservation for participation in the event of the care recipient of the associated second type of identification information by the user of the third type of identification information, and the reservation for participation. The information management system according to ( 8 ) above, which accepts cancellations.

( 10 ) The event information includes information on the holding period of the event,
( 8 ) above, wherein the control unit causes the transmission unit to send a reminder to the user of the third type of identification information who has accepted the participation reservation a predetermined period before the event period; or The information management system described in ( 9 ) above.

( 11 ) The notification is performed by a notification message to the user of the third type of identification information,
The information management system according to any one of (1) to ( 10 ) above, wherein the transmitter transmits the notification message at a preset notification time.

( 12 ) A reception unit that accepts access via the network;
a transmitting unit , second type identification information of a care recipient in a facility, first type identification information used in the facility where the care recipient is located, and the care associated with the second type identification information. A control program for controlling an information management system comprising: a storage unit storing third type identification information regarding a subject's family ;
(a) receiving, by the reception unit, event information regarding an event to be held at the facility and attended by a plurality of care recipients at the facility, through access using the first type of identification information;
a step (b) of registering the event information received in the step (a) in the storage unit;
The event information registered in the step (b) is made public, and the user of the third type of identification information associated with each of the second type of identification information of the plurality of care recipients in the facility by the transmission unit. A control program for causing a computer to execute processing including a step (c) of notifying the event information.
(13) The control program according to (12) above, wherein the event is an event in which the care recipient participates and a family member of the care recipient does not participate.

( 14 ) The process further includes a step (d) of receiving a public request for the event by the reception unit,
The control program according to ( 12 ) or (13) above, wherein in step (c), the event information is published and notified in response to receiving the disclosure request in step (d).

( 15 ) The event information includes information on the holding period of the event,
The control program according to ( 14 ) above, wherein the process further includes a step (e) of making the event information private as the event period elapses.

( 16 ) The facility has multiple units to which multiple care recipients belong,
The event includes an overall event held in the entire facility and an individual event held in each unit,
In the step (c), when the reception unit receives the registration of the event information regarding the individual event, the transmission unit sends the second type of care recipient belonging to the unit of the individual event. The control program according to any one of ( 12 ) to ( 15 ) above, wherein the control program notifies the event information to a user of the third type of identification information associated with the identification information of.

( 17 ) The person to be cared for is a cared person,
The event includes a level-based event in which participants differ depending on the level of support required and care required of the cared person,
In the step (c), when the reception unit receives the registration of the event information regarding the level-based event, the transmission unit transmits the second type of identification information of the participant according to the level. The control program according to any one of ( 12 ) to ( 16 ) above, wherein the control program notifies the event information to a user of the third type of identification information associated with.

( 18 ) The event information includes information on the holding period of the event,
From ( 12 ) above, the process further includes a step (f) of sending a reminder notification to the user of the third type of identification information by the transmitting unit a predetermined period before the event period. The control program according to any one of ( 17 ) above.

( 19 ) The step (c) is performed by a notification message to the user of the third type of identification information,
From ( 12 ) above, the processing further includes a step (g) of accepting a reservation for participation in the event by the user of the third type of identification information and a cancellation of the reservation for participation, in response to the notification message. The control program according to any one of ( 18 ) above.

( 20 ) The notification is performed by a notification message to the user of the third type of identification information,
In the step (g), in response to the notification message, the user of the third type of identification information makes a reservation for the care recipient of the associated second type of identification information to participate in the event, and The control program according to ( 19 ) above, which accepts cancellation of participation reservation.

( 21 ) The event information includes information on the holding period of the event,
The process further includes a step (h) of causing the transmission unit to send a reminder to the user of the third type of identification information who has accepted the participation reservation a predetermined period before the event period. , the control program according to ( 19 ) above, or ( 20 ) above.

( 22 ) The notification is performed by a notification message to the user of the third type of identification information,
The control program according to any one of ( 12 ) to ( 21 ) above, wherein in step (c), the notification message is transmitted at a preset notification time.

The information management system according to the present invention includes a reception unit that accepts access via a network, and a storage unit that registers information received by the reception unit through access using first type identification information used in a facility where a care recipient is located. , a control unit, and a transmission unit, the reception unit receives event information regarding an event to be held at the facility, and the control unit registers the event information received by the reception unit in the storage unit and publishes the event information. Furthermore, the event information is notified by the transmitting unit to the user of the third type of identification information associated with the second type of identification information of the person to be cared for at the facility. This allows families to be easily notified of events taking place at the facility.

1 is a diagram showing an overview of an information management system according to an embodiment of the present invention. FIG. 1 is a block diagram showing a schematic configuration of an information management system. FIG. 3 is a diagram showing an example of an ID list. FIG. 3 is a diagram showing an example of an ID list. FIG. 3 is a diagram showing event information transmission processing in the first embodiment. This is an example of an operation screen for registering event information displayed on a terminal device. This is an example of an input screen for inputting event information displayed on a terminal device. This is an example of a message displayed on a mobile terminal. This is an example of an input screen for inputting event information used in the second embodiment. FIG. 7 is a diagram illustrating event information transmission processing in the second embodiment. It is a figure showing event information transmission processing in a modification.

Embodiments of the present invention will be described below with reference to the accompanying drawings. In addition, in the description of the drawings, the same elements are given the same reference numerals, and redundant description will be omitted. Furthermore, the dimensional ratios in the drawings are exaggerated for convenience of explanation and may differ from the actual ratios.

(overall structure)
FIG. 1 is a diagram showing an overview of an information management system 10 according to this embodiment, and FIG. 2 is a block diagram showing a schematic configuration of the information management system 10.

The information management system 10 according to the present embodiment will be described using an example of a case where the information management system 10 is a care facility, manages content of a cared person in the nursing care facility, and responds to the cared person's family. However, the scope of application of this embodiment is not limited to nursing care facilities. In addition to nursing care facilities, care facilities include hospitals and facilities that provide child care services such as kindergartens or nursery schools. In addition, care recipients include care recipients, hospitalized patients, and kindergarten or nursery school children, and care includes nursing care, nursing care, and care for infants. In addition, the care record as content includes a care record sheet, a nursing record sheet (medical record, daily life record), and a response record (care record sheet) that records these cares, as well as information for the infant's family recorded by childcare staff. Contains contact book.

In addition, care recipients in facilities include caregivers in nursing care facilities, patients admitted to hospitals, and children or infants enrolled in kindergartens or nursery schools. . Events held at the facility include Setsubun, Doll's Festival, birthday parties, sports days, Christmas, excursions, walks, etc. Further, the event includes an event in which the person being cared for and/or their family participates.

As shown in FIG. 1, the information management system 10 and the plurality of terminal devices 30 and 40 are communicatively connected to each other through a network. The network is a communication line such as a public telephone network or a data communication network. Some networks may use a wired LAN, a wireless LAN, or the like (for example, a LAN that complies with the IEEE802.11 standard).

In the following, the facility (nursing facility) has a first type identification ID (first type identification information), and the resident (care recipient) of this facility has a second type identification ID (second type identification information). information), but this resident's family is given a third type identification ID (third type identification information), and these first to third type identification IDs are managed by the information management system 10. Ru. In addition, the first to third types of identification IDs are simply referred to as first to third type IDs below, and the first to third types of IDs are facility IDs, respectively. Also called care recipient ID or family ID. Further, the terminal device 30 uses the first type ID (facility ID), and the terminal device 40 uses the third type ID (family ID) to access the services of the information management system 10.

The terminal devices 301, 302, ... 30n (hereinafter, these are also collectively referred to simply as the terminal devices 30. The same applies to the terminal device 40) are terminal devices for each nursing facility, and are, for example, PCs (personal computers). Although the terminal is usually installed inside a nursing care facility, it is not limited to this, and an ID managed by the facility may be used for a terminal installed outside the facility. Further, the terminal device 30 may be a multifunction peripheral (MFP) connected to a network, like the terminal device 302. In this case, the functions of the terminal device 30 are incorporated into the multifunction device. Here, the cared person is a person who is admitted to a nursing care facility and is cared for on a daily basis by care staff (hereinafter simply referred to as staff). The terminal devices 401 and 402 are terminals used by the care recipient's family, and are portable terminal devices such as a PC or a smartphone. Family members are basically registered by the care facility management company based on an application from the care recipient or his or her family. The family may include relatives registered in advance by the cared person or other related persons including non-blood relatives.

The information management system 10 is a robot server (hereinafter also referred to as a "BOT server") that provides services for managing contents and messages of a nursing care facility. Details of the information management system 10 and details of the first to third type IDs managed by the information management system 10 will be described later.

As shown in FIG. 2, the information management system 10 includes a control section 11, a communication section 12, a first storage section 13, and a second storage section 14. The first storage unit 13 and the second storage unit 14 are so-called databases. The first storage unit 13 and the second storage unit 14 may be incorporated into the information management system 10 as shown in FIG. It may also be an independent configuration. Further, the entire information management system 10 may be a cloud server that is virtually constructed by a plurality of servers arranged on a network such as the Internet.

(First storage unit 13)
The first storage unit 13 manages content related to nursing care facilities. The content as this related information may include an ID list, nursing information (care information), event information, and a reservation list.

The "ID list" includes information on first to third type IDs and their mutual correspondence. 3 and 4 are examples of ID lists stored in the first storage unit 13. Referring to FIG. 3, the table 61 describes the correspondence between the first type ID (facility ID), facility name, and location. The table 62 describes the correspondence between the second type ID (care recipient ID), name, and room number. The table 63 describes the third type ID (family ID), name, contact information, and attributes. Referring to FIG. 4, the table 64 describes the correspondence between the first type ID and the second type ID. Further, the table 64 has a unit name (“1F East”) written therein. Here, a unit is a care recipient unit to which multiple care recipients who live in a common area such as the same floor within a facility belong, and a staff unit to which multiple staff in charge of these care recipient units belong. be. Furthermore, the table 65 describes the correspondence between the second type ID and the third type ID. That is, the first storage unit 13 stores the mutual correspondence of the first type ID to the third type ID. Further, the table 66 describes the second type ID and the certification level of the degree of support required and the degree of care required. Note that the items in these tables are merely examples, and any item may be omitted or other items may be added.

The first storage unit 13 stores related information. This related information includes event information regarding an event to be held at the facility and a list of people who have made reservations to participate in this event. Further, the related information may include image data obtained by reading the care record sheet (hereinafter referred to as "read image data") and care information (care information). The related information is information received by access using the first type ID (facility ID), and is stored in association with the first type ID and/or the second type ID. The nursing care information may include information regarding nursing care detected from text data obtained by character recognition processing of read image data of a nursing care record sheet. Furthermore, the nursing care information entered by key input (manual input) on the terminal device 30 by the staff, staff leader, or facility manager (hereinafter simply referred to as "staff, etc.") who provides care for the care recipient at the nursing care facility. It may also include information regarding.

(Second storage unit 14)
The second storage unit 14 manages messages related to access by a third type ID (family ID) or the like. The object of this management includes message history. Message history is managed for each type 3 ID. These will be described later.

(Control unit 11)
The control unit 11 includes a processor (CPU (Central Processing Unit) and GPU (Graphics Processing Unit)) that executes various calculation processes, and memory. The control unit 11 controls the entire information management system 10 based on a control program stored in the memory.

The control unit 11 has a message response function (chat function) and sends and receives interactive messages when accessed by the terminal device 40 using the third type ID (family ID). The control unit 11 analyzes the content of a message input by key input using the terminal device 40 from a family member with the third type ID, or a message obtained by converting voice data input by voice into text. Then, the control unit 11 generates a response to the message content, or electronic data such as file data related to the second type ID, such as event information, care record information, read image data of a care record sheet, etc., corresponding to the message content. (related information) is transmitted (provided) to the terminal device 40 of the originator. This file data can be generated from data such as read image data of a care record sheet stored in the first storage unit 13.

This message response function may be realized using a rule base in which questions and answers are prepared in advance. In this case, a screen displaying a plurality of menus may be presented, and the response may be made based on the item selected from the menus. Alternatively, the message history may be managed for each type 3 ID and reflected in the response. Alternatively, part or all of this response function may be realized by AI using a trained model such as a neural network. Some or all of these functions may be realized by using a BOT platform provided by a commercial operator.

(Communication Department 12)
The communication unit 12 has a function of communicating with other devices via a network. The communication unit 12 functions as a reception unit 121 and a transmission unit 122. The reception unit 121 accepts access from other devices via the network. The control unit 11 performs authentication processing in cooperation with the reception unit 121. In the authentication process, login ( access). The transmitting unit 122 also transmits and provides related information, which will be described later, as a response to the access.

(Event information transmission process)
(First embodiment)
Next, with reference to FIGS. 5 to 7, event information transmission processing performed by the information management system 10 according to the first embodiment will be described. FIG. 5 is a diagram showing event information transmission processing by the BOT function of the information management system 10.

(Step S1)
The event information is transmitted to the information management system 10 by access using the first type ID (facility ID) of the terminal device 30 of the nursing care facility. The transmitted event information is input by a staff member operating the terminal device 30, as described below.

6A and 6B are examples of operation screens for event information registration displayed on the terminal device 30, and are displayed using a web API provided by the information management system 10 or an input application running on the terminal device 30. be done.

Two events e1 and e2 are displayed on the operation screen d31 in FIG. 6A. These events have already been registered in the first storage unit 13. These events are composed of event information. The event information includes the event period (date, day of the week, time), event location, title, explanatory text (content) explaining the event, and image files related to the event. Further, the event information includes event attribute information (type, etc.) and a first type ID (facility ID or facility name (nursing facility x)). The event period (event period) may be held over multiple days.

Events include "general events" held in the entire facility, and "individual events" held in a portion of the entire facility, for example, one or more units. As an example of an individual event, for example, in a large-scale facility, a birthday party may be held in one or more units. Furthermore, the events may include events in which the cared person's family also participates, and "level-specific events" in which participants differ depending on the level of support and care required by the caregiver. . For example, events such as walking outside the facility, rehabilitation training events, etc. If the former is the case, participation will be restricted to those with a high level of support/care requirement, and if the latter, participation will be restricted only to those whose support/care requirement is above a certain level. Furthermore, events that require reservations for participation may be included. For example, if the event requires participation fees such as transportation expenses and admission fees, reservations for participation will be accepted.

In FIG. 6A, "whole facility" is selected as the event type (attribute information) using the pull-down button b11, so the whole event is displayed. When adding a new event, the staff member or the like operates the add button b12. As a result, an input screen d311 for event information registration shown in FIG. 6B is displayed as a pop-up on the terminal device 30. The staff etc. can set and input each of the above-mentioned items of event information through the input screen d311. Further, by using the pull-down button b21, one of "general event", "individual event", and "level-based event" can be set as event attribute information. When the input is completed, the input contents are confirmed by operating the registration button b20, the input event information is transmitted from the terminal device 30 to the information management system 10, and the screen returns to the operation screen d31. Note that, as shown in FIG. 6A, an upper limit on the number of events to be made public may be set. As will be described later, this is to prevent the amount of transmission from becoming excessive since event information for a plurality of events in the public state is transmitted at the same time (FIG. 7).

(Step S2)
The control unit 11 of the information management system 10 registers the event information received by the reception unit 121 in the first storage unit 13.

(Step S3)
In order to publish a newly added event, a staff member or the like can make a request to publish the event by operating the publishing buttons b13 and b14 on the operation screen d31 in FIG. 6A. On the operation screen d31, the event e1 is already in the public state, and the event e2 is in the private state. When the button b14 is operated by a staff member or the like, the terminal device 30 transmits a request to publish the event e2 to the information management system 10.

(Step S4)
The information management system 10 makes the event information of the event public in response to the disclosure request received by the reception unit 121 in step S3. Specifically, the event is made public to users (family members) of the third type ID associated with the care receiver (second type ID) corresponding to the attribute information included in the event information. In other words, it is published with viewing authority granted. For example, if the attribute information is "general event", the third type of users associated with all care recipients in the facility are granted viewing authority and made public. Then, along with this disclosure process, a disclosure notification, that is, a notification to the effect that the disclosure has been made to the user with the third type ID is performed.

Note that the publication notification process is performed immediately upon receiving a publication request from the terminal device 30, but may be performed at a preset time. For example, using the pull-down button b15 in FIG. 6A, a staff member or the like who accesses using the first type ID can set the transmission time (notification time). After receiving the disclosure request, the information management system 10 issues a disclosure notification at the set time. In nursing care settings, staff and others work in 24-hour shifts, so disclosure requests may be made in the middle of the night. This is because there is a risk of causing trouble. Furthermore, by issuing a disclosure notification at a fixed time during the day, family members have more opportunities to view the published content data.

FIG. 7 is an example of a message displayed on the mobile terminal (terminal device 402). A chat application (message application) operates on the terminal device 402. The operation screen d41 on the left is an example of a notification message automatically sent by the BOT function of the control unit 11 in response to the publication notification in step S4. This terminal device 402 is used by a family member of a care recipient, and the displayed message reads, "A new event has been published." This notification message is sent when a certain event is set from private to public. For example, a staff member or the like is notified in response to a disclosure request in response to operating the button b14 on the operation screen d31 in FIG. 6A.

(Step S5)
Here, the cared person's family makes a viewing request. For example, as shown in the operation screen d42 on the right side of FIG. 7, by sending a message m1, the cared person's family makes a viewing request to the information management system 10 through access using the third type ID. For example, the viewing request message m1 may be transmitted by arranging a viewing request button on the operation screen d41 and operating the button.

(Step S6)
The control unit 11 notifies (sends) event information as content data to the user (family member) of the third type ID who is the sender using the transmitting unit 122 to provide the event information. On the operation screen d42, event information is displayed in a message m2. In addition, in the example of the operation screen d42, event information of all events in the public state (corresponding to events e1 and e2 in FIG. 6A) for which viewing authority has been granted to the destination user at the time of sending the message m2 is shown. are sent together. That is, the other event (event e1) that was already in the public state is also made public at the same time. The user can view other event information by scrolling left and right on the operation screen d42.

In this way, the care information transmission system according to the first embodiment includes a reception section that accepts access via a network, and a reception section that receives access by using the first type of identification information used in the facility where the person to be cared for is located. The reception unit receives event information regarding an event held at the facility, and the control unit stores the event information received by the reception unit in the storage unit. The event information is registered, the event information is made public, and the transmission unit notifies the user of the third type identification information associated with the second type identification information of the person to be cared for at the facility. In this way, events held at the facility can be easily disclosed and notified to families, and the load on staff can be reduced.

In particular, in this embodiment, event information is made public in response to a public request made by the first type ID that registered the file, and a notification to the effect that the event information has been made public is issued. That is, the publication is performed in two stages: registration and publication. This can prevent erroneous distribution of event information.

In addition, by receiving a notification that a file has been published through a notification message by a so-called chat application running on a mobile terminal (terminal device 402) and accepting a request to send the file, the third type ID that received the notification is sent. Users (families) using the can easily access event information.

(Second embodiment)
Next, a second embodiment will be described with reference to FIGS. 8 and 9. In the first embodiment, the process of notifying the families of all care recipients of the facility with event information has been described using an event whose event information attribute is "general event" as an example. In the second embodiment described below, notification processing is performed according to the attributes of each type.

FIG. 8 shows an example of an input screen d312 for inputting event information used in the second embodiment. This figure corresponds to the input screen d311 in FIG. 6B, but in addition to the pull-down button b21, pull-down buttons b22 and b23 are arranged for inputting event attribute information.

As described above, using the pull-down button b21, the staff member or the like can set the event type as "general event," "individual event," or "level-based event" as event attribute information. With the added pull-down button b22, either "participation reservation required" or "participation reservation not required" can be set as attribute information regarding the presence or absence of a reservation. Furthermore, with the pull-down button d23, one of "care recipient," "care recipient and family," or "family" can be set for the participant as attribute information. Note that when an individual event is selected as the event type, one or more target units can be further set (using a button not shown). For example, "1F East" (see table 64 in FIG. 4) can be set as the unit. Similarly, when a level-based event is selected, it is possible to further set (by using a button not shown) the target level of the level of support required and the level of care required as participants. When the input of these attribute information and each item is completed, the input contents are confirmed by operating the registration button b20, the input event information is transmitted from the terminal device 30 to the information management system 10, and the operation Return to screen d31.

FIG. 9 is a diagram showing event information transmission processing performed by the information management system 10 according to the second embodiment. The process shown in FIG. 5 is a process subsequent to step S3 in FIG. 5, and is performed following a disclosure request after event information input through the operation screen d31 as shown in FIG. 8 is registered. Step S40 (steps S41 to S46) within the dashed line frame in FIG. 9 corresponds to the publication notification process of step S4 in FIG.

(Step S41)
In response to receiving the disclosure request, the control unit 11 sequentially performs the processing from step S41 on one or more events in the disclosure state. In step S41, the control unit 11 determines event attribute information (type) for the event to be determined (hereinafter referred to as "target event"). If the attribute information is a "general event", the process advances to step S42, if it is an "individual event", the process advances to step S43, and if it is a "level-based event", the process advances to step S44.

(Step S42)
The control unit 11 publishes the target event to the families of all care recipients in the facility. In other words, these family members are given viewing authority to the target event.

(Step S43)
The control unit 11 discloses the target event to the family of the cared person belonging to the target unit. In other words, these family members are given viewing authority to the target event.

(Step S44)
The control unit 11 acquires the support level and care level of the care recipient at the facility from the table 66 stored in the first storage unit 13 .

(Step S45)
The control unit 11 extracts care recipients that match the target level of the event attribute information. For example, if the level of care requirement level 1 or higher is the target level, care recipients matching that level are extracted. The control unit 11 publishes the target event for the extracted family of the care recipient. In other words, these family members are given viewing authority to the target event.

(Step S46)
The control unit 11 notifies the families targeted for disclosure that the target event has been disclosed.

(Steps S50, S60)
Here, the information management system 10 performs the same processing as steps S5 and S6 in FIG. 5 described above. That is, in response to receiving a viewing request from a family member to be made public, the event information is transmitted and provided as content data to the user (family member) of the third type ID of the sender. At this time, if the attribute information is for an event that indicates "reservation required," a reservation form will also be provided.

(Step S70)
Furthermore, if the family member wishes to participate in the event sent in step S60 that requires a reservation, the family makes a reservation for participation. Specifically, the family transmits a participation reservation request to the information management system 10 through the terminal device 40. These reservations include not only family members' participation reservations but also cared person's participation reservations. For example, if an event in which only the cared person participates incurs expenses, the cared person's family can make a reservation for the cared person's participation, thereby approving the family's handling of the expenses. Furthermore, there are cases where the family wishes to cancel the reservation for an event for which they have made a reservation, and the family can also send this cancellation request to the information management system 10. These reservations for participation or cancellation of participation can be made in response to the event information release notification message. For example, it is preferable to display a reservation form and accept participation reservations and cancellations through a notification message as shown in FIG.

When the information management system 10 receives a participation reservation or a request to cancel the reserved participation from the family member through access using the third type ID (YES), the information management system 10 advances the process to step S80. If not received, the process ends (end).

(Step S80)
The information management system 10 updates the reservation list for the corresponding event according to the received reservation details.

In this way, the information management system 10 according to the second embodiment can easily disclose and notify the family members of cared people who are eligible to participate, depending on the type of event (general event, individual event, event by level). This, in turn, can reduce the burden on staff.

Furthermore, in the information management system 10, reservations for participation in an event or cancellation thereof can be made in response to a notification of publication. This can further reduce the burden on staff compared to the previous situation where staff accepted requests over the phone or via paper.

(Modified example)
Next, a modification will be described with reference to FIG. 10. In the information management system 10 according to the modified example, registered events are managed based on information about their holding period. The following processing is performed at a predetermined cycle, such as every day.

(Step S91)
The control unit 11 acquires information on the holding period of the event stored and registered in the first storage unit 13. Note that in this process, only events to be published may be targeted.

(Step S92)
The control unit 11 determines whether there is an event within a predetermined period (before the predetermined period) until the event period. For example, if the predetermined period is one day, if there is an event within one day (the previous day) from the event period (YES), the process advances to step S93. If there is no event within the predetermined period (NO), the process advances to step S94. Note that in the case of an event that is held over multiple days, this determination is made based on the first day (start time).

(Step S93)
The control unit 11 sends a reminder to the family member who is the subject of disclosure. Specifically, a reminder message will be sent to users (families) with type 3 ID to inform them that the event date is coming soon. Note that if the event requires a reservation to participate, a reminder may be sent only to the family members who have made a reservation to participate. Note that this includes not only reminder notifications for events scheduled to be attended by family members themselves, but also reminders for events reserved by the family, in which only the cared person will participate.

(Step S94)
If there is an event for which the event period (last day) has passed (YES), the control unit 11 advances the process to step S95; if not (NO), the control unit 11 ends the process (END).

(Step S95)
The control unit 11 makes the event private. Note that the event made private may be deleted from the first storage unit 13 after a certain period of time has elapsed.

In this way, in the modified example, the information management system 10 can increase the event recognition rate of the family members who received the notification by providing a reminder based on the event period. Additionally, by sending reminders to family members who have made reservations, you can prevent them from forgetting to participate in the reserved event. Furthermore, by making events private after their holding period has passed, family members can see only the events they need, making it easier to check the events they need. This is particularly useful when performing a process in which, in response to a new event being registered and published, other events that are in the public state also transmit event information at the same time (for example, the operation screen shown in Figure 7). d42).

The configuration of the information management system 10 explained above is the main configuration explained in explaining the features of the above-described embodiment, and is not limited to the above-mentioned configuration, and can be modified in various ways within the scope of the claims. can. Moreover, the configuration provided in the general information management system 10 is not excluded.

(Other variations)
For example, the modification shown in FIG. 10 may be applied to the first and second embodiments. As explained in Figure 7 etc., when a new event is published, event information of other events is also transmitted; however, event information of the newly published target event is not limited to this. It is also possible to send only the Furthermore, in the first embodiment etc., an example was explained in which event information is notified by receiving a viewing request from a family member (step S5 in FIG. 5, message m1 in FIG. 7, etc.). It is also possible to omit S5 and simply notify the event information by making it public without waiting for a viewing request. That is, event information may be included in the notification that the information has been published. Furthermore, in this case, it is preferable to transmit only event information for events that have newly become public. Similarly, step S3 of the disclosure request from staff or the like may be omitted, and the information may be disclosed at the same time as registration.

Furthermore, the means and methods for performing various processes in the information management system 10 according to the embodiments described above can be realized by either a dedicated hardware circuit or a programmed computer. The program may be provided on a computer-readable recording medium such as a USB memory or a DVD (Digital Versatile Disc)-ROM, or may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is usually transferred and stored in a storage unit such as a hard disk. Further, the above program may be provided as a standalone application software, or may be incorporated into the software of the device as a function.

10 Information management system 11 Control unit 12 Communication unit 121 Reception unit 122 Transmission unit 13 First storage unit (for content management)
14 Second storage section (for message management)
30, 301, 302, 30n terminal equipment (for facilities)
40, 401, 402 Terminal device (for family use)

Claims (22)

A reception section that accepts access via the network,
A second type of identification information of a person to be cared for in a facility, a first type of identification information used in the facility where the person to be cared for is present, and a family member of the person to be cared for associated with the second type of identification information. a storage unit that stores third type identification information regarding the information, and registers information received by the reception unit through access using the first type identification information;
a control unit;
comprising a transmitting section;
The reception unit receives event information regarding an event to be held at the facility and in which a plurality of care recipients at the facility participate, through access using the first type of identification information ;
The control unit registers the event information received by the reception unit in the storage unit, publishes the event information, and sends each of the second type identification information of the plurality of care recipients by the transmission unit. Notifying the event information to the user of the associated third type of identification information;
Information management system. The information management system according to claim 1, wherein the event is an event in which the care recipient participates and a family member of the care recipient does not participate. The reception unit accepts a public request for the event,
The information management system according to claim 1 or 2, wherein the control unit publishes the event information and provides the notification in response to receiving the disclosure request. The event information includes information about the holding period of the event,
The information management system according to claim 3 , wherein the control unit makes the event information private as the event period elapses. The facility has a plurality of units to which a plurality of the care recipients belong,
The event includes an overall event held in the entire facility and an individual event held in each unit,
When the reception unit receives the registration of the event information regarding the individual event, the control unit transmits the second type of identification of the care recipient belonging to the unit of the individual event by the transmission unit. The information management system according to any one of claims 1 to 4 , wherein the event information is notified to a user of the third type of identification information associated with the information. The person to be cared for is a cared person,
The event includes a level-based event in which participants differ depending on the level of support required and care required of the cared person,
When the reception unit receives the registration of the event information regarding the level-based event, the control unit causes the transmission unit to associate the event information with the second type of identification information of the participant according to the level. The information management system according to any one of claims 1 to 5 , wherein the event information is notified to a user of the third type of identification information. The event information includes information about the holding period of the event,
The controller according to any one of claims 1 to 6 , wherein the transmitter notifies the user of the third type of identification information of a reminder a predetermined period before the event period. information management system. The notification is performed by a notification message to the user of the third type of identification information,
The control unit receives a reservation for participation in the event by a user of the third type of identification information and a cancellation of the reservation for participation in response to the notification message. information management system. The notification is performed by a notification message to the user of the third type of identification information,
In response to the notification message, the control unit makes a reservation for participation in the event of the care recipient of the associated second type of identification information by the user of the third type of identification information, and the reservation for participation. The information management system according to claim 8 , wherein the information management system accepts cancellation of. The event information includes information about the holding period of the event,
9. The control unit causes the transmission unit to send a reminder to the user of the third type of identification information who has accepted the participation reservation a predetermined period before the event period. The information management system according to item 9 . The notification is performed by a notification message to the user of the third type of identification information,
The information management system according to any one of claims 1 to 10 , wherein the transmitter transmits the notification message at a preset notification time. A reception section that accepts access via the network,
a transmitting unit , second type identification information of a care recipient in a facility, first type identification information used in the facility where the care recipient is located, and the care associated with the second type identification information. A control program for controlling an information management system comprising: a storage unit storing third type identification information regarding a subject's family ;
(a) receiving, by the reception unit, event information regarding an event to be held at the facility and attended by a plurality of care recipients at the facility, through access using the first type of identification information;
a step (b) of registering the event information received in the step (a) in the storage unit;
The event information registered in the step (b) is made public, and the user of the third type of identification information associated with each of the second type of identification information of the plurality of care recipients in the facility by the transmission unit. A control program for causing a computer to execute processing including a step (c) of notifying the event information. 13. The control program according to claim 12, wherein the event is an event in which the care recipient participates and a family member of the care recipient does not participate. The process further includes a step (d) of receiving a public request for the event by the reception unit,
14. The control program according to claim 12, wherein, in the step (c), the event information is published and notified in response to accepting the publication request in the step (d). The event information includes information about the holding period of the event,
15. The control program according to claim 14 , wherein the process further includes a step (e) of making the event information private as the event period elapses. The facility has a plurality of units to which a plurality of the care recipients belong,
The event includes an overall event held in the entire facility and an individual event held in each unit,
In the step (c), when the reception unit receives the registration of the event information regarding the individual event, the transmission unit sends the second type of care recipient belonging to the unit of the individual event. 16. The control program according to claim 12 , wherein the control program notifies the event information to a user of the third type of identification information associated with the identification information. The person to be cared for is a cared person,
The event includes a level-based event in which participants differ depending on the level of support required and care required of the cared person,
In the step (c), when the reception unit receives the registration of the event information regarding the level-based event, the transmission unit transmits the second type of identification information of the participant according to the level. 17. The control program according to claim 12 , wherein the control program notifies the user of the third type of identification information associated with the event information. The event information includes information about the holding period of the event,
13. The process further comprises a step (f) of sending a reminder notification to the user of the third type of identification information by the transmitter a predetermined period before the event period. 18. The control program according to any one of Item 17 . The step (c) is performed by a notification message to the user of the third type of identification information,
The processing further includes a step (g) of accepting a reservation for participation in the event by the user of the third type of identification information and a cancellation of the reservation for participation in response to the notification message. 19. The control program according to any one of Item 18 . The notification is performed by a notification message to the user of the third type of identification information,
In the step (g), in response to the notification message, the user of the third type of identification information makes a reservation for the care recipient of the associated second type of identification information to participate in the event, and The control program according to claim 19 , which accepts cancellation of participation reservation. The event information includes information about the holding period of the event,
The process further includes a step (h) of causing the transmission unit to send a reminder to the user of the third type of identification information who has accepted the participation reservation a predetermined period before the event period. , the control program according to claim 19 , or claim 20 . The notification is performed by a notification message to the user of the third type of identification information,
22. The control program according to claim 12 , wherein in step ( c ), the notification message is transmitted at a preset notification time.