JP6813403B2 - Medical / long-term care information management method, medical / long-term care information management system and medical / long-term care information management program - Google Patents

Description

The present invention relates to a medical / nursing information management method, a medical / nursing information management system, and a medical / nursing information management program. Further, for example, one for each target person (patient, long-term care recipient) of a medical / nursing service. The above groups are generated to facilitate communication between group members of each group using a timeline, and medical information and long-term care information of the target person posted on the timeline in the form of a message or a file. A medical / long-term care information management method that allows the range of people who can access the medical information or long-term care information of the target person to be arbitrarily set as necessary, even if the information is shared while protecting its privacy. , The system and its program.

The applicant creates one or more groups for each target person (patient, long-term care recipient) of medical / long-term care services, and facilitates communication between group members of each group using a timeline. , A patent application has been filed for a medical / long-term care support system that shares medical information and long-term care information of the target patient posted on the timeline in the form of messages and files while protecting their privacy (Patent Document 1). reference). In this system, one or more groups can be generated for each target person (patient, long-term care recipient) of the medical / long-term care service, but in order to share the medical information and long-term care information of the target person while protecting their privacy, each group. There is an operational rule that the target person, that is, the patient or the person requiring long-term care, who belongs to the group is limited to one person. This is to ensure that medical information and long-term care information of multiple patients and long-term care recipients are never mixed in the same group, and this rule is strictly adhered to.

In the medical / long-term care support system of Patent Document 1, the user terminal (use of medical / long-term care service) can browse and input / output medical information and long-term care information about individual patients or persons requiring long-term care, send / receive messages, etc. via a communication network. By making it feasible on the terminal of the person, medical professionals and long-term care workers of various occupations such as doctors, nurses, nutritionists, care managers, helpers, etc., who have different specialized fields, cooperate with each other and patients and need long-term care. It is possible to support people so that they can provide better quality medical services and long-term care services.

In addition, Non-Patent Document 1 is provided with a timeline, a bulletin board, a shared folder, etc. for each group, and messages and files posted on the timeline can be viewed and shared among group members of the group. , A groupware called "Cybozu live" is disclosed. This groupware is provided by Cybozu, Inc. and can be used in mobile terminals and personal computers. Information posted in the form of messages or files on the timeline of any group can only be viewed by members of that group. Similarly, files uploaded to a shared folder in any group can only be viewed by members of that group. In this groupware, unlike the medical / long-term care support system of Patent Document 1, a group can be freely created as needed.

JP 2015-15010

https://live.cybozu.co.jp/overview.html/

However, it has been found that the medical / long-term care support system of Patent Document 1 described above has a problem that cannot be dealt with. That is, in the field of medical care and long-term care, there is a lot of medical / long-term care information that we want to share in units smaller than the group unit created for each patient or long-term care recipient, and the information sharing unit often fluctuates. The problem is that the system cannot handle the situation even though there is a situation.

Specifically, in the medical / long-term care support system of Patent Document 1, one or more groups are created for each individual patient or long-term care recipient according to the theme such as a disease. A timeline for sharing information among all members (patients, patient-related persons, medical staff, care workers, etc.) belonging to each group (hereinafter, also referred to as all member timelines) and medical staff belonging to the group. A timeline for sharing information only with medical staff and care workers (hereinafter also referred to as the medical / care worker timeline) is created and used for communication between group members of each group. Group members of each group usually include patients and long-term care recipients, as well as a large number of doctors and nurses belonging to multiple medical and long-term care facilities, as well as patients and long-term care recipients. Since pharmacists, care managers, etc. are included, for example, information that only medical professionals belonging to the same medical facility want to share, information that only nurses or physiotherapists need to share, etc. Information that you want to share with a limited number of members (ie, a smaller number of people) than members often occurs. However, it is impossible to realize such information sharing with the medical / long-term care support system of Patent Document 1. This is because the system can generate one or more groups for each target person (patient, long-term care recipient) of medical / long-term care services, but the target person (patient, long-term care recipient) associated with each group is This is because there is a strict operational rule that only one person can be created, so multiple groups cannot be created in duplicate for the same theme (disease, etc.) of the same patient or care recipient. For this reason, in this system, the range in which medical / long-term care information can be shared is limited to all medical / long-term care workers belonging to the same group and all group members including patients and patient-related persons. It will end up.

Further, in the medical / long-term care support system of Patent Document 1, all member timelines and medical / long-term care worker timelines are created, and the messages posted on each timeline and the files attached to those messages are each time. It can only be shared among members who have access to the line (ie, all healthcare professionals or all group members). For example, if a medical facility prepares a rehabilitation plan for a specific patient, only the medical staff belonging to the facility will consider it in advance, and then modify it appropriately to complete the final rehabilitation plan for all medical care and long-term care. Even if you want to make it available to workers and all group members, such a request cannot be realized by this system.

On the other hand, in the groupware called "Cybozu live" of Non-Patent Document 1, one or more groups can be freely created as needed, so that there is a problem like the medical / nursing care support system of Patent Document 1. Does not occur. This is because a new group may be created to include only those who want to share information as needed. However, this groupware attempts to share general information on a group-by-group basis, and each group is linked to a specific patient or a person requiring long-term care as in the medical / long-term care support system of Patent Document 1. Absent. For this reason, the group of Non-Patent Document 1 does not include the idea of sharing medical information and long-term care information of a specific patient or long-term care recipient among a limited number of people while protecting the privacy of that person. The ware is clearly different from the system of Patent Document 1.

The present invention has been made in consideration of the above-mentioned circumstances, and the purpose of the present invention is to create one or more groups for each target person (patient or long-term care recipient) of medical / long-term care services. Regardless of whether or not the target person (patient or long-term care recipient) associated with each group is limited to one person, the medical / long-term care information of the target person posted by identifying who the information is about The purpose of the present invention is to provide a medical / long-term care information management method, a system thereof, and a program thereof, which can arbitrarily set the range of accessible persons as needed.

Another object of the present invention is to centrally manage the access authority to the medical / long-term care information of the subject (patient or long-term care recipient) posted by specifying who the information is about for each subject. To provide a medical / long-term care information management method, a system thereof, and a program thereof that can share the medical / long-term care information among a limited number of people while protecting the privacy of the target person. is there.

Still other objects of the invention not specified herein will become apparent from the following description and accompanying drawings.

(1) The medical / long-term care information management method according to the first aspect of the present invention is
By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or long-term care recipient A method of managing the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of the long-term care service.
User identification information (for example, user ID) is assigned and stored for each user who uses the medical / nursing care service via the user terminal.
The service beneficiary identification information (for example, patient ID) is assigned to the patient or the care recipient as the user, and the service beneficiary identification information is stored in association with the user identification information.
Business worker identification information (for example, medical worker ID) is assigned to a medical worker or a care worker as the user, and the business worker identification information is stored in association with the user identification information.
In response to the instruction from the user terminal, a group having unique group identification information (for example, group ID) associated with the service beneficiary identification information is generated.
By selectively assigning one or more of the users to the group as group members in response to an instruction from the user terminal, the patient or the required person corresponding to the service beneficiary identification information related to the group. The medical / nursing information of the caregiver can be shared among the group members via the user terminal.
In response to an instruction from the user terminal, a secret room having unique room identification information (for example, room ID) associated with the group identification information is generated.
In response to an instruction from the user terminal, at least a part of the group members belonging to the group related to the secret talk room is selectively assigned to the secret talk room as room members, so that the group belongs to the group. The medical / long-term care information of the patient or the person requiring long-term care corresponding to the service beneficiary identification information can be shared among the room members via the user terminal.
The individual medical / nursing information of the patient or the person requiring long-term care, which is posted by specifying who the information is about, is the group identification information of the group to which the medical / nursing information is posted or the secret room. It is characterized in that it is stored in association with the room identification information of the above.

In the medical / long-term care information management method according to the first aspect of the present invention, a group having unique group identification information (for example, group ID) is generated in relation to the service recipient identification information (for example, patient ID), and the group is generated. By selectively assigning one or more of the users as group members, medical / long-term care information of the patient or the person requiring long-term care corresponding to the group can be transmitted between the group members via the user terminal. It can be shared with. Therefore, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the group can be shared among the group members belonging to the group via the user terminal.

Further, after generating a secret talk room having unique room identification information (for example, room ID) in relation to the group identification information, at least one of the group members belonging to the group related to the secret talk room. By selectively assigning the department to the secret talk room as a room member, medical / long-term care information of the patient or the person requiring long-term care corresponding to the group can be transmitted between the room members via the user terminal. Make it sharable. Therefore, the medical / nursing information of the patient or the person requiring long-term care corresponding to the group can be shared among the room members belonging to the secret talk room via the user terminal. .. Here, since the room member of the secret story room is at least a part of the group member, a part or all of the group member is selected as the room member as needed. Thereby, the range of persons who can access the medical / nursing information of the patient or the person requiring long-term care corresponding to the group can be easily changed.

Therefore, if necessary, the range of persons (accessible persons) who can access the individual medical / long-term care information of the target person (that is, the patient or the person requiring long-term care) posted by specifying who the information is about. Can be set arbitrarily. This can create one or more groups for each of the patients or care recipients who are the targets of the medical / long-term care service, but one subject (patient or care recipient) associated with each group. It is irrelevant with or without the limitation of being limited to.

Further, the individual medical / nursing information of the patient or the person requiring long-term care posted by specifying who the information is about is the group identification information or the secret of the group to which the medical / nursing information is posted. In order to store the information in association with the room identification information of the talk room, an accessible person for each of the medical / long-term care information is sent to the group member of the group to which the medical / long-term care information is posted or the room member of the secret talk room. It is set automatically. Therefore, the access authority to the medical / long-term care information of the target person (that is, the patient or the person requiring long-term care) posted by specifying who the information is about can be centrally managed for each target person. .. Further, this makes it possible to share the medical / long-term care information among a limited number of people while protecting the privacy of the target person.

(2) In a preferable example of the medical / long-term care information management method according to the first aspect of the present invention, a person who is a group member of the group related to the secret talk room but is not a room member of the secret talk room. Is set so as not to have access authority to the medical / long-term care information of the subject posted to the secret talk room.

(3) In another preferable example of the medical / long-term care information management method according to the first aspect of the present invention, when the secret talk room is generated, at least a part of the group members is designated as the room members. , The designated group member is automatically invited to the secret talk room to become the room member.

(4) In still another preferable example of the medical / long-term care information management method according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about. When the group is designated as the posting destination, all the group members of the group are stored as accessible persons to the medical / long-term care information, and when the secret talk room is designated, the secret talk room is specified. All the room members of the above are stored as accessible persons to the medical / long-term care information.

(5) In still another preferable example of the medical / long-term care information management method according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is , Posted in message format or file format to the timeline of the group or the timeline of the secret room, or a predetermined direct posting location provided separately from the timeline of the group and the secret room. Posted directly in file format to.

(6) In still another preferable example of the medical / long-term care information management method according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can view it, and when posted to the secret room, the room member of the posted secret room is posted. Only available for viewing.

(7) In still another preferable example of the medical / long-term care information management method according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can confirm the posted medical / long-term care information on the predetermined posted information list screen, and the posted information is addressed to the secret room. When posted, only the room member of the posted secret story room can confirm the posted medical / long-term care information on a predetermined posted information list screen.

(8) The medical / long-term care information management system according to the second aspect of the present invention is
By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or long-term care recipient A system that manages the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of the long-term care service.
A user identification information storage means (for example, a user information storage unit) that assigns and stores user identification information (for example, a user ID) to each user who uses the medical / nursing care service via the user terminal.
Service beneficiary identification information storage that assigns service beneficiary identification information (for example, patient ID) to the patient or the care recipient as the user and stores the service beneficiary identification information in association with the user identification information. Means (eg patient information storage) and
Business worker identification information that assigns business worker identification information (for example, medical worker ID) to a medical worker or care worker as the user and stores the business worker identification information in association with the user identification information. Means of storage (for example, medical staff information storage department) and
A group management means (for example, a group management unit) that generates a group having unique group identification information (for example, a group ID) in association with the service beneficiary identification information in response to an instruction from the user terminal.
By selectively assigning one or more of the users to the group as group members in response to an instruction from the user terminal, the patient or the required person corresponding to the service beneficiary identification information related to the group. Group member selection means (for example, group management department) that enables sharing of caregiver medical / nursing information among the group members via the user terminal, and
With a secret talk room management means (for example, a secret talk room management unit) that generates a secret talk room having unique room identification information (for example, room ID) in association with the group identification information in response to an instruction from the user terminal. ,
In response to an instruction from the user terminal, at least a part of the group members belonging to the group related to the secret talk room is selectively assigned to the secret talk room as room members, so that the group belongs to the group. A room member selection means (for example, a user management unit) that enables sharing of medical / long-term care information of the patient or the care recipient corresponding to the service recipient identification information among the room members via the user terminal. )When,
The individual medical / nursing information of the patient or the person requiring long-term care, which is posted by specifying who the information is about, is the group identification information of the group to which the medical / nursing information is posted or the secret room. It is characterized in that it is provided with a posted information storage means (for example, a secret story room management unit and a file management unit) that stores information in association with the room identification information.

In the medical / long-term care information management system according to the second aspect of the present invention, the group identification information (for example, patient ID) unique to the service recipient identification information (for example, patient ID) is used by the group management means and the group member selection means. For example, by generating a group having a group ID) and selectively assigning one or more of the users to the group as group members, medical / nursing information of the patient or the person requiring long-term care corresponding to the group. Can be shared among the group members via the user terminal. Therefore, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the group can be shared among the group members belonging to the group via the user terminal.

Further, after the secret story room management means and the room member selection means generate a secret story room having unique room identification information (for example, room ID) in relation to the group identification information, the secret story is described. By selectively assigning at least a part of the group members belonging to the group related to the room to the secret room as room members, medical care / nursing care of the patient or the person requiring long-term care corresponding to the group. Information can be shared among the room members via the user terminal. Therefore, the medical / nursing information of the patient or the person requiring long-term care corresponding to the group can be shared among the room members belonging to the secret talk room via the user terminal. .. Here, since the room member of the secret story room is at least a part of the group member, a part or all of the group member is selected as the room member as needed. Thereby, the range of persons who can access the medical / nursing information of the patient or the person requiring long-term care corresponding to the group can be easily changed.

Therefore, if necessary, the range of persons (accessible persons) who can access the individual medical / long-term care information of the target person (that is, the patient or the person requiring long-term care) posted by specifying who the information is about. Can be set arbitrarily. This can create one or more groups for each of the patients or care recipients who are the targets of the medical / long-term care service, but one subject (patient or care recipient) associated with each group. It is irrelevant with or without the limitation of being limited to.

Further, the individual medical / nursing information of the patient or the person requiring long-term care, which is posted by specifying who the information is about by the posted information storage means, is sent to the group to which the medical / nursing information is posted. In order to store the group identification information or the room identification information of the secret story room in association with the room identification information, an accessible person for each of the medical / long-term care information is the group member of the group or the secret story to which the information is posted. It is automatically set to the room member of the room. Therefore, the access authority to the medical / long-term care information of the target person (that is, the patient or the person requiring long-term care) posted by specifying who the information is about can be centrally managed for each target person. .. Further, this makes it possible to share the medical / long-term care information among a limited number of people while protecting the privacy of the target person.

(9) In a preferable example of the medical / long-term care information management system according to the second aspect of the present invention, a person who is a group member of the group related to the secret talk room but is not a room member of the secret talk room. Is set so as not to have access authority to the medical / long-term care information of the subject posted to the secret talk room.

(10) In another preferable example of the medical / long-term care information management system according to the first aspect of the present invention, when the secret talk room is generated, at least a part of the group members is designated as the room members. , The designated group member is automatically invited to the secret talk room to become the room member.

(11) In still another preferable example of the medical / long-term care information management system according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about. When the group is specified as the posting destination, all the group members of the group are stored as accessible persons to the medical / long-term care information, and when the secret room is specified, the secret room is specified. All the room members of the above are stored as accessible persons to the medical / long-term care information.

(12) In still another preferred example of the medical / long-term care information management system according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is Posting in message format or file format to the timeline of the group or the timeline of the secret room, or a predetermined direct posting location provided separately from the timeline of the group and the secret room. Posted directly in file format to.

(13) In still another preferable example of the medical / long-term care information management system according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can view it, and when posted to the secret room, the room member of the posted secret room is posted. Only available for viewing.

(14) In still another preferred example of the medical / long-term care information management system according to the first aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can confirm the posted medical / long-term care information on the predetermined posted information list screen, and the posted information is addressed to the secret room. When posted, only the room member of the posted secret story room can confirm the posted medical / long-term care information on a predetermined posted information list screen.

(15) The medical / long-term care information management program according to the third aspect of the present invention is
By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or long-term care recipient A program that manages the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of long-term care services.
A process of assigning and storing user identification information (for example, a user ID) to an individual user who uses the medical / nursing care service via the user terminal.
A process of assigning service beneficiary identification information (for example, patient ID) to the patient or the care recipient as the user, and storing the service beneficiary identification information in association with the user identification information.
A process of assigning a business worker identification information (for example, a medical worker ID) to a medical worker or a long-term care worker as a user and storing the business worker identification information in association with the user identification information.
A process of generating a group having unique group identification information (for example, a group ID) in relation to the service beneficiary identification information in response to an instruction from the user terminal.
By selectively assigning one or more of the users to the group as group members in response to an instruction from the user terminal, the patient or the required person corresponding to the service beneficiary identification information related to the group. A process that enables the caregiver's medical / nursing information to be shared among the group members via the user terminal, and
A process of generating a secret room having unique room identification information (for example, a room ID) in relation to the group identification information in response to an instruction from the user terminal.
In response to an instruction from the user terminal, at least a part of the group members belonging to the group related to the secret talk room is selectively assigned to the secret talk room as room members, so that the group belongs to the group. A process that enables the medical / nursing information of the patient or the person requiring long-term care corresponding to the service recipient identification information to be shared among the room members via the user terminal.
The individual medical / long-term care information of the patient or the person requiring long-term care, which is posted by specifying who the information is about, is the group identification information of the group to which the medical / long-term care information is posted or the secret story room. It is characterized in that a computer executes a process of storing the room identification information in association with the room identification information.

In the medical / long-term care information management program according to the third aspect of the present invention, the information about whom is specified and posted for the same reason as the medical / long-term care information dissociation method according to the first aspect of the present invention described above. The range of persons (accessible persons) who can access the individual medical / nursing information of the target person (that is, the patient or the person requiring long-term care) can be arbitrarily set as needed. This can create one or more groups for each of the patients or care recipients who are the targets of the medical / long-term care service, but one subject (patient or care recipient) associated with each group. It is irrelevant with or without the limitation of being limited to.

Further, the individual medical / nursing information of the patient or the person requiring long-term care posted by specifying who the information is about is the group identification information or the secret of the group to which the medical / nursing information is posted. In order to store the information in association with the room identification information of the talk room, an accessible person for each of the medical / long-term care information is sent to the group member of the group to which the medical / long-term care information is posted or the room member of the secret talk room. It is set automatically. Therefore, the access authority to the medical / long-term care information of the target person (that is, the patient or the person requiring long-term care) posted by specifying who the information is about can be centrally managed for each target person. .. Further, this makes it possible to share the medical / long-term care information among a limited number of people while protecting the privacy of the target person.

(16) In a preferred example of the medical / long-term care information management program according to the third aspect of the present invention, a person who is a group member of the group related to the secret talk room but is not a room member of the secret talk room. Is set so as not to have access authority to the medical / long-term care information of the subject posted to the secret talk room.

(17) In another preferred example of the medical / long-term care information management program according to the third aspect of the present invention, when the secret talk room is generated, at least a part of the group members is designated as the room members. , The designated group member is automatically invited to the secret talk room to become the room member.

(18) In yet another preferred example of the medical / long-term care information management program according to the third aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about. When the group is specified as the posting destination, all the group members of the group are stored as accessible persons to the medical / long-term care information, and when the secret room is specified, the secret room is specified. All the room members of the above are stored as accessible persons to the medical / long-term care information.

(19) In yet another preferred example of the medical / long-term care information management program according to the third aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is Posting in message format or file format to the timeline of the group or the timeline of the secret room, or a predetermined direct posting location provided separately from the timeline of the group and the secret room. Posted directly in file format to.

(20) In still another preferred example of the medical / long-term care information management program according to the third aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can view it, and when posted to the secret room, the room member of the posted secret room is posted. Only available for viewing.

(21) In still another preferred example of the medical / long-term care information management program according to the third aspect of the present invention, the medical / long-term care information of the patient or the person requiring long-term care posted by specifying who the information is about is When posted to the group, all the group members of the posted group can confirm the posted medical / long-term care information on the predetermined posted information list screen, and the posted information is addressed to the secret room. When posted, only the room member of the posted secret story room can confirm the posted medical / long-term care information on a predetermined posted information list screen.

In the present specification, "medical / long-term care information" is information posted on a timeline created for each group or secret story room in the form of a message or in the form of a file, and the group and secret story. Information posted directly to a predetermined direct posting location provided separately from the room timeline, and refers to medical or long-term care. In other words, it refers to information related to medical care or long-term care of individual patients or long-term care recipients who are the target of medical / long-term care services. For example, medical examination result information described in the medical records of patients and persons requiring nursing care, roentgen photograph information, image information by CT and MRI inspection devices, plans, reports, minutes, etc. related to treatment, nursing care, medication, rehabilitation, etc. There are text information and various files in which such information is stored. In addition to these, for example, there are data files of various applications, various files such as photographs, still images, and moving images, and information related to those files. Information posted on the timeline in the form of a message is also included in "medical / long-term care information".

As used herein, "posting" means delivering arbitrary information in message or file format to the group or the secret room. The information may be posted to the timeline of the group or the timeline of the secret room, or the group or the secret room without going through the timeline of the group and the secret room. It may be a predetermined posting destination (direct posting destination) provided in.

The medical / long-term care information management method according to the first aspect of the present invention, the medical / long-term care information management system according to the second aspect of the present invention, and the medical / long-term care information management program according to the third aspect of the present invention are (a). One or more groups can be created for each target person (patient or long-term care recipient) of medical / long-term care services, but the limitation is that the target person (patient or long-term care recipient) associated with each group is limited to one person. The effect is that the range of people who can access the medical / long-term care information of the target person posted by specifying who the information is, regardless of the presence or absence, can be arbitrarily set as needed. b) The access authority to the medical / long-term care information of the target person (patient or long-term care recipient) posted by specifying who the information is can be centrally managed for each target person. There is an effect that the medical / long-term care information can be shared among a limited number of people while protecting the privacy of the target person.

It is a conceptual diagram which shows the usage state of the medical support system which operates in cooperation with the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the mutual relationship of a patient, a patient-related person, a medical worker and a medical-related facility participating in the medical support system shown in FIG. It is a functional block diagram which shows the internal structure of the medical support system shown in FIG. In the figure which shows the configuration example of the table used in the medical support system shown in FIG. 1, (a) is a user table, (b) is a patient table, (c) is a medical worker table, and (d) is medical care. It is a related facility table. In the figure which shows the configuration example of the table used in the medical support system shown in FIG. 1, (a) is a medical facility patient table, (b) is a disease table, (c) is a group table, and (d) is. It is a group participation table. In the figure which shows the configuration example of the table used in the medical support system shown in FIG. 1, (a) is an invitation request table, (b) is a timeline table, (c) is a medical information sharing rule table, (d). ) Is the NFC terminal management rule table. It is a figure which shows the configuration example of the table used in the medical support system shown in FIG. 1, (a) is a message transmission reservation table, (b) is a patient attribute table. It is explanatory drawing which shows the relationship between all the tables used in the medical support system shown in FIG. It is explanatory drawing which shows the relationship between the display area generated for each patient-specific disease of the timeline formed in each group by the medical support system shown in FIG. 1 and the person who can access the display area. It is a functional block diagram which shows the outline of the medical support system shown in FIG. 1 and the internal structure of the medical information management system which concerns on one Embodiment of this invention which operates in cooperation with the system. It is a functional block diagram which shows the detail of the internal structure of the medical information management system which concerns on one Embodiment of this invention. A secret story room created by the medical information management system according to the embodiment of the present invention, its affiliated members and a timeline, and a group created by the medical support system shown in FIG. 1, its affiliated members and a timeline. It is a conceptual diagram which shows the relationship. It is a figure which shows the configuration example of the table used in the medical information management system which concerns on one Embodiment of this invention, (a) is a room table, (b) is a room participation user management table, (c) is a room timeline. The management table, (d) is a file management table. It is a flowchart which shows a series of operations at the time of newly creating a secret talk room, and posting a message or a file to the timeline in the medical information management system which concerns on one Embodiment of this invention. FIG. 14A is a continuation of FIG. 14A, which is a flowchart showing a series of operations when creating a secret talk room and posting a message or a file on the timeline in the medical information management system according to the embodiment of the present invention. FIG. 14A is a continuation of FIG. 14A, which is a flowchart showing a series of operations when creating a secret talk room and posting a message or a file on the timeline in the medical information management system according to the embodiment of the present invention. It is a flowchart which shows a series of operations at the time of posting a message or a file to the timeline of an existing secret talk room in the medical information management system which concerns on one Embodiment of this invention. FIG. 15A is a continuation of FIG. 15A, which is a flowchart showing a series of operations when posting a message or a file to the timeline of an existing secret talk room in the medical information management system according to the embodiment of the present invention. It is a flowchart which shows a series of operations at the time of browsing the file posted on the timeline of the existing secret talk room in the medical information management system which concerns on one Embodiment of this invention. 16A is a continuation of FIG. 16A, which is a flowchart showing a series of operations when viewing a file posted on the timeline of an existing secret room in the medical information management system according to the embodiment of the present invention. 16A is a continuation of FIG. 16A, which is a flowchart showing a series of operations when viewing a file posted on the timeline of an existing secret room in the medical information management system according to the embodiment of the present invention. It is a flowchart which shows a series of operations at the time of posting a file directly to an existing secret talk room in the medical information management system which concerns on one Embodiment of this invention. FIG. 17A is a continuation of FIG. 17A, which is a flowchart showing a series of operations when a file is directly posted to an existing secret room in the medical information management system according to the embodiment of the present invention. FIG. 17A is a continuation of FIG. 17A, which is a flowchart showing a series of operations when a file is directly posted to an existing secret room in the medical information management system according to the embodiment of the present invention. It is explanatory drawing which shows the example of the "home screen" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "display screen of the timeline of a group" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "secret talk room name input screen" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "secret talk room participant selection screen" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "home screen" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "display screen of the timeline of a secret talk room" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "file direct posting screen" of the secret talk room of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of "posting destination selection screen by direct file posting" to the timeline of the secret talk room of a specific patient used in the medical information management system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the example of the "patient detail information display screen" of a specific patient used in the medical information management system which concerns on one Embodiment of this invention.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

(Usage form of medical support service)
FIG. 1 shows the overall configuration when a service recipient such as a patient or a medical worker uses the medical support service provided by the medical support system 30 linked with the medical information management system 100 according to the embodiment of the present invention. Shown.

In the following description, when individual patients are distinguished, they are referred to as "patient P1", "patient P2", etc., and when individual patients are not distinguished, they are referred to as "patient P". Similarly, when distinguishing individual medical workers, it is described as "medical worker M1", "medical worker M2", etc., and when it is not distinguished, it is described as "medical worker M". When distinguishing individual patient-related persons, it is described as "patient-related person R1", "patient-related person R2", etc., and when it is not distinguished, it is described as "patient-related person R". When individual medical facilities are not distinguished, they are referred to as "medical facilities F", and when they are distinguished, they are referred to as "medical facilities F1", "medical facilities F2" and the like. When individual groups are not distinguished, they are described as "group G", and when they are distinguished, they are described as "group G11", "group G12" and the like.

As shown in FIG. 1, this medical support service provided by the medical support system 30 is provided by a patient P, a patient-related person R, or a medical worker M who wishes to use the medical support system after registering as a user by a predetermined method. The patient terminal 10 owned by P, the medical worker terminal 11 operated by the medical worker M, or the patient-related person terminal 12 owned by the patient-related person R (hereinafter, these terminals are collectively referred to as a "user terminal"). (Sometimes), it has come to be used via the Internet 20, which is a communication network.

The patient P, the patient-related person R, or the medical worker M who has registered as a user is the "user" of this medical support service. Since this medical support service is realized by the medical support system 30, the "user" of the medical support service can also be said to be the "user" of the medical support system 30. Patient P, patient-related person R, or medical worker M who has not registered as a user cannot use this medical support service.

When an instruction is sent to the medical support system 30 from any of the user terminals 10, 11 or 12 via the Internet 20, the operation of the hardware and software installed in the medical support system 30 causes the "user registration" described later to be performed. Various operations and functions such as "group generation", "invitation to group", "message transmission / reception (communication)", "family registration", and "viewing medical information" are executed. Also, by doing so, the medical information and exchanged messages of each patient can be transmitted between multiple healthcare professionals M, or between patient P and healthcare professional M, while protecting the privacy of patient P. It becomes possible to share between patient P, medical staff M, and patient-related person R, and it becomes possible to provide better quality medical services to individual patient P based on the shared medical information and messages. ..

The patient terminal 10 and the patient-related person terminal 12 are usually mobile terminals such as a mobile phone or a smartphone, and each patient P or the patient-related person R owns his / her own terminal, but is a desktop type or a notebook type. Personal computers (personal computers) and touch-sensitive terminals can also be used. Since the medical worker terminal 11 is often installed in a medical facility, it is usually a desktop type or notebook type personal computer, but it goes without saying that a touch panel type terminal or a mobile terminal can also be used. In short, these terminals 10, 11 and 12 may be any terminal device capable of transmitting, receiving and displaying information with and from the medical support system 30 via the Internet 20, and the form and configuration thereof are not limited.

Each patient P suffers from one or more diseases and receives medical services such as diagnosis and treatment from a medical worker M who belongs to a specific medical facility F. In order to simplify the explanation, in this embodiment, it is assumed that only two patients P1 and P2 are using this medical support service, but it goes without saying that more patients P actually use it. No.

The patient-related person R refers to a person who is related to the patient P in some way, such as a family member, a relative, a friend, or an acquaintance of the individual patient P. Even if it is a medical worker M, if it is a family member, a relative, a friend, an acquaintance, etc. of a certain patient P, it can be a patient-related person R of the patient P. Here, it is assumed that eight patient-related persons R1, R2, R3, R4, R5, R6, R7 and R8 are participating, but depending on the circumstances of patient P, more or more or Needless to say, it may be used by fewer patient-related persons R.

The medical worker M refers to a person who is engaged in medical care at a medical facility F such as a doctor or a nurse. Medical worker M belongs to various medical facilities F such as clinics (small clinics), hospitals (medium and large medical facilities), and home-visit nursing stations with specialized fields, and the medical facilities F provides medical services such as diagnosis and treatment to patient P. Here, it is assumed that only eight medical workers M1, M2, M3, M4, M5, M6, M7 and M8 are participating, but in reality, more or less medical workers M Needless to say that will participate.

The medical facility F refers to a facility where medical services are provided to patient P by medical worker M, for example, a small clinic, a larger hospital, a home-visit nursing station, or the like. Any facility that provides some kind of medical service such as diagnosis, treatment, nursing, care, examination, surgery, consultation, etc. is sufficient, and its form and scale do not matter.

Further, in FIG. 1, it is assumed that the patient P, the medical worker M, and the patient-related person R own the terminals 10, 11 and 12, respectively, but the present invention is not limited to this. Patient P, patient-related person R, and medical worker M each have identification information (user ID) that can be uniquely identified, and even if they log in to the medical support system 30 from the same terminal, they can be distinguished from each other. There is no problem even if it is shared by multiple people.

FIG. 2 shows the interrelationship between patients P1 and P2, patient-related persons R1 to R8, and medical personnel M1 to M8 who are users of the medical support system 30, in other words, using the medical support system 30. It is explanatory drawing.

In the medical support system 30, group G is generated and registered for each disease of individual patient P. That is, a separate group G is formed for each disease of each patient P. The person (participant) (that is, group member) who participates in each group G is usually a medical worker who belongs to the medical facility F where the patient P is receiving medical treatment, etc. in addition to the patient P himself / herself. Includes at least one person M and further includes patient-related person R added as needed. Therefore, the group members of each group G are generally composed of the patient P himself, the medical staff M in charge, and the patient-related person R.

Any one of the medical-related facilities F to which the medical worker M participating in each group G belongs is usually "family-registered" with respect to the group G (and thus the patient P). The “family-registered” medical facility F is primarily responsible for the overall treatment policy of patient P's disease in Group G.

However, the composition of group members is not limited to such cases. For example, only patient P and one or more healthcare professionals M may be group members (not including patient participants R), or only multiple healthcare professionals M are group members (patient P). Also does not include patient-related person R). The former occurs, for example, when the patient P does not want to inform the patient-related person R of his / her medical information. The latter occurs when a plurality of healthcare professionals M involved in the treatment of patient P want to share medical information of patient P but do not want to inform patient P. If the patient P is not included in the group members, the approval for sharing the medical information cannot be obtained from the patient P on the medical support system 30, so that the patient P is separately obtained outside the medical support system 30. For example, approval may be obtained in writing. Of course, only the process in which the patient P approves the digitized document or the like may be added to the medical support system 30 for convenience. Needless to say, a subsystem for obtaining approval for sharing medical information from patient P may be separately incorporated into the medical support system 30.

Participants (group members) other than the patient P of each group G are called "supporters" regardless of whether they are medical workers M or patient-related persons R. This is because they are people who support patient P in some way. Therefore, it can be said that the group members of each group G are composed of the patient P himself and at least one supporter when the patient P is included. When patient P is not included, it can be said that it is composed of only a plurality of supporters.

Here, as is clear from FIG. 2, patient P1 suffers from three diseases (here, diabetes, hyperlipidemia, and gout), and the three diseases of patient P1 are divided into groups G11, G12, and Gout. G13 has been generated and a medical facility F is associated with each group G. Specifically, clinic F1 is registered as a family member for group G11 for diabetes treatment, clinic F2 is registered as a family member for group G12 for hyperlipidemia treatment, and group G13 for gout treatment is registered. On the other hand, hospital F3 is registered as a family member. Thus, here patient P1 belongs to three groups G11, G12 and G13. As will be described later, the groups G11, G12 and G13 also belong to the medical staff M who belong to the clinics F1, the clinic F2 and the hospital F3 which are registered as family members.

Patient P2 suffers from two diseases (here, Alzheimer's disease and hypertension), and groups G21 and G22 are generated for each of the two diseases of patient P2, and the medical facility F associates each group. Has been done. Specifically, the hospital F3 is registered as a family member for the group G21 for Alzheimer's treatment, and the home-visit nursing station F4 is registered as a family member for the group G22 for hypertension treatment. Thus, here patient P2 belongs to two groups G21 and G22. As will be described later, the groups G21 and G22 also belong to the medical staff M who belong to the hospital F3 and the home-visit nursing station F4, which are registered as family members, respectively.

As described above, group G11 is a group for treating diabetes of patient P1, group G12 is a group for treating hyperlipidemia of patient P1, and group G13 is a group for treating gout of patient P1. Group G21 is a group for treating Alzheimer's disease of patient P2, and group G22 is a group for treating hypertension of patient P2. In this way, since the group G is created for each disease possessed by each patient P, medical information regarding the specific disease of the specific patient P is shared within each group G, and therefore, for the treatment of the disease, etc. On the other hand, a high support effect can be expected, and as a result, better quality medical services can be provided.

The medical worker M1 is a doctor, belongs to the clinic F1, and belongs to the diabetes treatment group G11 and the gout treatment group G13 of the patient P1 as supporters. The medical worker M2 is a nurse, belongs to the same clinic F1 as the medical worker M1, and belongs to the diabetes treatment group G11 of the patient P1 as a supporter.

The medical worker M3 is a doctor, belongs to the clinic F2, and belongs to the hyperlipidemia treatment group G12 of the patient P1 as a supporter. The medical worker M4 is a nurse, belongs to the same clinic F2 as the medical worker M3, and belongs to the hyperlipidemia treatment group G12 of the patient P1 as a supporter.

The medical worker M5 is a doctor, belongs to the hospital F3, and belongs to the diabetes treatment group G13 of the patient P1 as a supporter. The medical worker M6 is a doctor and belongs to the same hospital F3 as the medical worker M5, and belongs to the diabetes treatment group G11 of the patient P1 and the Alzheimer treatment group G21 and the hypertension treatment group G22 of the patient P2 as supporters. doing.

The medical worker M7 is a nurse, belongs to the home-visit nursing station F4, and belongs to the Alzheimer's treatment group G21 of the patient P2 as a supporter. The medical worker M8 is a nurse, belongs to the same home-visit nursing station F4 as the medical worker M7, and belongs to the hypertension treatment group G22 of the patient P2 as a supporter.

As described above, in the medical support system 30, groups G11, G12 and G13 are formed for each of the three diseases (here, diabetes, hyperlipidemia, and gout) possessed by the patient P1, and these groups G11, Clinic F1, clinic F2 and hospital F3 are registered as family members in each of G12 and G13. Therefore, the medical professionals M1 and M2 belonging to the clinic F1 are in charge of treating the disease (here, diabetes) of the group G11 of the patient P1 as the attending physician. Medical professionals M3 and M4 belonging to the clinic F2 are in charge of treating the disease (here, hyperlipidemia) of the group G12 of the patient P1 as the attending physician. Medical professionals M5 and M6 belonging to the hospital F3 are in charge of treating the disease (here, gout) of the group G13 of the patient P1 as the attending physician.

Similarly, groups G21 and G22 are formed for each of the two diseases (here, Alzheimer's disease and hypertension) having patient P2, and hospital F3 and home-visit nursing station F4 are registered as family members in each of these groups G21 and G22, respectively. ing. Therefore, the medical staffs M5 and M6 belonging to the hospital F3 are in charge of treating the disease (here, Alzheimer's disease) of the group G21 of the patient P2 as the attending physician. Medical professionals M7 and M8 belonging to the home-visit nursing station F4 are in charge of treating the disease (here, hypertension) of the group G22 of the patient P2 as the attending physician.

The various functions required to realize the above-mentioned sharing and communication (message exchange) of medical information in each group G are described from the patient terminal 10, the medical worker terminal 11, or the patient-related person terminal 12 as described later. The medical support system 30 provides in response to a request or instruction.

(Configuration and function of medical support system)
Next, the configuration and function of the medical support system 30 will be described with reference to FIG. FIG. 3 is a functional block diagram showing the internal configuration of the medical support system 30.

As shown in FIG. 3, the medical support system 30 includes a user management unit 310, a group management unit 320, an authentication unit 340, and a communication control unit 350.

The communication control unit 350 uses the medical support system 30 and a plurality of user terminals (that is, the patient terminal 10, the medical worker terminal 11, and the patient-related person) via the Internet 20 as a communication network provided outside the medical support system 30. This section enables information to be sent and received to and from the terminal 12). Since the communication control process of the communication control unit 350 is executed by a known method, the description thereof will be omitted.

The authentication unit 340 authenticates whether or not the person who has accessed the medical support system 30 from the user terminal 10, 11 or 12 via the Internet 20 is a legitimate user who has been registered as a user in the medical support system 30. This is the section to do.

The authentication unit 340 is connected to the Internet 20 provided outside the medical support system 30 via the communication control unit 350. The user management unit 310 and the group management unit 320 are connected to the patient terminal 10, the medical worker terminal 11, and the patient-related person terminal 12 outside the medical support system 30 on condition that the authentication unit 340 obtains a predetermined authentication. Send and receive information between. Then, only when the authentication unit 340 authenticates as a regular user, the person is allowed to access the user management unit 310 and the group management unit 320. Only then will the user be able to use the medical support services provided by the medical support system 30.

Next, the user management unit 310 will be described.

The user management unit 310 registers individual users who use the medical service provided by the medical facility F, or users who support the users, that is, patient P, medical worker M, and patient-related person R (user registration). ) And the section that manages registered users. The user management unit 310 has a registration unit 311, a user information storage unit 312, a patient information storage unit 313, a medical worker information storage unit 314, a medical facility information storage unit 315, and a disease information storage unit 316.

The registration unit 311 is formed of software that controls the operation, and controls the operation related to the overall user registration in the user management unit 310. For example, a predetermined user registration screen (not shown) is displayed on the user terminal 10, 11 or 12 that has accessed the medical support system 30, and the person who wishes to use the medical support service (user) , Encourage you to enter and send the specified personal information. Correspondingly, when predetermined personal information is transmitted from the user terminal 10, 11 or 12 to the medical support system 30, the personal information is stored in the user information storage unit 312 as "user information" of the person who wants to use the personal information. .. In addition, the registration unit 311 reads and uses the user information stored in the user information storage unit 312 as necessary, and also corrects / deletes the user information.

The user information storage unit 312 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, playing, and erasing information on the information storage medium, and user information is in response to instructions from the registration unit 311. That is, the necessary information of the patient P as a user, the medical worker M, and the patient-related person R is stored. At this time, "user identification information" (user ID) that can be uniquely identified is assigned to each user. The user information is stored, for example, in the form of a user table as shown in FIG. 4A. The items in this user table are the "user ID" (user identification information) assigned to each user, the "login ID" and "password" required for each user to log in to the medical support system 30, and each user. Is the "registration date" which is the date when the medical support system 30 is registered, and the "status" which indicates the validity / invalidity of each user's registration.

The patient information storage unit 313 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and the patient P is instructed by the registration unit 311. Memorize your personal information. At this time, a uniquely identifiable "patient ID" is assigned to each patient P. This "patient ID" is "patient identification information" and also "service beneficiary identification information". The personal information of patient P is stored, for example, in the form of a patient table as shown in FIG. 4 (b). The items in this patient table are the "patient ID" (service recipient identification information) assigned to each patient P, the "user ID" (user identification information) possessed by each patient P, and the "patient name" of each patient P. , "Gender", "Date of birth", "Email address", "Address" and "Telephone number".

The medical worker information storage unit 314 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and responds to instructions from the registration unit 311. Memorize the personal information of the medical worker M. At this time, a uniquely identifiable "medical worker ID" is assigned to each medical worker M. This "medical worker ID" is "medical worker identification information" and is also "business worker identification information". The personal information of the medical worker M is stored in the form of a medical worker table as shown in FIG. 4 (c), for example. The items in this medical staff table are the "medical worker ID" (business worker identification information) assigned to each medical worker M and the "user ID" (user identification information) possessed by each medical worker M. The "medical facility ID" assigned to the medical facility F to which the medical worker M belongs, and the "medical worker name", "gender", "date of birth" and "occupation type" of each medical worker M. It has become. Job types such as doctors and nurses are stored in the "Job type" column.

The medical facility information storage unit 315 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and responds to instructions from the registration unit 311. Memorize the necessary information of medical facility F. At this time, a uniquely identifiable "medical facility ID" is assigned to each medical facility F. This "medical facility ID" is "medical facility identification information". The necessary information of the medical facility F is stored in the form of the medical facility table as shown in FIG. 4D, for example. The items in this medical facility table are the "medical facility ID" (medical facility identification information) assigned to each medical facility F, and the "facility name", "facility type", and "facility type" of each medical facility F. These are "medical department", "address", "phone number", "HP (homepage)", "medical hours" and "nearest station". In the "facility type" column, the type of each medical facility F such as a medical clinic, a hospital, and a home-visit nursing station is stored.

The disease information storage unit 316 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and the disease information is in response to instructions from the registration unit 311. Remember. At this time, a uniquely identifiable "disease ID" is assigned to each disease. This "disease ID" is "disease identification information". The disease information is stored, for example, in the form of a disease table as shown in FIG. 5 (b). The items in this disease table are the "disease ID" (disease identification information) assigned to each disease, and the "medical facility patient ID" defined in the medical facility patient table shown in FIG. 5 (a). It is the "disease name". The "medical facility patient ID" is identification information indicating the relationship (link) between the patient P and the medical facility F registered by the patient P as a family member. In the disease table, the "disease ID" is associated with the "medical facility patient ID" because the "medical facility patient ID" can be used to easily associate the patient P with the disease and the medical facility. Because it can be done.

Next, the group management unit 320 will be described.

The group management unit 320 is a section that manages the group G that is registered and formed for each disease of the individual patient P in the medical support system 30. For example, in addition to new group registration, it performs many functions such as storing group member information, controlling invitation requests, timelines and messages, and family registration. The group management unit 320 includes a registration unit 321, a group information storage unit 322, a group member information storage unit 323, an invitation request control unit 324, an invitation request information storage unit 325, a timeline control unit 326, a message control unit 327, and a family facility. It has an information storage unit 328, a shared consent information storage unit 329, a patient existence verification unit 330, and an authentication unit 331.

The registration unit 321 is formed from software that controls the operation, and generates and registers a group G for each disease of the individual patient P at the request of the medical worker M or the patient P. In addition, at the request of the medical worker M or the patient P, the process related to the “family registration” (specifically, the association between the patient P, the disease, and the medical facility F) described later is also executed.

The group G is generated at the request of the medical worker M when the medical worker M performs "patient group registration". “Patient group registration” refers to registering the patient P treated by the medical facility F to which the medical worker M belongs and the disease thereof in the medical support system 30. At this time, the medical worker M designates the patient P who is being treated by the medical facility F to which he / she belongs and the disease thereof, and registers the patient in the medical support system 30, which is the medical worker. This is so that the medical information of the patient P can be shared within the medical-related facility F to which the M belongs. The registration unit 321 automatically generates a group G in synchronization with the "patient group registration", and stores the generated information related to the group G in the group information storage unit 322.

The initial group members of group G thus generated are zero unless a predetermined member (default member) is automatically invited. Neither the medical worker M who has performed "patient group registration" nor the patient P who has been subject to "patient group registration" is a group member. In order for the medical worker M who has "registered as a patient group" to become a group member, he / she must send an invitation request to himself / herself and approve it by himself / herself. Similarly, in order for patient P who is the target of "patient group registration" to become a group member, it is necessary to send an invitation request to patient P for approval.

Group G is generated at the request of patient P when patient P requests "family registration". At this time, the patient P selects one of the medical-related facilities F for which he / she is receiving or is about to receive medical treatment, requests "family registration", and approves the medical-related facility F. I will ask you to do it. This is because the patient P mainly desires to receive treatment and designates a medical facility F which is mainly responsible for the overall treatment policy. The registration unit 321 automatically generates a group G in synchronization with the "family registration", and stores the generated information (group information) related to the group G in the group information storage unit 322. In the "family registration", specifically, the patient P, the disease, and the medical facility F are associated with each other.

Even in the group G thus generated, the initial group members are zero unless the default members are automatically invited. Neither the patient P who requested the "family registration" nor the medical worker M of the medical facility F who was the target of the "family registration" is a group member. In order for patient P who requested "family registration" to become a group member, he / she must send an invitation request to himself / herself and approve it himself / herself. Similarly, in order for the medical worker M related to the "family registration" to become a group member, the patient P who requested the "family registration" must send an invitation request to the medical worker M for approval. ..

When a new group G is generated, a member (for example, a specific medical worker M or a patient P himself / herself) who belongs to the newly generated group G from the beginning can be designated as a default member. By doing so, a member designated in advance is automatically invited to the group G at the same time as the generation of the group G, and becomes the group member from the time when the group G is generated.

The group information storage unit 322 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium. Group information, that is, which patient each group G is. It stores information indicating what kind of disease P is related to and which medical facility F is registered as a "family facility". The "group information" is stored, for example, in the form of a group table as shown in FIG. 5 (c). This group table includes a "group ID" which is group identification information, a "group name" indicating what kind of disease the group is related to, and a "patient ID" defined in the disease table of FIG. 5 (b). And are included as items.

The group member information storage unit 323 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium. The group member information storage unit 323 includes group member information, that is, the patient P who can be said to be the owner of each group G, and the medical staff M and the patient-related persons who participate in each group G as a supporter of the patient P. Store the information related to R. The "group member information" is stored in the form of a group participation table as shown in FIG. 5D, for example. This group participation table participates in the "group participation ID" which is the identification information attached to the action of "group participation" in a certain group G and the "user ID" of the user who participates in the group G. It includes an item called "accessible timeline" that specifies the "group ID" of the group G and the timeline that each member can access. By using such a group participation table, it is possible to record the group members belonging to each group G, and in each group G, which group member can access which timeline (that is, each group). -What kind of access authority the member has) can also be recorded.

The invitation request control unit 324 is formed from software that controls the operation, and identifies a non-group member (that is, patient P, medical worker M, or patient-related person R) who wants to participate in each group G. , Control "invitation requests" sent to those non-group members. The invitation request control unit 324 sends an invitation request in the form of an e-mail to the identified non-group members in response to the instructions of the user, that is, the healthcare worker M or the patient P or the patient-related person R. It also receives a reply from the user who received the invitation request (indicating whether or not the invitation request was approved).

The invitation request is an email-style invitation sent to a user who wants to join the desired group G and become a group member. The invitation request can be sent by the patient P, the medical staff M, or the patient-related person R, but before sending the invitation request to the user who wishes to join the group G, the predetermined administrator's " You need to get a "permit". This is decided by the administrator in consideration of whether or not the user who is inviting is suitable as a group member, and whether or not the participation of the user causes any trouble. This manager includes a "healthcare worker side manager" and a "patient side manager". The "healthcare worker side administrator" is a health care worker M (also a user) who has the authority to "permit" or "deny" the transmission of an invitation request, and for each medical facility F or for each group. Set. As the "administrator on the medical staff side", for example, the director or secretary of the clinic is designated. The "patient side administrator" is the patient P himself (also a user) or a user who is authorized by the patient P to "permit" or "deny" the transmission of the invitation request from the patient P's family and friends. , It is set for each patient P or for each group. As the "patient side administrator", for example, a parent, spouse, child, close friend, etc. of patient P are designated.

Normally, both the "healthcare worker side manager" and the "patient side manager" whether the medical worker M sends the invitation request or the patient P or the patient related person R sends the invitation request. It is stipulated that an invitation request cannot be sent without permission. That is, it is set to determine whether or not to send the invitation request after considering both the circumstances on the side of the medical worker M and the circumstances on the side of the patient P. This is because when a group member becomes a group member, the medical information and messages of the patient P can be viewed, and who becomes a group member has a great influence on both the patient P and the medical worker M. .. However, it is not limited to this. If the permission of either the "healthcare worker side administrator" or the "patient side administrator" is obtained, the invitation request may be sent, or only the "healthcare worker side administrator" has permission. If so, you may be able to send an invitation request. This point can be determined as needed or as desired.

As described above, in the medical support system 30, in order for the transmission of the invitation request to be "completed" ("invitation completed"), at least one of the "medical worker side manager" and the "patient side manager" is "completed". "Permission" is required so that adding group members does not cause any problems.

The user who receives the invitation request sent with the "permission" of both the "healthcare worker side administrator" and the "patient side administrator", or at least one of them, is the group G specified in the invitation request. If you want to participate in, you can "approve" the invitation. Then you will be automatically added as a group member. If you do not want to join Group G, you can "reject" the invitation. In this way, the user who receives the invitation request can choose to join or not join Group G by deciding whether or not to "approve" the invitation.

The user who approves the invitation becomes a member of group G, but all group members other than patient P (specifically, medical worker M and patient-related person R) become supporters of patient P. Medical information and messages of patient P are shared among group members according to the sharing rules (described later) selected by patient P. Therefore, for example, when a medical worker M of another medical facility F wants to receive a second opinion for his / her disease, or a family member or relative who wants patient P to know about the treatment process related to his / her disease. If there is a patient-related person R such as a friend, an invitation request is sent to such people. By doing so, while ensuring the uniqueness of the medical information about the specific disease of the patient P of the medical-related facility F, a plurality of medical workers M including the medical workers of other medical-related facilities and the patient-related persons. It can be shared with R and patient P himself.

The settings of the "medical worker side manager" and the "patient side manager" are stored in the invitation request information storage unit 325. The invitation request control unit 324 executes the "permission" process by the "healthcare worker side manager" and the "patient side manager". The invitation request control unit 324 executes the generation and transmission of the invitation request and the reception of the reply from the invitation request recipient.

The invitation request information storage unit 325 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium. The invitation request information storage unit 325 receives "invitation request information" generated by the invitation request control unit 331 in response to the request, that is, various information indicating who sends the invitation request to whom, and the invitation request by the administrator. Memorize information about permission or denial. In addition, the content of the reply from the recipient of the invitation request (approval or rejection of the invitation request) and the settings of the "medical worker side administrator" and the "patient side administrator" are also stored. The "invitation request information" is stored, for example, in the form of the invitation request table shown in FIG. 6A. The items in this invitation request table are the "invitation request ID" assigned to each invitation request, the "invitation source user ID" that is the identification information of the user who sends the invitation request, and whether or not the invitation request can be sent. Identification information "Invitation request permission / rejection", "Invitation request approval" which is identification information of whether or not the invitation request is approved by the invitee, "Invitation destination user ID" which is identification information of the recipient to whom the invitation request is sent. , "Invitation email address" and "Invitation passphrase" of the recipient (destination) to which the invitation request is sent, "Group ID" which is the identification information of the invited group, and the timeline that the group members can access Includes an "accessible timeline" showing the code.

In addition, the invitation request table in FIG. 6A includes the "invitation destination passphrase" whether or not the person who received the invitation request is a legitimate invitation destination, in other words, the person himself / herself. This is to confirm with this passphrase whether or not there is. In order for the person who received the invitation request to join the group of the invitee related to the invitation request, access the URL described in the invitation request email and display the invitation request approval screen. You need to enter the passphrase. If the entered passphrase does not match the "invitation destination passphrase" stored in the invitation request table, you will not be able to join the group, so you can easily authenticate the invitation destination. It is.

The timeline control unit 326 is formed of software that controls its operation, and controls a "timeline" (that is, an information display area) assigned to each group G. Specifically, an information display area called a "timeline" is assigned to the newly generated group G, and the shared medical information is assigned to the timeline in a predetermined order (for example, in the order of posted time). Display it. Since the information to be displayed and the parameters such as the display time are sent from the medical worker terminal 11 to the group management unit 330 via the Internet 20, the timeline control unit 326 sends the sent information according to the parameters. Display on the timeline.

An example of the timeline is shown in FIG. This timeline 51 was generated for the diabetes treatment group G11 of patient P1 and includes a shared area 51a for all and a shared area 51b for healthcare professionals. Information shared by all members of the group G11 is displayed in the all-shared area 51a. In the medical worker sharing area 51b, information shared only by the medical worker M of the group G11 is displayed. Therefore, the medical information displayed in the shared area 51a can be shared by all the members of the group G11, and in addition to the patient P1, the medical workers M1 and M2 belonging to the clinic F1 and the medical workers belonging to the hospital F3 are engaged. Person M6 and patient-related persons R1, R2 and R4 can freely post and view. Unlike this, the medical information displayed in the medical worker shared area 51b can be shared only by the group G11 medical staff, and the medical staffs M1 and M2 belonging to the clinic F1 and the medical staff belonging to the hospital F3 Worker M6 can freely post and browse.

In FIG. 9, one timeline 51 divided into a shared area 51a for all employees and a shared area 51b for medical staff is provided for the group G11, but the "timeline for all" and "medical care" are provided for the group G11. Needless to say, two timelines called "worker timelines" may be provided. Actually, in the timeline table of FIG. 6B, this is the case, and in the group of group ID "10001", the patient side timeline to which the timeline ID "1" is assigned (timeline for all). And, a timeline on the medical staff side (timeline for medical staff) to which the timeline ID "2" is assigned is provided.

The message control unit 327 is formed of software that controls its operation, and controls transmission / reception of a message addressed from one group member to another group member. For this control, for example, the message transmission reservation table shown in FIG. 7A is used. The items of this message transmission reservation table are the "transmission reservation ID" which is the identification information assigned to each transmission reservation, the "destination user ID" which is the identification information of the user to whom the message is sent, and the identification of the user who sends the message. It is the "sender user ID" which is information, the "message" which is the content to be transmitted, and the "scheduled transmission date and time" where the scheduled date and time when the message is transmitted is stored.

The patient attribute table shown in FIG. 7B stores the attributes of individual patients P, and is used when the message control unit 336 selectively transmits a predetermined message to some patients P. Will be done. This patient attribute table includes "patient attribute ID" which is identification information attached to the attribute of each patient P, "patient ID" of each patient P, "attribute name" of each patient P, and each patient P. It has an item called "attribute value". The value of "2013 medical examination guide" stored in the "attribute name" needs to be sent to this patient P in the "2013 medical examination guide" and is stored in the "attribute value". The value of "not yet" indicates that the "guidance for the 2013 health examination" has not yet been transmitted.

The family facility information storage unit 328 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium. The family facility information storage unit 328 stores "family facility information" that is used and generated in the "family registration" (association of patient P, disease, and medical-related facility F) process executed by the registration unit 321. The details of the family registration are described in Patent Document 1 described above, and since they have nothing to do with medical information management, the description thereof will be omitted. The “family facility information” is stored, for example, in the form of a medical facility patient table as shown in FIG. 5 (a). The items in this medical-related facility patient table are the "medical-related facility patient ID" assigned to each individual patient P receiving treatment at each medical-related facility F, and the medical-related facility shown in FIG. 4 (d). The "medical facility ID" specified in the table, the "patient number" of the patient P in the medical facility F, and the "patient name", "gender", "date of birth", and "insurance" of the patient P. , "Last consultation date", "Address", "Phone number", "Email address" and "Passcode". The "medical facility patient ID" is identification information indicating the relationship between the patient P and the medical facility F registered by the patient P, and is "family facility identification information" or "medical facility / patient relationship identification". Information can be said. The "patient number" is identification information of the patient P who is receiving medical treatment or the like at the medical facility F. The "passcode" is information assigned to each patient P for identity verification, and is used when the patient P approves the family registration request.

The registration unit 321 displays a predetermined sharing rule selection screen (not shown) on a predetermined medical information sharing inquiry screen (which is displayed on the user terminal. Not shown), and displays a sharing rule, that is, medical information. Prompt to select a sharing range. For example, there are two options for sharing rules, one is "shared only inside the medical facility F related to family registration", and the other one is "inside the medical facility F related to family registration and family registration". It is shared by all group members, including the patient P himself / herself. When any of the sharing rules is selected, the registration unit 321 stores the answer to "agree to sharing" and the selected sharing rule in the sharing consent information storage unit 329. Needless to say, you may set three or more sharing rules.

The shared consent information storage unit 329 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and is generated by the registration unit 321 as "self". Memorize the statement of intention (sharing consent information) to the effect that "I agree to share medical information" and the selected sharing rule. The sharing consent information and the selected sharing rule are stored, for example, in the form of the medical information sharing table shown in FIG. 6 (c). The items of this medical information sharing table are the "user ID" of the patient P, the "medical facility ID" of the medical facility F registered as a family member, and the "sharing rule" agreed by the patient P. In the medical information sharing table shown in FIG. 6 (c), the patient P with the user ID "100" is given "in-hospital sharing permission" at the medical facility F with the medical facility ID "1000", and is medical related. The medical facility F whose facility ID is "1001" gives "comprehensive sharing permission".

The patient existence verification unit 330 is formed from software that controls its operation, and is "whether or not the patient P who has requested family registration actually exists", in other words, "the patient P is the person himself / herself". Yes, isn't it impersonating another person? " This patient reality verification process is preferably performed before initiating the family registration process described above. FIG. 6D shows an example of an NFC terminal table created for managing NFC terminals. This NFC terminal table includes a "medical facility ID" assigned to each medical facility F, an "NFC terminal number" assigned to each NFC terminal, and a medical facility patient table in FIG. 5 (a). It has an item called "medical facility patient ID" assigned to each patient in each medical facility F and a "passcode" assigned to each patient P as defined in the above. The passcode entered in the "passcode" column of the NFC terminal table is the same as the passcode entered in the "passcode" column of the medical facility patient table in FIG. 5 (a).

The authentication unit 331 is formed of software that controls its operation, and is a patient P, a medical worker M, or a patient-related person R who has accessed a specific group G of the medical support system 30 via a user terminal. Checks if they are legitimate members of that group G, in other words, if they have permission to access the timeline of that group G. Then, if it is confirmed that it is a legitimate member, it is allowed to access the timeline of the group G. If it is confirmed that it is not a legitimate member, it refuses to access the timeline of the group G.

The above-mentioned various tables used in the medical support system 30 have a relationship as shown in FIG.

(Operation of medical support system)
In the medical support system 30 having the above configuration, a group G is registered and generated for each disease of each patient P in order to share medical information and a message. As described above, the group G is created by the patient group registration by the medical worker M or the family registration by the patient P. In addition, group members of group G are added by inviting patient P, medical staff M, and patient-related person R as necessary, except for default members, and are deleted from group G as necessary. The default. Details of these operations of the medical support system 30 are described in Patent Document 1, but since these are not related to the medical information management system 100 according to the present embodiment, their description will be omitted.

Further, for the same reason, the description of operations such as user registration, new patient registration, new medical worker registration, and supporter invitation of the medical support system 30 will be omitted.

(Configuration of medical information management system)
Next, the configuration of the medical information management system 100 according to the embodiment of the present invention will be described with reference to FIGS. 10 and 11.

As shown in FIGS. 10 and 11, the medical information management system 100 according to the present embodiment is configured to operate in cooperation with the medical support system 30, and the user management unit 110 and the secret talk room management unit 120. And a file management unit 130.

The user management unit 110 is a section that manages users who use the medical information management system 100. That is, among the patient P, the medical worker M, and the patient-related person R who are the users of the medical support system 30, the user who uses the medical information management system 100 is registered (user registration), and the registered user is managed. It is a section. The user management unit 110 has a registration unit 111, a user information storage unit 112, and a user participation control unit 113. The user management unit 110 operates in cooperation with the user management unit 310 of the medical support system 30.

The registration unit 111 is formed of software that controls the operation, and controls the operation related to the overall user registration in the user management unit 110. For example, the user terminal 10, 11 or 12 of the user who uses the medical information management system 100 (that is, the user of the medical support system 30 who creates the secret talk room S and uses the function) has a predetermined secret talk room name. For those who wish to use the secret talk room function of the medical information management system 100 by displaying the input screen (see FIG. 20) and the secret talk room participant selection screen (see FIG. 21). , Prompt to enter / send the prescribed information. In response to this, when predetermined information is transmitted from the user terminal 10, 11 or 12 to the medical information management system 100, the information is stored in the user information storage unit 112 as "user information" of the person who wants to use the information. Further, the registration unit 111 reads and uses the user information stored in the user information storage unit 112 as necessary, and also corrects / deletes the user information.

The user information storage unit 112 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, reproducing, and erasing information on the information storage medium, and is secretly talked about in response to an instruction from the registration unit 111. The user information of the user (patient P, the medical worker M, or the patient-related person R) who wishes to use the room function and the user information of the room member belonging to the created secret talk room S are stored. Specifically, for example, the "user identification information" (user ID) assigned to each user by the medical support system 30 is stored in the form of the room table shown in FIG. 13 (a). The items of this room table are the "room ID" assigned to the created secret story room S, the "room name" attached to the secret story room S, and the group G in which the secret story room S was created. The "group ID" and the "created user ID" which is the user ID of the user who created the secret story room S are included.

The user participation control unit 113 is formed of software that controls its operation, and is a user (patient P, medical worker M, and patient) who becomes a participant (room member) of the secret talk room in response to an instruction from the registration unit 111. The related party R) is controlled to participate in the newly created secret story room S or the existing secret story room S as a room member. Then, the user information of the user who participates as a room member is stored in the user information storage unit 112. Specifically, for example, the "user identification information" (user ID) assigned to each user by the medical support system 30 is stored in the form of the room participation user management table shown in FIG. 13 (b). The items of this room participation user management table are the "room ID" assigned to the secret story room S, the "group ID" of the group G in which the secret story room S was created, and the participation of the secret story room S. The "created user ID" which is the user ID of the user (room member) is included.

Next, the secret story room management unit 120 will be described.

The secret talk room management unit 120 is a section that manages the secret talk room S created in each group G in the medical information management system 100. For example, in addition to newly registering the secret story room S, functions such as storing information of room members of the secret story room S and controlling the timeline and messages of the secret story room S are executed. The secret talk room management unit 120 has a secret talk room registration unit 121, a timeline control unit 122, and a secret talk room information storage unit 123. The secret story room management unit 120 operates in cooperation with the group management unit 320 of the medical support system 30.

The secret room registration unit 121 is formed from software that controls its operation, and is a group of individual patients P at the request of a group member of group G of individual patients P (for example, medical worker M). Create a secret story room S inside G and register it. At that time, the secret talk room registration unit 121 provides secret talk room information, that is, information indicating that each secret talk room S is inside which group G of which patient P and what kind of member belongs to it. It is generated and stored in the secret story room information storage unit 123. The "secret room information" is stored in the form of a room table as shown in FIG. 13A, for example. By changing the name of the secret story room S, a plurality of secret room S can be created in the same group G as needed. There is no limit to the total number of secret room S created in the same group G.

The initial room members of the secret story room S created in this way are zero, but since the participants are selected and added immediately after the secret story room S is created, the group members of the added group G are added. Become a room member. In this case, the invitation of the participants to the secret talk room S is automatically performed by the medical support system 30, that is, is performed by the automatic invitation, unlike the case of participation in the group G. For this reason, the process of sending and approving the invitation request required when creating Group G is not necessary for the participation of room members.

In the secret story room S created in this way, there is one "room manager". In other words, one of the room members is always assigned to the "room manager" of the secret room S. Normally, the user (room creator) who created the secret story room S is automatically assigned to the "room administrator", but the "room administrator" can be arbitrarily changed. However, since only the "room administrator" has the authority to change the "room administrator", the operation to change the "room administrator" is performed by the "room administrator" at that time specifying the new "room administrator". Need to do while. Although the user ID of the "room administrator" is not shown, for example, the item of "room administrator user ID in the room participation user management table of FIG. 13 (b) or the room table of FIG. 13 (a)" is shown. Is provided and recorded.

The timeline control unit 122 is formed from software that controls its operation, and controls a "timeline" (that is, an information display area) assigned to each secret room S. Specifically, an information display area called a "timeline" is generated and assigned to the newly generated secret story room S, and shared medical messages and attachments are assigned to the timeline. Display in order (for example, in order of posted time). The information to be displayed and the parameters such as the display time are sent from the user terminal that posted the message or the like to the secret talk room management unit 120 via the Internet 20 and the group management unit 330, so that the timeline control unit 122 can be used. Display the sent information on the timeline according to the parameters. For storing the timeline information of each secret room S, for example, the format of the room timeline management table as shown in FIG. 13C is used. The items of this room timeline management table include the "room ID" assigned to the secret story room S, the "group ID" of the group G in which the secret story room S was created, and the message posted on the room timeline. It is assigned to the user ID of the user, the "posting user ID", the information indicating the time when the message was posted, the "posting time stamp", the content of the message, the "posting message", and the posted file. The "posted file ID" which is the identification information is included.

An example of the timeline is shown in FIG. 12 (b). This timeline 151 is for the secret talk room Sa generated within the diabetes treatment group Ga of patient Pa. The group members of Group Ga are patient Pa, 3 patient-related persons Ra, Rb, Rc, and 7 medical workers Ma, Mb, Mc, Md, Me, Mf and Mg, for a total of 11 members. Only three of them, Ma, Mb and Mc, are participating in the secret talk room Sa. Therefore, the room members of the secret story room Sa are three medical workers Ma, Mb, and Mc, and the information such as messages and files posted on the timeline 151 is all the room members of the secret story room Sa. Shared by (ie, healthcare professionals Ma, Mb and Mc), i.e., free to post and view by all room members.

The secret story room information storage unit 123 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, playback, and erasing of information on the information storage medium, and the secret story room registration 121 generates a secret story. Memorize talk room information. The secret room information is stored in the form of, for example, the room table of FIG. 13A, the room participation user management table of FIG. 13B, and the room timeline management table of FIG. 13C.

Next, the file management unit 130 will be described.

In the medical information management system 100, the file management unit 130 posts to each secret story room S in a form attached to a message posted on the timeline or in a form independent of the message posted on the timeline. This section manages the files to be created. The file management unit 130 includes a file registration unit 131, a file browsing control unit 132, a file posting control unit 133, and a file access control unit 134. The file management unit 130 operates in cooperation with the group management unit 320 of the medical support system 30.

The file registration unit 131 is formed of an information storage medium such as a hard disk and software that controls operations such as recording, playback, and erasing of information on the information storage medium, and is a file posted to each secret story room S. The memory and the information related to the file (file name, file ID, user ID of the file poster, etc.) are registered. The information related to each file is stored in the form of a file management table as shown in FIG. 13D, for example. The items of this file management table are the "file ID" assigned to each file, the "file name" of each file, the "room ID" assigned to the secret room S, and the secret room S created. The "group ID" of the group G is included.

The file browsing control unit 132 controls whether or not the file posted in each secret story room S can be browsed. This is so that the file posted in the secret story room S can be viewed only by a user who has access authority, that is, an accessible person (for example, a medical worker M who belongs to a predetermined medical facility F). is there. This control is executed according to the file access authority (described later) given to each file.

The file posting control unit 133 posts (uploads) a file to each secret story room S by attaching it to a message posted on the timeline or in a form independent of the message posted on the timeline. Control the operation when File posting (uploading) is performed by a known method.

The file access control unit 134 sets the access authority for legally accessing each file posted in the secret story room S, and depending on the posting destination of the file, only the group members belonging to the group G Alternatively, it is controlled so that only the room members belonging to the secret story room S can access (view) the file. Here, when the file registration unit 131 registers each posted file, the attribute flag is set for each file, and the file is posted as an attached file of timeline information or the timeline. Regardless of whether the file was posted independently of the information, when the posting destination of the file is group G, the attribute flag of the file is set and the posting destination of the file is not group G (that is, the posting destination is the secret story room S). When), the attribute flag of the file is not set. The file access control unit 134 constantly checks the attribute flag of the posted file, and when the attribute flag is set, determines that the posting destination is group G, and is a group member of that group G. Grant access authority (viewing authority) to everyone. On the other hand, when the attribute flag of the posted file is not set, it is determined that the posting destination is the secret story room S, and access authority (viewing authority) is given to all the room members of the secret story room S which is the posting destination. Give. For this access control, for example, the format of the file management table as shown in FIG. 13D is used. In this file management table, the file ID of each file is associated with the room ID and the group ID, and the room ID and the group ID are further associated with the room participation user management table of FIG. 13B. Therefore, the user ID of the user who has the access authority (viewing authority) for each file is entered in the room participation user ID column having the corresponding room ID (for example, the room ID is "0001") in the room participation user management table. , "00111", "02432", "09879", etc. are listed (registered as a list). However, the present invention is not limited to such a method.

The meanings of the four tables in FIGS. 13 (a) to 13 (d) described above are as follows.

In the room table of FIG. 13A, a secret story room called "medical staff only" is created in the group having the group ID "00522", and the room ID "0001" is created in the secret story room. Is assigned, and the user who created the secret talk room is a user to which the user ID "00111" is assigned. Further, a secret room called "only medical staff" is created in the group whose group ID is "00813", and the room ID "0002" is assigned to the secret room. Then, it is shown that the person who created the secret story room is the same user who created the secret story room called "medical staff only". Furthermore, in the group with the group ID "00813" in which the secret story room called "medical staff only" was created, the same user who created the above two secret story rooms called "rehabilitation related information". It is shown that another secret story room to be called is created, and the room ID "0003" is assigned to the secret story room. In this way, the room ID of the secret talk room is stored in association with the group ID and the room ID.

The room participation user management table of FIG. 13 (b) is a member (room) belonging to a secret story room (room ID = 0001) called "medical staff only" created in a group having a group ID of "00522". -Member) indicates that there are three users whose user IDs are "00111", "02432", and "09879". In this way, the user ID of the user who participates in the secret talk room is stored in association with the room ID of the secret talk room and the group ID of the group to which the secret talk room belongs.

The room timeline management table of FIG. 13C is a timeline of a secret story room (room ID = “0001”) called “medical staff only” created in a group having a group ID of “00522”. It shows the situation, and the poster of the posted message "The pressure ulcer is very good" is the user with the user ID "00111", and the file with the file ID "00001" is attached to the message by the same user. Indicates that it has been posted. In addition, the poster of the posted message "OK" is a user with a user ID of "02432", and a file with a file ID of "00002" is attached to the message and posted by the same user. Is shown. Furthermore, the poster of the posted message "Thank you" indicates that the user has a user ID of "09879". The blanks in this table (pointed by arrow A) indicate that there are no files posted by the poster of the posted message "OK" (there are no files attached to the message). In this way, the message posted in the secret story room (this is medical / long-term care information about a specific patient or long-term care recipient) is the user ID of the user who posted the message and the posting of the message. It is associated with the room ID of the previous secret story room and the group ID of the group to which the secret story room belongs, and is stored together with the posting time stamp information indicating the posting time of the message. A file ID is assigned to each file attached to the message and then stored in association with information (posting user ID, room ID, and group ID) that identifies the attachment source message.

The file management table of FIG. 13D shows the status of the timeline of the secret talk room (room ID = 0001) created in the group whose group ID is “00522” and which is called “medical worker only”. The file name of the file with the file ID "0001" indicates that it is "Rehabilitation plan for March.xls", and the file name of the file with the file ID "0002" is "Decubitus January.jpg". The file name of the file whose file ID is "0003" is "Rehabilitation.jpg". The blanks in this table (the part indicated by the arrow B) are in the secret story room (room ID is "0001") where the file name is "Rehabilitation.jpg" and the posting destination is "Medical staff only". It indicates that it is a group (group ID = 00522). In this way, each file posted to the secret story room or group (also medical / long-term care information about a specific patient or long-term care recipient) is assigned a file ID, and then the file is posted. It is associated with the room ID of the previous secret story room and the group ID of the group to which the secret story room belongs, and is stored together with the file name information of the file. However, if the posting destination of the file is a group instead of the secret story room, the room ID does not exist, so the association with the room ID is not performed.

(Operation of medical information management system)
Next, the operation of the medical information management system 100 of the present embodiment having the above configuration will be described.

(Create a new secret story room and post it on the timeline)
14A to 14C show when a secret talk room S is newly created in a specific group G and a message or a file is posted to the timeline 151 in the medical information management system 100 operating in cooperation with the medical support system 30. It is a flowchart which shows a series of operations of.

First, when the medical worker M who is a user of the medical support system 30 logs in to the medical support system 30 from his / her own user terminal (medical worker terminal 11) (step S201), the medical support system 30 authenticates (step). S202). When the medical support system 30 determines that the user is a legitimate user, a timeline list is displayed on the home screen (step S203). The home screen is, for example, a screen as shown in FIG.

When the medical worker M looks at the home screen on his / her user terminal 11 and selects a desired timeline (step S204), the medical support system 30 has a predetermined management authority for the logged-in medical worker M. Whether or not it is determined (step S205). If it is determined that the user does not have the predetermined management authority, the timeline of the selected group is displayed on the user terminal 11 without displaying the secret room creation button (step S206). When it is determined that the user has the predetermined management authority, the timeline of the selected group is displayed on the user terminal 11 while displaying the secret room creation button (step S207). The timeline display screen at this time is, for example, a screen as shown in FIG. 19, and is a timeline on the medical staff side (viewable only by medical staff) and a timeline on the patient side (viewable by all group members). At the right end of the tab for selecting and displaying one of the above, a secret story room creation button is displayed.

When the medical worker M looks at the timeline display screen on his / her user terminal 11 and clicks the secret talk room creation button (step S208), the medical information management system 100 uses the secret talk room name input screen. It is displayed on the terminal 11 (step S209). The secret story room name input screen is, for example, a screen as shown in FIG.

When the medical worker M looks at the secret story room name input screen on his / her user terminal 11 and inputs the secret story room name "only for hospital staff" (step S210), the medical information management system 100 inputs. A new secret story room S is created and registered in the selected group with the secret story room name (step S211). Then, the medical information management system 100 displays a selection screen of a user participating in the secret talk room S on the user terminal 11 (step S212). When the medical worker M looks at the secret talk room participation user selection screen on his / her user terminal 11 and selects a user to participate in the secret talk room S (step S213), the medical support system 30 determines the selected user. Is automatically invited to the new secret story room S (automatic invitation process). Through such steps, a new secret room S including the selected user as a room member is created and registered. After that, the home screen is displayed on the user terminal 11 (see step S215 in FIG. 14B). An example of the home screen at this time is shown in FIG. As can be seen from FIG. 22, the timeline list of the secret story room S newly created under the name of "hospital staff only" is included in the timeline list displayed on the home screen.

When the medical worker M looks at the home screen as shown in FIG. 22 on his / her user terminal 11 and selects the newly created timeline of the secret talk room S called “only the staff in the hospital” (step S216). ), The medical information management system 100 displays the timeline of the selected secret talk room S on the user terminal 11 (step S217). In this state, the medical worker M can freely post a message to the timeline of the secret talk room S without attaching a file or by attaching a desired file. FIG. 23 shows an example of the timeline of the secret story room S called “only the staff in the hospital”. This timeline is accessible only to room members of that secret room S.

When the medical worker M posts a message on the timeline of the secret story room S called "only the staff in the hospital" on his / her user terminal 11 (step S218), the medical information management system 100 sends the input message. Is registered and displayed on the timeline (step S219). Then, it is determined whether or not the input message has an attached file (step S220). If it is determined that there is no attached file, the series of processes ends. If it is determined that there is an attached file, the medical information management system 100 sets the accessible user range to all the room members of this secret story room S, and registers the attached file (step S221). The timeline control unit 122 of the secret room management unit 120 executes the registration of the input message and the display on the timeline. The posted attached file and the information related to the attached file are stored in the file registration unit 131 of the file management unit 130. This attachment is accessible only to room members of Secret Room S.

The file name of the attached file registered in this way is added to and displayed in the file list on the patient detailed information display screen (see FIG. 26) (step S222). Then, a series of processes is completed. Since this file list (file list) displayed on the patient detailed information display screen is visible only to the room members of the secret story room S, the group members of the group G in which the secret story room S is created can be seen. However, a person who is not a room member of this secret story room S cannot know the existence of the posted file itself.

If it is determined in step S206 of FIG. 14A that the user does not have the predetermined management authority, the timeline of the selected group G is displayed on the user terminal 11 without displaying the secret talk room creation button. You can't create a new room, you can only post messages and attach files. At this stage, when the medical worker M posts a message on the timeline of the secret story room S called "only the staff in the hospital" on his / her user terminal 11 (step S223), the message (attached file is present). For example, the message and the attached file) are executed in steps S224 to S227 of FIG. 14C, and the processing performed there is the same as the processing of steps S219 to S222 of FIG. 14B. In this way, a series of processes is completed.

(Posting to the timeline of the existing secret story room)
15A and 15B are flowcharts showing a series of operations when posting a message or a file to the timeline 151 of the existing secret talk room S in the medical information management system 100 that operates in cooperation with the medical support system 30. ..

First, when the medical worker M who is a user of the medical support system 30 logs in to the medical support system 30 from his / her own user terminal (medical worker terminal 11) (step S231), the medical support system 30 authenticates (step). S232). When the medical support system 30 determines that the user is a legitimate user, the medical support system 30 determines whether or not the user is a participating user of any of the existing secret talk rooms S (step S233). Then, if it is determined that the user is not a participating user of any of the existing secret talk rooms S, a timeline list of only the group is displayed on the home screen (step S234). On the contrary, if it is determined that the user is a participating user of any of the existing secret talk rooms S, the timeline list of both the group and the secret talk room is displayed on the home screen (step S235). The home screen at this time is, for example, a screen as shown in FIG.

When the medical worker M looks at the home screen on his / her user terminal 11 and selects the timeline of the desired secret talk room (for example, the secret talk room S referred to as “hospital staff only”) (step S236), The medical information management system 100 displays the timeline of the selected secret talk room on the user terminal 11 (step S237). The timeline display screen at this time is, for example, a screen as shown in FIG. 23.

When the medical worker M looks at the timeline display screen on his / her user terminal 11 and posts a message to the timeline of the secret story room S called "only the staff in the hospital" (step S238), the medical information management system In 100, the input message is registered and displayed on the timeline (step S239). Then, it is determined whether or not the input message has an attached file (step S240). If it is determined that there is no attached file, the series of processes ends. If it is determined that there is an attached file, the medical information management system 100 sets the accessible user range to all the room members of the secret story room S, and registers the attached file (step S241). This attachment is accessible only to room members of Secret Room S.

The file name of the attached file registered in this way is added to and displayed in the file list on the patient detailed information display screen (step S242). Then, a series of processes is completed. Since this file list (file list) displayed on the patient detailed information display screen is visible only to the room members of the secret story room S, the group members of the group G in which the secret story room S is created can be seen. However, a person who is not a room member of this secret story room S cannot know the existence of the posted file itself.

In step S233 of FIG. 15A, when the medical support system 30 determines that the logged-in user is not a participating user of any of the existing secret talk rooms S, the timeline list of only the group is displayed on the home screen (step S234). ). At this stage, when the medical worker M posts a message on the timeline of the selected group G on his / her user terminal 11 (step S245), the message (if there is an attached file, the message and the attached file). Steps S246 to S249 of FIG. 15B are executed with respect to the above, and the processing performed there is the same as the processing of steps S239 to S242 of FIG. 15A. In this way, a series of processes is completed.

(Viewing files posted on the timeline of an existing secret room)
16A to 16C are flowcharts showing a series of operations when viewing a file posted on the timeline of an existing secret room in the medical information management system 100 that operates in cooperation with the medical support system 30.

First, when the medical worker M who is a user of the medical support system 30 logs in to the medical support system 30 from his / her own user terminal (medical worker terminal 11) (step S251), the medical support system 30 authenticates (step). S252). When the medical support system 30 determines that the user is a legitimate user, the medical support system 30 determines whether or not the user is a participating user of any of the existing secret talk rooms S (step S253). Then, if it is determined that the user is not a participating user of any of the existing secret talk rooms S, a timeline list of only the group is displayed on the home screen (step S254). On the contrary, if it is determined that the user is a participating user of any of the existing secret talk rooms S, the timeline list of both the group and the secret talk room is displayed on the home screen (step S255). The home screen at this time is, for example, a screen as shown in FIG.

When the medical worker M looks at the home screen on his / her user terminal 11 and selects the timeline of the desired secret talk room (for example, the secret talk room S referred to as “hospital staff only”) (step S256), The medical information management system 100 displays the timeline of the selected secret talk room on the user terminal 11 (step S257). The timeline display screen at this time is, for example, a screen as shown in FIG. 23.

When the medical worker M looks at the timeline display screen on his / her user terminal 11 and clicks the patient detailed information display button (see FIG. 23) (step S258), the medical information management system 100 has an existing secret story. It is determined whether or not the user is a participating user in the room S (step S259). Then, if it is determined that the user is not a participating user of any of the existing secret talk rooms S, a list of files posted only to the group is displayed on the patient detailed information display screen (step S260). On the contrary, if it is determined that the user is a participating user of any of the existing secret talk rooms S, a list of files posted to both the group and the secret talk room is displayed on the patient detailed information display screen (step S261). The patient detailed information display screen at this time is, for example, a screen as shown in FIG. 26.

When the medical worker M looks at the patient detailed information display screen on his / her user terminal 11 and selects a desired file (step S262), the medical information management system 100 displays the selected file on the user terminal 11. Open (step S263). Therefore, the medical worker M can browse the contents of the file on his / her user terminal 11 (step S264). When the medical worker M finishes browsing and clicks the button to close the file (step S265), the medical information management system 100 closes the opened file (step S266), and ends a series of processes.

In step S254 of FIG. 16A, when the medical support system 30 determines that the logged-in user is not a participating user of any of the existing secret talk rooms S, the timeline list of only the group is displayed on the home screen (step S254). ). At this stage, when the medical worker M selects the timeline of the desired group G on his / her user terminal 11 (step S267 in FIG. 16B), the timeline of the selected group is displayed (step S268). .. Then, when the medical worker M looks at the timeline display screen on his / her user terminal 11 and clicks the patient detailed information display button (see FIG. 23) (step S269), the medical information management system 100 causes the patient details. A list of files posted only to the group is displayed on the information display screen (step S270).

When the medical worker M looks at the file list on his / her user terminal 11 and selects a desired file (step S271), the medical information management system 100 opens the selected file on the user terminal 11 (step). S272). Therefore, the medical worker M can browse the contents of the file on his / her own user terminal 11 (step S273). When the medical worker M finishes browsing and clicks the button to close the file (step S274), the medical information management system 100 closes the opened file (step S275), and ends the process.

In step S259 of FIG. 16A, when the medical support system 30 determines that the logged-in user is not a participating user of any of the existing secret talk rooms S, it displays a list of files posted only to the group on the home screen. (Step S260). At this stage, when the medical worker M selects a desired file on his / her user terminal 11 (step S276 in FIG. 16C), the selected file is opened on the user terminal 11 (step S277). Therefore, the medical worker M can browse the contents of the file on his / her user terminal 11 (step S278). When the medical worker M finishes browsing and clicks the button to close the file (step S279), the medical information management system 100 closes the opened file (step S280), and ends a series of processes.

(Posting files directly to an existing secret room)
17A to 17C are flowcharts showing a series of operations when a file is directly posted to an existing secret room in the medical information management system 100 that operates in cooperation with the medical support system 30.

First, when the medical worker M who is a user of the medical support system 30 logs in to the medical support system 30 from his / her own user terminal (medical worker terminal 11) (step S301), the medical support system 30 authenticates (step). S302). When the medical support system 30 determines that the user is a legitimate user, the medical information management system 100 determines whether or not the user is a participating user of any of the existing secret talk rooms S (step S303). Then, if it is determined that the user is not a participating user of any of the existing secret talk rooms S, a timeline list of only the group is displayed on the home screen (step S304). On the contrary, if it is determined that the user is a participating user of any of the existing secret talk rooms S, the timeline list of both the group and the secret talk room is displayed on the home screen (step S305). The home screen at this time is, for example, a screen as shown in FIG.

When the medical worker M looks at the home screen on his / her user terminal 11 and selects the timeline of the desired secret talk room (for example, the secret talk room S referred to as “hospital staff only”) (step S306), The medical information management system 100 displays the timeline of the selected secret talk room on the user terminal 11 (step S307). The timeline display screen at this time is, for example, a screen as shown in FIG. 23.

When the medical worker M looks at the timeline display screen on his / her user terminal 11 and clicks the patient detailed information display button (step S308), the medical information management system 100 displays the patient detailed information display screen on the user terminal 11. Displayed above (step S309). The patient detailed information display screen at this time is, for example, a screen as shown in FIG. 26.

After that, when the medical worker M looks at the patient detailed information display screen on his / her user terminal 11 and clicks the file direct posting button (see FIG. 26) (step S310), the medical information management system 100 directs the file. The posting screen is displayed on the user terminal 11 (step S311). The file direct posting screen at this time is, for example, a screen in the format shown in FIG. 24.

When the medical worker M looks at the file direct posting screen on his / her user terminal 11 and selects the file to be posted directly (step S312), the medical information management system 100 displays the posting destination selection screen on the user terminal 11. (Step S313 in FIG. 17B). When the medical worker M looks at the posting destination selection screen on his / her user terminal 11 and selects a desired group or secret talk room as the posting destination (step S314), the medical information management system 100 selects the selected group. Alternatively, the file is directly posted to a predetermined location (for example, a predetermined folder for direct posting) in the secret talk room (step S315), the accessible user range for the file is set, and then the file is registered (step S316). Then, the file name of the directly posted file is additionally displayed in the file list on the patient detailed information display screen (step S317), and the process ends.

The posting destination selection screen in step S313 is, for example, a screen as shown in FIG. 25. In the posting destination selection screen of FIG. 25, the file in which the "Post" button is displayed in the file name is a file in which the posting destination is not specified. A file for which the "Post" button is not displayed in the file name is a file for which the posting destination has already been specified, and after the file name, for example, (secret story room "hospital staff only"). , The destination specified for the file is displayed. When you click the "Post" button, a list of timelines for groups or secret rooms that can be posted (similar to the home screen in Fig. 22) will be displayed, so select the timeline as the posting destination from among them. Just do it.

In step S303 of FIG. 17A, if it is determined that the medical worker M is not a participating user of any of the existing secret talk rooms S, a timeline list of only the group is displayed on the home screen (step S304). Then, when the medical worker M looks at the timeline list on his / her user terminal 11 and selects the timeline of the desired group (step S318 in FIG. 17C), the medical information management system 100 is displayed on the home screen. A timeline list of only groups is displayed (step S319). Subsequent steps S320 to S326 are the same as steps S306 to S312 of FIG. 7A. After that, steps S313 to S317 of FIG. 17B are executed to end the process.

As described above, in the medical information management system 100 according to the embodiment of the present invention, the service is received by the group management unit 320 of the medical support system 30 for the user of the medical support service provided by the medical support system 30. By generating a group G having a group ID which is a unique group identification information in relation to a patient ID which is a person identification information, and selectively assigning one or more of the above users to the group G as a group member. , Medical / nursing information of patients corresponding to group G can be shared among group members via a user terminal. Therefore, the medical / long-term care information of the patient corresponding to the group G can be shared among the group members belonging to the group G via the user terminal.

Further, after generating the secret story room S having the room ID which is the unique room identification information in relation to the group ID which is the group identification information, the group members belonging to the group G related to the secret story room S are generated. By selectively assigning at least a part of the above to the secret talk room S as a room member, the medical / long-term care information of the patient corresponding to the group G can be shared among the room members via the user terminal. To do. Therefore, the medical / long-term care information of the patient corresponding to the group G can be shared among the room members belonging to the secret talk room S via the user terminal. Here, since the room members of the secret story room S are at least a part of the group members, a part or all of the group members may be selected as the room members as needed. Therefore, the range of people who can access the medical / long-term care information of the patient corresponding to the group G can be easily changed.

Therefore, if necessary, the range of persons (accessible persons) who can access the individual medical / long-term care information of the target person (that is, the patient) of the medical support service posted by specifying who the information is about. Can be set arbitrarily. This is because one or more group G can be created for each patient who is the target person of the medical support service, but there is a restriction that the target person (patient) associated with each group G is limited to one person. It is irrelevant.

Further, the individual medical / long-term care information of the patient, which is posted by the secret talk room management unit 120 and the file management unit 130 of the medical information management system 100 by specifying who the information is about, is the medical / long-term care information. In order to store the information in association with the group ID of the group G or the room ID of the secret story room S to which the information is posted, an accessible person for each of the medical / long-term care information is a group member of the group G to which the information is posted. Alternatively, it is automatically set as a room member of the secret story room S. Therefore, the access authority to the medical / long-term care information of the target person (that is, the patient) posted by specifying who the information is can be centrally managed for each target person (that is, the patient). .. Further, this makes it possible to share the medical / long-term care information among a limited number of people while protecting the privacy of the target person.

The medical information management method according to the present invention is executed by the medical information management system 100 described above. The medical information management program according to the present invention is a program installed on a computer to realize the medical information management system 100 described above.

(Modification example)
The above-described embodiment shows an example embodying the present invention. Therefore, the present invention is not limited to this embodiment, and it goes without saying that various modifications can be made without departing from the gist of the present invention.

For example, in the above-described embodiment, the present invention is described as a medical information management system configured to cooperate with a medical support system, but the present invention is not limited thereto. It is possible to have a long-term care information management system configured to cooperate with a long-term care support system, or a medical / long-term care information management system configured to cooperate with a medical / long-term care support system that can support both medical care and long-term care. It goes without saying that it is possible to do so. Further, it is also possible to configure it as an independent medical / long-term care information management system without coordinating with other systems. In that case, the present invention provides various functions entrusted to the medical support system in the above embodiment. It is necessary to implement it in the medical / long-term care information management system. However, since the method of additionally implementing such various functions is clear from Patent Document 1 and the like, the description on this point will be omitted.

Further, in the above-described embodiment, the secret talk room S is created for the patient P, and the medical staff is allowed to participate as a room member, but the present invention is not limited to this. A secret story room S may be created for the person requiring long-term care, and a medical worker or a long-term care worker may participate as a room member. Any group member of the group to which an individual secret story room belongs can be a room member of that secret story room, if desired.

Further, in the above-described embodiment, an example in which one secret talk room Sa is created in the group Ga is described, but the present invention is not limited to this. It goes without saying that two or more secret talk rooms may be created in one group Ga. In addition, room members belonging to two or more secret talk rooms may be duplicated. That is, a room member with one secret room can be a room member of one or more other secret rooms at the same time.

10 Patient terminal 11 Medical person terminal 12 Patient related person terminal 20 Internet 30 Medical support system 51 Timeline 51a All shared area 51b Medical worker shared area 100 Medical information management system 110 User management unit 111 Registration unit 112 User information storage unit 113 User Participation control unit 120 Secret story room management unit 121 Secret story room registration unit 122 Timeline control unit 123 Secret story room information storage unit 130 File management unit 131 File registration unit 132 File browsing control unit 133 File posting control unit 134 File access control Department 151 Timeline of Secret Story Room 310 User Management Department 311 Registration Department 312 User Information Storage Department 313 Patient Information Storage Department 314 Medical Worker Information Storage Department 315 Medical Facility Information Storage Department 316 Disease Information Storage Department 320 Family Registration Management Department 321 Registration unit 322 Family facility information storage unit 323 Shared consent information storage unit 324 Patient existence verification unit 330 Group management department 331 Invitation request control unit 332 Invitation request information storage unit 333 Group information storage unit 334 Group member information storage unit 335 Timeline Control unit 336 Message control unit 337 Authentication unit 340 Authentication unit 350 Communication control unit F Medical facilities F1 Clinic F2 Clinic F3 Hospital F4 Visiting nursing station G group Ga Group G11 Patient P1 Diabetes treatment group G12 Patient P1 hyperlipidemia Treatment Group G13 Patient P1 Gout Treatment Group G21 Patient P2 Alzheimer Treatment Group G22 Patient P2 Hypertension Treatment Group M Medical Workers M1, M2, M3, M4, M5, M6, M7, M8 Medical Workers Ma , Mb, Mc, Md, Me, Mf, Mg Medical worker P Patient P1, P2 Patient Pa Patient R Patient related person R1, R2, R3, R4, R5, R6, R7, R8, Ra, Rb, Rc Patient relationship Person Ra, Rb, Rc Patient related person S, Sa Secret talk room

Claims (21)

By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or the long-term care recipient A method of managing the medical / nursing information by using a medical / nursing information management system that manages the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of the nursing service.
User identification information is assigned and stored for each user who uses the medical / nursing care service via the user terminal.
The service beneficiary identification information is assigned to the individual patient or the care recipient as the user, and the service beneficiary identification information is stored in association with the user identification information.
Business worker identification information is assigned to each medical worker or long-term care worker as the user, and the business worker identification information is stored in association with the user identification information.
In response to the instruction from the user terminal , a plurality of groups , each having a unique group identification information, are generated.
The group identification information of each of the plurality of groups is stored in a one-to-one correspondence with the service recipient identification information of the patient or the care recipient designated by the instruction from the user terminal.
Wherein in response to an instruction from the user terminal, by belong one or more of the users to the group of the designated 1 as a selective group members, corresponding to the service recipient identification information relating to the group medical and nursing care information of the patient or the care recipient, via the user terminal and can be shared between the group members,
In response to an instruction from the user terminal, one or a plurality of secret talk rooms each having a unique room identification information associated with the designated group identification information are generated.
In response to an instruction from the user terminal , at least a part of the group members of the group of 1 related to the secret room is selected to belong to the designated secret room of 1 as a room member. As a result, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the service recipient identification information related to the group posted to the secret story room can be obtained from the room member via the user terminal. In addition to making it possible to share between, it is possible to change the range of people who can access the medical / nursing information of the patient or the person requiring long-term care corresponding to the service recipient identification information related to the group.
When the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is posted to the group in response to an instruction from the user terminal. , When the medical / long-term care information is stored in association with the group identification information of the group to which the posting is made and posted to any one or more of the secret talk rooms related to the group, the relevant By storing the medical / nursing information in association with the room identification information of the secret story room to which the posting destination is posted, the access authority to the medical / nursing information can be given to the patient or the person requiring long-term care related to the medical / nursing information. A medical / long-term care information management method characterized by being able to be centrally managed for each . A person who is a group member of the group of 1 related to the designated secret room but is not a member of the room of the secret room is posted to the group posted to the secret room. The medical / long-term care information management method according to claim 1, which is set so as not to have access authority to the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information. In response to an instruction from said user terminal, when generating the secret story room associated with the group of the designated 1 1, at least part of the group members of the group of the secret story room is given as the room members, designated the group members medical and nursing information management method according to claim 1 or 2 is automatically invited to the secret story room becomes the room member. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the service beneficiary identification information of the designated 1 group is one or more of the group. When posted to any of the secret story rooms, all the room members of the posted secret story room are stored as accessible persons to the medical / long-term care information, according to claims 1 to 3. The medical / long-term care information management method described in either . In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
To one or more of the secret story timeline addressed provided any of the rooms of the timeline or the group provided the group, according to claim 1 to 4 can be post message format or file format The medical / long-term care information management method described in any of the above. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
It is possible to post directly in a file format to a predetermined direct posting location provided separately from the timeline provided in the group and the timeline provided in one or more of the secret talk rooms related to the group. The medical / long-term care information management method according to any one of claims 1 to 4. In response to the instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service recipient identification information related to the designated 1 group is posted to the secret talk room. Then, according to any one of claims 1 to 6, only the room member of the posted secret story room can confirm the posted medical / long-term care information on a predetermined posted information list screen. Medical / long-term care information management method. By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or long-term care recipient A system that manages the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of the long-term care service.
A user identification information storage means for assigning and storing user identification information to individual users who use the medical / nursing care service via the user terminal.
A service beneficiary identification information storage means that assigns service beneficiary identification information to each individual patient or care recipient as the user and stores the service beneficiary identification information in association with the user identification information.
A business worker identification information storage means that allocates business worker identification information to each medical worker or long-term care worker as a user and stores the business worker identification information in association with the user identification information.
In response to the instruction from the user terminal , a plurality of groups each having a unique group identification information are generated, and the group identification information of each of the plurality of groups is designated by the instruction from the user terminal. A group management means for storing the service recipient identification information of the patient or the person requiring nursing care in a one-to-one correspondence .
Wherein in response to an instruction from the user terminal, by belong one or more of the users to the group of the designated 1 as a selective group members, corresponding to the service recipient identification information relating to the group the medical and nursing care information for the patient or the care recipient, and group members selecting means for enabling shared between the group members via the user terminal,
A secret room management means for generating one or more secret rooms, each of which has unique room identification information associated with the designated group identification information of one in response to an instruction from the user terminal.
In response to an instruction from the user terminal , at least a part of the group members of the group of 1 related to the secret room is selectively assigned as room members to the designated secret room of 1. As a result, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the service beneficiary identification information related to the group posted to the secret story room can be obtained from the room member via the user terminal. Room member selection means that can be shared among people and can change the range of persons who can access the medical / nursing information of the patient or the person requiring long-term care corresponding to the service recipient identification information related to the group. When,
When the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is posted to the group in response to an instruction from the user terminal. , When the medical / long-term care information is stored in association with the group identification information of the group to which the posting is made and posted to any one or more of the secret talk rooms related to the group, the relevant By storing the medical / nursing information in association with the room identification information of the secret story room to which the posting destination is posted, the access authority to the medical / nursing information can be given to the patient or the person requiring long-term care related to the medical / nursing information. A medical / long-term care information management system characterized by being equipped with a means for storing posted information that can be centrally managed for each . A person who is a group member of the group of 1 related to the designated secret room but is not a member of the room of the secret room is posted to the group posted to the secret room. The medical / long-term care information management system according to claim 8 , which is set so as not to have access authority to the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information. In response to an instruction from said user terminal, when generating the secret story room associated with the group of the designated 1 1, at least part of the group members of the group of the secret story room is given as the room members, medical and nursing information management system according to claim 8 or 9, wherein the group member specified is automatically invited to the secret story room becomes the room member. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information of the designated 1 group is one or more of the group. When posted to any of the secret story rooms, all the room members of the posted secret story room are stored as accessible persons to the medical / long-term care information, according to claims 8 to 10. The medical / long-term care information management system described in either. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
The timeline addressed provided to any of the one or more of the secret story room according to the timeline or the group provided the group, according to claim 8. postable in a message format or file format The medical / long-term care information management system according to any one of 11 to 11. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
It is possible to post directly in a file format to a predetermined direct posting location provided separately from the timeline provided in the group and the timeline provided in one or more of the secret talk rooms related to the group. The medical / long-term care information management system according to any one of claims 8 to 11 . In response to the instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service recipient identification information related to the designated group 1 is posted to the secret talk room. Then, according to any one of claims 8 to 13, only the room member of the posted secret story room can confirm the posted medical / long-term care information on the predetermined posted information list screen. Medical / long-term care information management system. By making medical / long-term care information related to a specific patient or long-term care recipient viewable on the user terminal via a communication network in response to a request from the user terminal, medical care / long-term care for the patient or long-term care recipient A program that manages the medical / nursing information related to the patient or the person requiring long-term care when supporting the provision of long-term care services.
A process of assigning and storing user identification information to individual users who use the medical / nursing care service via the user terminal, and
A process of assigning service beneficiary identification information to each patient or person requiring care as a user and storing the service beneficiary identification information in association with the user identification information.
A process of assigning business worker identification information to an individual medical worker or long-term care worker as a user and storing the business worker identification information in association with the user identification information.
A process of generating a plurality of groups , each of which has unique group identification information , in response to an instruction from the user terminal .
A process of storing the group identification information of each of the plurality of groups in a one-to-one correspondence with the service recipient identification information of one patient or a care recipient designated by an instruction from the user terminal. When,
Wherein in response to an instruction from the user terminal, by belong one or more of the users to the group of the designated 1 as a selective group members, corresponding to the service recipient identification information relating to the group a process of the medical and nursing information of a patient or the care recipient, and can be shared among the group members via the user terminal,
A process of generating one or more secret talk rooms, each of which has unique room identification information associated with the designated group identification information of 1 , in response to an instruction from the user terminal.
In response to an instruction from the user terminal , at least a part of the group members of the group of 1 related to the secret room is selected to belong to the designated secret room of 1 as a room member. As a result, the medical / long-term care information of the patient or the person requiring long-term care corresponding to the service recipient identification information related to the group posted to the secret story room can be obtained from the room member via the user terminal. A process that enables sharing between the patients and a process that makes it possible to change the range of persons who can access the medical / nursing information of the patient or the person requiring long-term care corresponding to the service recipient identification information related to the group.
When the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is posted to the group in response to an instruction from the user terminal. , When the medical / long-term care information is stored in association with the group identification information of the group to which the posting is made and posted to any one or more of the secret talk rooms related to the group, the relevant By storing the medical / nursing information in association with the room identification information of the secret story room to which the posting destination is posted, the access authority to the medical / nursing information can be given to the patient or the person requiring long-term care related to the medical / nursing information. A medical / long-term care information management program characterized by having a computer execute processing that can be centrally managed for each <br />. A person who is a group member of the group of 1 related to the designated secret room but is not a member of the room of the secret room is posted to the group posted to the secret room. The medical / long-term care information management program according to claim 15, which is set so as not to have access authority to the medical / long-term care information of the patient or the long-term care recipient corresponding to the service recipient identification information. In response to an instruction from said user terminal, when generating the secret story room associated with the group of the designated 1 1, at least part of the group members of the group of the secret story room the is given as room members, the group members specified medical and nursing information management program according to claim 15 or 16 is automatically invited to the secret story room becomes the room member. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information of the designated 1 group is one or more of the group. When posted to any of the secret story rooms, all the room members of the posted secret story room are stored as accessible persons to the medical / long-term care information in claims 15 to 17. The medical / long-term care information management program described in either. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
The timeline addressed provided to any of the one or more of the secret story room according to the timeline or the group provided the group, according to claim 15 to 18 can be post message format or file format Medical / long-term care information management program described in any of. In response to an instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service beneficiary identification information related to the designated 1 group is
It is possible to post directly in a file format to a predetermined direct posting location provided separately from the timeline provided in the group and the timeline provided in one or more of the secret talk rooms related to the group. The medical / long-term care information management program according to any one of claims 15 to 18 . In response to the instruction from the user terminal, the medical / long-term care information of the patient or the long-term care recipient corresponding to the service recipient identification information related to the designated 1 group is posted to the secret talk room. Then, according to any one of claims 15 to 20, only the room member of the posted secret story room can confirm the posted medical / long-term care information on a predetermined posted information list screen. Medical / long-term care information management program.

Images