JP2011100362A - Information access control system, server device thereof, and information access control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To disclose personal information of a user only to valid users, and to easily and reliably set a user who browses the information. <P>SOLUTION: User relation information showing a relation between a user and other users is stored in a user relation management server MSV. An access control rule storing conditions for disclosing medical health related information of the user in association with the user relation, is stored in a data provision server PSV. When an information acquisition request is transmitted from a user terminal UT, an inquiry is made from the data provide server PSV to the user relation management server MSV about a relation between the user who made the request and the user in response to the information acquisition request. Whether to permit disclosure of the medical health related information of the user is determined on the basis of the answer result and the access control rule. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention provides information for realizing a service for providing user information, which is dispersed and stored in a database held by, for example, a medical institution, health-related organization, or local government, to the person or a third party authorized by the person. The present invention relates to an access control system, its server device, and an information access control method.

In recent years, EHR (Electronic Health Record) aims to provide integrated medical services and health services by interconnecting and sharing information related to medical care and health held by multiple medical institutions, health-related organizations, and local governments via communication networks. ) A system has been proposed.
The EHR system handles medical and health related information related to personal privacy. Privacy-related information can lead to serious damage to individuals, and its distribution and disclosure must be kept to a minimum. For this reason, in a conventional system that handles personal information, identification is performed by an authentication technique, and information related to the principal is basically referred to only by the principal (see, for example, Non-Patent Document 1).

Medical information and what EHR has brought about-Role of local community and self-management of information-Internet <URL: http://e-public.nttdata.co.jp/f/repo/602_j0902/j0902.aspx>

  However, in a situation where only the person can view medical health related information, it is difficult to utilize the medical health related information, and it is difficult to realize an integrated medical service rooted in the region aimed at in modern Japan. For example, it is not possible to obtain useful information from the viewer after having the other person browse the information, for example, having a doctor fully browse his / her information and receiving diagnosis and guidance. In order to make use of the information related to the medical health of the person, the person who wants to disclose information needs to have a mechanism that can be disclosed easily and without error.

  The present invention has been made paying attention to the above circumstances, and the purpose of the present invention is to allow the disclosure of the user's personal information only to an appropriate partner and to easily and reliably set the disclosure target user. An information access control system, a server device thereof, and an information access control method are provided.

In order to achieve the above object, one aspect of the present invention is that the personal information of the first user stored in the database is used as an information acquisition request transmitted from a terminal used by the second user as an information acquirer. In response to the system or method for searching and transmitting to the requesting terminal,
Means or process for managing user relationship information representing a relationship between the first user and a second user who permits the disclosure of the personal information, and the personal information of the first user in association with the user relationship information; A means or a process for managing an access control rule in which a disclosure condition is set;
When the information acquisition request including the identification information of the first and second users is sent from the terminal by the means or process for determining whether to permit or not access, the first and second information included in the information acquisition request The user relation management means and the access control rule management means are respectively accessed based on the identification information 2 and the individual of the first user with respect to the second user based on the user relation information and the access control rule. When it is determined whether or not the disclosure of the information is permitted, and the information disclosure is permitted as a result of the determination, the corresponding personal information is read from the database based on the identification information of the first user, and the acquisition request source terminal It is comprised so that it may transmit to.

  Accordingly, whether or not the personal information of the first user may be disclosed to other users is determined by associating the preset information indicating the human relationship with the first user and this user relationship with the disclosure condition. The determination is made based on the set access control rule. Therefore, the personal information of the first user is disclosed only to the second user who has a preset relationship with the first user and satisfies the disclosure conditions defined in the access control rule. Is done. Therefore, it is possible to receive advice by disclosing personal information to a second user who has a specific relationship, such as a family member or family doctor, for example, while preventing the problem of unlimited disclosure of personal information. It becomes. Also, once the disclosure conditions for users having a specific relationship are set, the disclosure condition setting operation for users having a similar relationship is simplified. In addition, it is easy for general users to understand, it is difficult to make mistakes in setting rules, and incorrect information is unlikely to be disclosed.

  For example, when the family doctor is changed due to moving, if there is no means or process related to the present invention, an error-free disclosure condition may be set in the access control rule for the new doctor. Necessary. However, according to the present invention, once the disclosure condition related to the human relationship “family” is set in the access control rule, even when the family doctor is added or changed, the “family” is included in the user relationship information of the user. Thus, the setting can be completed simply by adding a new doctor user, and it is not necessary to set the disclosure conditions for the new doctor user individually and in detail in the access control rule. Furthermore, once the disclosure condition related to the human relationship “Family” is set in the access control rule, even if the number of families increases due to marriage, for example, this new family user is added as “Family” to the human relationship information with the user concerned The disclosure conditions for the new family user need not be set individually and in detail in the access control rule.

Another aspect of the present invention is characterized by comprising the following aspects.
In the first aspect, when a user relationship acquisition request including identification information of the second user is sent from the terminal, user relationship management is performed based on the identification information of the second user included in the user relationship acquisition request. Means for accessing the means, searching for user relation information representing the relation between the second user and the first user who is permitted to disclose information to the second user, and transmitting it to the requesting terminal. Or it further comprises a process.

In the second aspect, in the means or process for managing access control rules, the attribute information of the second user, the information specifying the disclosure period or the non-disclosure period, and the disclosure target among the plurality of items constituting the personal information A means or process for managing an access control rule that further includes at least one of information specifying an item or non-disclosure target item as a disclosure condition, and determining whether access is permitted or not is included in the access control rule as a disclosure condition. The disclosure of the personal information of the first user to the second user, taking into account the attribute information of the second user, the information specifying the disclosure period or the non-disclosure period, or the information indicating the disclosure target item or the non-disclosure target item This is to judge permission.
In this way, in addition to human relationships such as “family” and “family”, the attribute information of the second user, information specifying the disclosure period or non-disclosure period, and the disclosure target item or non-disclosure target item are represented. It is possible to determine whether access is permitted by further considering at least one piece of information, and it is possible to realize finer access control.

  For example, by considering the name of the primary doctor or the name of the hospital to which the second user belongs as attribute information of the second user, the information is not disclosed unconditionally to all the primary doctors, but only for the primary doctor of the X internal medicine clinic. It is possible to perform disclosure restrictions such as disclosing Further, by considering a disclosure period or a disclosure prohibition period, information can be disclosed or not disclosed only in a specific period. For example, it is possible to refrain from unnecessary information disclosure by setting the information disclosure to the Y osteopathic clinic that only passes for a certain period for fracture treatment as 6 months from the first visit. Furthermore, by specifying the data items to be access controlled, disclosure / non-disclosure control for each data item can be performed. For example, disclosure control for each information item such as clarifying the name of an affected disease but not disclosing a specific treatment record can be made to his / her family.

  That is, according to the present invention, an information access control system, a server device thereof, and an information access control that make it possible to disclose a user's personal information only to an appropriate partner, and to easily and reliably set a user to be disclosed. A method can be provided.

It is a block diagram which shows the function structure of the information access control system concerning one Embodiment of this invention. It is a figure which shows the user relationship registration process sequence in the system shown in FIG. It is a figure which shows an example of the user relationship information registered by the user relationship registration process sequence shown in FIG. It is a figure which shows the other example of the user relationship information registered by the user relationship registration process sequence shown in FIG. It is a figure which shows the access control rule registration control sequence in the system shown in FIG. It is a figure which shows the access control rule update / deletion control sequence in the system shown in FIG. It is a figure which shows an example of the access control rule list | wrist registered by the access control rule registration control sequence shown in FIG. It is a figure which shows the case where information acquisition was able to be performed in the information acquisition process sequence of the system shown in FIG. It is a figure which shows the case where information acquisition cannot be performed in the information acquisition process sequence of the system shown in FIG. It is a block diagram which shows the function structure of the information access control system concerning other embodiment of this invention.

Embodiments according to the present invention will be described below with reference to the drawings.
1 is a functional block diagram showing an overall configuration of an information access control system according to an embodiment of the present invention.
The information access control system according to this embodiment includes a plurality of data provider servers PSV1 to PSVn operated by medical institutions, health-related institutions, exercise-related facilities, etc., a plurality of service cooperation servers SSV, an authentication server ASVa, A user registration server RSV and a user relationship management server MSV are provided, and these servers and these servers and the user terminal UT can be connected via a network NW.

  The network NW is composed of, for example, an IP network represented by the Internet, and a plurality of access networks for accessing the IP network. As the access network, for example, a local area network (LAN), a wireless LAN, a mobile phone network, a wired telephone network, and a cable television (CATV) network are used.

  The user terminal UT is used for general user terminals such as patients used at home, etc., and for doctors, public health nurses, pharmacists, etc. to obtain patient medical information upon request from patients. And a console terminal for an operator provided in the user registration server RSV.

  The data provide servers PSV1 to PSVn are obtained by connecting a program memory, a data memory for storing various databases, and a communication interface to a central control unit (CPU) via a bus. The application processing module 10, the information acquisition request processing module 11, the access control rule management module 12, the access control module 13, the cooperation processing module 14, and the user setting processing module 15 are provided. Any of these functional modules is realized by causing the CPU to execute a program stored in the program memory.

  The database includes a user database 16, a linkage ID database 17, an access control rule database 18, and an application database 19. The user database 16 stores user information for identifying and managing each user. The user information includes user identification information (ID), user basic information, user attributes, and the like. In the application database 19, personal information of each user, for example, medical health related information such as health guidance information and health diagnosis information is stored in association with the user ID.

  The cooperation ID database 17 stores ID cooperation information requested to be registered by the user registration server RSV. The ID linkage information is information for accessing personal data of a user who has the own server from another server.

  The access control rule database 18 represents an access control rule for setting under what conditions access to the medical health related information of the user stored in the application database 19 is permitted. Information is stored. FIG. 7 shows an example of this access control rule list.

In the access control rule, a plurality of rule items representing information disclosure conditions are described. This rule item is registered, for example, a data possessing user (managed by an ID or the like) indicating the owner of medical health related information, a data item to be an access control target (“target data-item”), and from what time to when "Target data-period", which is information indicating whether or not the data is subject to access control, "Target user" indicating who is subject to access restriction or permission, and which organization is subject to access restriction / permission “Target user-organization” indicating the target, “Target user-role” indicating what kind of qualification is subject to access restriction or permission, and data owner and what It is composed of “target user-relationship” indicating whether a person in a human relationship is a target of access restriction or permission. “Target data-item” includes, for example, disease name, medication name, weight, allergy information.
In addition to the above rule items, the access control rule represents an item indicating whether or not the user can read the medical health related information stored in the application database 19 and whether or not the medical health related information can be written. Items are listed.

  In addition, an item (“target user-authentication unit”) that limits an authentication unit that permits access is included, for example, access is permitted only when a user who is an access control target is authenticated with an IC card and a password. It is also possible to In addition, a “rule effective period” item indicating the effective period of the access control rule itself is included, thereby making it possible to disclose / not disclose information only in a specific period.

  In response to a request from the user registration server RSV, the user setting processing module 15 searches its own cooperation ID database 17 and user database 16, registers or deletes ID cooperation information in the cooperation ID database 17, and the user database 16 The user information is registered or deleted, and the result is returned to the user registration server RSV.

  The cooperation processing module 14 acquires authentication information from the authentication server ASVa, and exchanges attributes with other data provider servers PSV1 to PSVn using the ID association information stored in the cooperation ID database 17 (distribution of personal data). )I do. This attribute exchange processing is performed using a function such as an authentication linkage unit having a function such as SP in SAML (Security Assertion Markup Language) or a function such as WSC (Web Service Consumer) in ID-WSF (Identity Web Service Framework). Is called. SAML and ID-WSF are specifications for Web services defined by the Liberty Alliance.

The access control rule management module 12 performs an access control rule registration, update or deletion process for the access control rule database 18.
When the information acquisition request processing module 11 receives an information acquisition request transmitted from the service cooperation server SSV, the access control module 13 associates the information with the information that is the request target based on the received information acquisition request. With reference to the access control rule, it is determined whether or not the information can be read and written. When it is determined that access is possible, an information acquisition request is transferred to the application processing module 10 to perform processing for reading out medical health related information that is a request target.

  The application processing module 10 includes an application function that provides health guidance to the user based on the user's personal information such as health guidance information and health diagnosis information. This application function can use each function module in the data provider servers PSV1 to PSVn, and other parts can be freely created.

  Similar to the data provider servers PSV1 to PSVn, the authentication server ASVa is obtained by connecting a program memory, a data memory for storing a database, and a communication interface to a CPU via a bus. 21, a cooperation processing module 22, and a user setting processing module 23. Any of these functional modules is realized by causing the CPU to execute a program stored in the program memory.

  As a database, a user database 24, a linkage ID database 25, and a directory database 26 are provided. The user database 24 stores user information for identifying and managing each user. In the cooperation ID database 25, ID cooperation information requested to be registered by the user registration server RSV is stored. This ID linkage information is set for each server for each user. The directory database 26 stores directory data indicating the location of personal information, that is, which server holds which medical health related information.

  In response to a request from the user registration server RSV, the user setting processing module 23 searches its own ID linkage database 25 and user database 24, registers or deletes ID linkage information in the linkage ID database 25, and stores it in the user database 24. User information is registered or deleted, and processing for responding the result to the user registration server RSV is performed.

  The cooperation processing module 22 uses the user database 24, the cooperation ID database 25, and the directory database 26 to provide authentication information and a directory service to the data provider servers PSV1 to PSVn. The cooperation processing module 22 has an SP (Service Provider) function in ID-WSF for the above processing, and an IDP (Identity Provider) function in SAML.

  The authentication processing module 21 performs an authentication process for the user, and authenticates the validity of the user by referring to the user database 24 based on the user information input by the user at the user terminal UT. As an authentication method, various authentication methods such as ID / password authentication, IC card authentication, public key cryptography authentication, and multi-factor authentication can be used.

  Similar to the authentication server ASVa, the service cooperation server SSV has a CPU connected to a program memory, a data memory for storing a database, and a communication interface via a bus. A module 32, an access control rule setting management request module 33, an information acquisition request module 34, a cooperation processing module 35, and a user setting processing module 36 are provided. Any of these functional modules is realized by causing the CPU to execute a program stored in the program memory.

  As a database, a user database 37 and a cooperation ID database 38 are provided. The user database 37 stores user information for identifying and managing each user. In the cooperation ID database 38, registration is requested from the user registration server RSV and ID cooperation information is stored.

  In response to a search request from the user registration server RSV, the user setting processing module 36 searches its own user database 37 and the linkage ID database 38, registers or deletes ID linkage information in the linkage ID database 38, a user database The user information is registered or deleted in 37, and the search result is returned to the user registration server RSV.

  The cooperation processing module 35 acquires authentication information from the authentication server ASVa, and uses the cooperation ID database 38 to exchange attributes with the data provider servers PSV1 to PSVn, other service cooperation servers SSV, and the like. The SAML has a SP function for this attribute exchange process. Moreover, it has the function of WSC in ID-WSF.

  When the information acquisition request transmitted from the user terminal UT is received, the relationship search module 32 functions when presenting a list of users who are information acquisition targets. Process to search for the user who has.

  The information acquisition request module 34 uses the user information stored in the user database 37 to request the data provider servers PSV1 to PSVn to collect access control rule information and individual medical health related information.

  The access control rule setting management request module 33 adds or updates access control rule information to the access control rule database 18 for the data provider servers PSV1 to PSVn in response to an access control rule setting request sent from the user terminal UT. Or request deletion.

  The application processing module 31 includes an application for performing a list service of various medical / health related information regarding the requesting user in response to a request transmitted from the user terminal UT.

  Similarly to the authentication server ASVa and the like, the user registration server RSV has a CPU connected to a program memory, a data memory for storing a database, and a communication interface via a bus. A module 41 and a user setting processing module 42 are provided. As a database, a user database 43 is provided. This user database 43 stores user information of each user. Each of the function modules is realized by causing the CPU to execute a program stored in the program memory.

  The user setting processing module 42 updates the user information stored in its own user database 43 in response to an operation from the user or operator, and at the same time with respect to the authentication server ASVa, the data provider servers PSV1 to PSVn, and the service cooperation server SSV. Request user registration, update or deletion.

  Further, the association between the user ID, the authentication server ASVa, the data provider servers PSV1 to PSVn, and the user ID that is individually managed by the service cooperation server SSV, and the release process thereof are performed.

  Furthermore, in order to make the data provider servers PSV1 to PSVn available or unavailable, the authentication server ASVa is requested to register or cancel the service related information. A function for converting an anonymous ID (SAML or the like) used independently by each of the authentication server ASVa, the data provider server PSV1 to PSVn, and the service cooperation server SSV into a system common user ID, or from a system common user ID into each anonymous ID. Also have. Each server also has a user search function under specified conditions.

  Similarly to the authentication server ASVa and the like, the user relationship management server MSV has a CPU connected with a program memory, a data memory for storing a database, and a communication interface. A module 51, a cooperation processing module 52, an organization / role management module 53, and a user setting processing module 54 are provided. Any of these functional modules is realized by causing the CPU to execute a program stored in the program memory.

  The database includes a user relationship database 55, a user database 56, a cooperation ID database 57, an organization database 58, a role database 59, and a relationship name database 60. The user database 56 stores user information for identifying and managing each user. In the cooperation ID database 57, registration is requested from the user registration server RSV and ID cooperation information is stored.

  The relationship name database 60 stores specific names representing the human relationship between the user and the information acquisition user who has permitted the user to view his / her personal information. Specific names representing human relationships include, for example, “family”, “family”, and “work colleague”. The role database 59 stores role information of a user who is an information acquirer. The role information includes, for example, “doctor”, “health nurse”, “nurse”, which are roles identified by national qualifications in the field of health and welfare such as hcRole (health care role) discussed by ISO. A role name such as “Physiotherapist” is used. The organization database 58 stores the name of the organization to which the user who is the information acquirer belongs. Examples of the organization name include “A clinic”, “B citizen hospital”, “C fitness club”, and the like.

  The user relationship database 55 stores information representing a human relationship between a user and an information acquisition user who has permitted the user to view his / her personal information. 3 and 4 show an example of information representing human relationships stored in the user relationship database 55. FIG. That is, FIG. 3 shows the relationship information of citizen B, and the user who has created a personal relationship with citizen B on this system is citizen A, and the relationship is “family”. Moreover, FIG. 4 has shown the relationship information of citizen A, and citizen B, citizen C, X hospital x doctor, Y hospital y doctor, and Y hospital z public health nurse are users who have a human relationship with citizen A. It shows that. In addition, doctors x, y, and z public health nurses are all registered as a relationship of “family” of citizen A.

  The organization / role management module 53 manages the organization, role, and relationship name respectively stored in the organization database 58, role database 59, and relationship name database 60, and executes registration, update, or deletion of these information. Has function.

  In response to the request transmitted from the user registration server RSV, the user setting processing module 54 searches its own cooperation ID database 57 and user database 56, registers or deletes ID cooperation information in the cooperation ID database 57, Information is registered or deleted, and the result is returned to the user registration server RSV.

  When a user relation information search request is sent from the service cooperation server SSV and the data provider servers PSV1 to PSVn, the user relation management module 51 reads the user relation information of the user specified by this request from the user relation database 55. . Then, the read user relation information is returned to the requesting server.

Next, the operation of the system configured as described above will be described.
(1) Registration of user relation information First, registration processing of user relation information is performed as follows. FIG. 2 is a sequence diagram showing the processing procedure and processing contents.

  That is, it is assumed that the user himself / herself has performed an operation for requesting addition, deletion, or update of his / her user relation information while logged on to the system at the user terminal UT. Then, in response to this operation, a request for requesting addition, deletion or update of the user relationship information is transmitted from the user terminal UT to the service cooperation server SSV. When receiving the request, the service cooperation server SSV transfers the request to the user relationship management server MSV under the control of the application processing module 31.

  Upon receiving the request, the user relationship management server MSV newly registers the user relationship information in the user relationship database 55 according to the content of the request under the control of the user relationship management module 51, or the registered user relationship Update or delete information. Then, a response indicating the execution result (OK or NG) is returned. This response is sent from the user relationship management server MSV to the service cooperation server SSV, and is transferred from the service cooperation server SSV to the requesting user terminal UT.

  Thus, in the user relationship database 55 of the user relationship management server MSV, if the requesting user is a citizen B, for example, user relationship information as shown in FIG. 3 is registered. If the requesting user is a citizen A, for example, user relation information as shown in FIG. 4 is registered.

(2) Registration of access control rule Next, the registration process of the access control rule is performed as follows. FIG. 5 is a sequence diagram showing the processing procedure and processing contents.

  In other words, it is assumed that the user performs an operation for requesting registration of an access control rule representing a disclosure condition of his / her personal information while logged on to the system at the user terminal UT. Then, first, a search / selection request for a registration target organization, a registration target role, or a registration target relation name is transmitted from the user terminal UT to the service cooperation server SSV. Upon receiving the search / selection request, the service cooperation server SSV transmits the search / selection request to the user relationship management server MSV under the control of the access control rule setting management request module 33.

  Upon receiving the access control rule search / selection request, the user relationship management server MSV receives access control rules from the organization database 58, role database 59, or relationship name database 60 under the control of the organization / role management module 53, respectively. When editing, information indicating the organization name, role name, or relation name that is a candidate to be described in the item is read. Then, the information representing the read organization name, role name, or relation name is returned to the service cooperation server SSV. Information representing the organization name, role name, or relationship name is sent to the requesting user terminal UT via the service cooperation server SSV and displayed on the display.

  In this state, on the user terminal UT, the user selects a desired one from the displayed organization name, role name, or relationship name candidate and inserts it into the corresponding item in the access control rule. For other items constituting the access control rule such as “target data-period”, “target user-authentication means”, “rule validity period”, “readability”, “writeability”, etc. Is inserted manually. Thus, the access control rule is edited.

  It is assumed that the editing of the access control rule is finished and the user performs a transmission operation. Then, a registration request for a new access control rule created by the above editing is transmitted from the user terminal UT to the service cooperation server SSV. When receiving the registration request, the service cooperation server SSV transmits the access control rule registration request to the data provider servers PSV1 to PSVn under the control of the access control rule setting management request module 33.

Upon receiving the access control rule registration request, the data provider servers PSV1 to PSVn receive the new access control rule sent together with the registration request under the control of the access control rule management module 12 and the requesting user ID. And stored in the access control rule database 18. Then, a response indicating the processing result (registration OK or NG information) is returned. This response is transmitted from the data provider servers PSV1 to PSVn to the service cooperation server SSV, and is transferred from the service cooperation server SSV to the requesting user terminal UT.
Thus, for example, access control rules as shown in FIG. 7 are additionally registered in the list in the access control rule database 18 of the data provider servers PSV1 to PSVn.

(3) Updating or deleting access control rules
The access control rule registered or registered in the access control rule database 18 is changed or deleted as follows. FIG. 6 is a sequence diagram showing the processing procedure and processing contents.

  In other words, it is assumed that the user performs a display request operation for his / her access control rule list while logged on to the system at the user terminal UT. Then, a display request for the access control rule list is transmitted from the user terminal UT to the service cooperation server SSV. When receiving the display request, the service cooperation server SSV transfers the display request to the data provider servers PSV1 to PSVn under the control of the access control rule setting management request module 33.

  When the data provider servers PSV1 to PSVn receive the display request, under the control of the access control rule management module 12, the access corresponding to the access control rule database 18 based on the ID of the display target user included in the display request. A list of control rule lists is read, and the read list of access control rule lists is returned. This list of access control rule lists is transferred and displayed to the requesting user terminal UT via the service cooperation server SSV.

  In this state, it is assumed that the user selects a rule to be changed or deleted from the displayed access control rule list and performs a change or delete operation. Then, a request for changing or deleting the selected rule is transmitted from the user terminal UT to the service cooperation server SSV. Upon receiving the rule change or deletion request, the service cooperation server SSV sends the rule change or deletion request to the data provider servers PSV1 to PSVn under the control of the access control rule setting management request module 33. Forward.

When the data provider servers PSV1 to PSVn receive the request for change or deletion, the access control rule database 18 stores the access control rules stored in the access control rule database 18 under the control of the access control rule management module 12. For changing or deleting the rule specified by the request. Then, a response indicating the processing result (change or deletion OK or NG information) is returned. This response is transmitted from the data provider servers PSV1 to PSVn to the service cooperation server SSV, and is transferred from the service cooperation server SSV to the requesting user terminal UT.
Thus, the access control rules stored in the access control rule database 18 of the data provider servers PSV1 to PSVn are changed or deleted.

(4) Acquisition of user's medical health related information Here, a case where citizen B who is the family of the citizen A acquires the medical health related information of the citizen A stored in the data provider users PSV1 to PSVn will be described as an example. To do. 8 and 9 are sequence diagrams showing the procedure of the acquisition process and the processing content.

  When the citizen B logs into the system at the user terminal UT, the authentication procedure for the citizen B is first executed between the user terminal UT and the authentication server ASVa. Then, when the validity of the citizen B is confirmed by this authentication procedure and the citizen B performs an operation for acquiring his own user relationship information, a request for acquiring the user relationship information is transmitted from the user terminal UT to the service cooperation server SSV. The Upon receiving the user relationship information acquisition request, the service cooperation server SSV first generates a user relationship search / designation request for citizen B under the control of the relationship search module 32, and sends this request to the user relationship management server MSV. Send to.

  When the user relationship management server MSV receives the user relationship search / designation request, the user is a list of users who have a human relationship with the requesting citizen B from the user relationship database 55 under the control of the user relationship management module 51. The related information is searched, and the searched user related information is returned to the requesting user terminal UT. In the user terminal UT, the user relation information is displayed on the display.

  In this state, it is assumed that the citizen B selects the citizen A as the information acquisition target user from the displayed user list. Then, an information acquisition request including the user ID of the selected citizen A and the user ID of citizen B who is the information acquirer is transmitted from the user terminal UT to the service cooperation server SSV. Upon receiving the information acquisition request, the service cooperation server SSV transmits the information acquisition request to the data provider servers PSV1 to PSVn under the control of the information acquisition request module 34.

  When the data provider servers PSV1 to PSVn receive the information acquisition request, first, data necessary for the access control module 13 to process the received information acquisition request under the control of the information acquisition request processing module 11 After conversion into the format, the converted information acquisition request is transferred to the access control module 13. When the access control module 13 receives the information acquisition request, the access control module 13 determines whether or not the transmission source user (citizen B) has the authority to acquire the medical health related information of the citizen A as follows. .

  That is, first, a request for confirmation of user relation information of the requesting user (citizen B) is transmitted to the user relation management server MSV. Upon receiving the confirmation request, the user relationship management server MSV reads the user relationship information of the requesting user (citizen B) from the user relationship database 55 under the control of the user relationship management module 51, and stores this user relationship information as data. Return to the provide servers PSV1 to PSVn.

  Next, referring to the received user relationship information and the access control rules of citizen A stored in the access control rule database 18, whether citizen B has the authority to acquire medical health related information of citizen A or not. Determine. For example, “family” is set as the relationship with the target user as shown in FIG. 7 in the access control rule 1 of the citizen A, while the citizen A is the citizen in the user relationship information of the citizen B as shown in FIG. If it is registered as a family of B, it is determined that citizen B has the authority to acquire information related to medical health of citizen A.

  When it is confirmed that the citizen B is a person who has the authority to acquire the medical health related information of the citizen A, the access control module 13 transfers the received information acquisition request of the citizen A to the application processing module 10. To do.

The application processing module 10 selectively reads out the medical health related information of the citizen A from the application database 19 according to the transferred request, and transfers the read medical health related information of the citizen A to the access control module 13. The access control module 13 transfers the transferred medical health related information of the citizen A to the information acquisition request processing module 11, and the information acquisition request processing module 11 returns the medical health related information of the citizen A as a response. This response is transmitted to the requesting user terminal UT via the service cooperation server SSV.
Thus, the citizen B who is a family of the citizen A can browse the medical health related information of the citizen A at the user terminal UT.

  On the other hand, in the process of determining whether or not there is an information acquisition authority by the access control module 13 of the data provider servers PSV1 to PSVn, the citizen B is not set as the “family” of the citizen A, and the “family” doctor or public health nurse , It is determined that it is not registered. In this case, the access control module 13 of the data provider servers PSV1 to PSVn does not permit the reading and writing of the medical-related health related information of the citizen A based on the determination result (NG). Then, an NG response to refuse information acquisition is returned to the information acquisition request processing module 11 as shown in FIG. This NG response is returned from the data provider servers PSV1 to PSVn to the requesting user terminal UT via the service cooperation server SSV.

  As described above in detail, in this embodiment, the user relationship information representing the human relationship between the principal user and another user is stored in the user relationship management server MSV, and the medical relationship of the principal user is associated with the user relationship. Access control rules in which information disclosure conditions are set are stored in the data provider servers PSV1 to PSVn. Then, when an information acquisition request is transmitted from the user terminal UT, the user relationship from the data provider servers PSV1 to PSVn indicates the relationship between the acquisition request source user and the user in accordance with the information acquisition request. The management server MSV is inquired, and it is determined whether or not to permit disclosure of the medical health related information of the principal user based on the answer result and the access control rule. And only when it is permitted, the medical health related information of the principal user is read from the application database 19 and transmitted to the requesting user terminal UT.

  Therefore, only when the information acquisition requesting user has a preset relationship with the principal user and satisfies the disclosure conditions stipulated in the access control rules, The user's medical health related information is disclosed. For this reason, after preventing the trouble that the user's medical health related information, which is personal information, is disclosed indefinitely, the medical health related information is disclosed to users who have a specific relationship such as family members or family doctors. It is possible to receive advice.

  In addition, the organization name to which the user belongs, the disclosure validity period, and the information disclosure target item are further added as disclosure conditions to the access control rule, and the user included in the access control rule as the disclosure condition when determining whether access is permitted or not Based on the organization name, the disclosure validity period, and the disclosure target item, whether to permit disclosure of the medical health related information of the principal user to the user of the information acquisition request source is determined. For this reason, in addition to human relationships such as “family” and “family”, it is possible to determine whether access is permitted by further considering the organization name of the information acquisition request source user, the disclosure validity period, and the items to be disclosed. In addition, finer access control can be realized.

  Furthermore, user-related information or access control rules can be registered, changed, or deleted in response to a request from the user terminal UT. In addition, when this registration, change clothes or deletion process is performed, the registered user relation information is transmitted from the user relation management server MSV to the user terminal UT, and the user refers to this user relation information and the user relation information or Access control rule change processing is performed. For this reason, once a disclosure condition for a user having a specific relationship is set, a disclosure condition setting operation for a user having a similar relationship can be easily performed. Further, it is easy for a general user to understand, and it is difficult to make a mistake in setting a rule.

  The present invention is not limited to the above embodiment. For example, although the user relationship management server MSV is provided independently in the embodiment, the function of the user relationship management server MSV may be provided in the authentication server ASVb as shown in FIG. In this way, when the user terminal UT logs in to the system, the authentication server ASVb can simultaneously perform the authentication process of the login source user and the transmission of user relation information to the user. Further, when the data provider servers PSV1 to PSVn try to refer to the user relation information when determining whether to permit access, the user relation information can be acquired simultaneously with the authentication confirmation request to the authentication server.

In addition, the configuration of the data provider server, service cooperation server, user registration server, authentication server, user relationship management server, and a series of access control procedures using these servers are variously modified without departing from the scope of the present invention. Can be implemented.
In short, the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, you may combine suitably the component covering different embodiment.

  UT ... User terminal UT, PSV1-PSVn ... Data provide server PSV1-PSVn, ASVa ... Authentication server ASVa, ASVb ... Authentication server ASVa, SSV with user relation management function ... Service cooperation server SSV, RSV ... User registration server RSV, MSV ... user relationship management server MSV, NW ... network, 10, 31 ... application processing module, 11 ... information acquisition request processing module 11, 12 ... access control rule management module 12, 13 ... access control module 13, 14, 22, 35 , 52 ... cooperation processing module, 15, 23, 36, 42, 54 ... user setting processing module, 16, 24, 37, 43, 56 ... user database, 17, 25, 38, 57 ... ID database for cooperation, 18 ... Access Control rule database, 19 ... Application database, 21 ... Authentication processing module 21, 26 ... Directory database, 32 ... Relationship search module 32, 33 ... Access control rule setting management request module 33, 34 ... Information acquisition request module 34, 41 ... Use Operator operation processing module, 51... User relation management module, 53... Organization / role management module 53, 55... User relation database, 58.

Claims (9)

An information access control system that searches for personal information of a first user stored in a database in response to an information acquisition request transmitted from a terminal used by a second user as an information acquirer, and transmits the information to a requesting terminal. In
User relationship management means for managing user relationship information representing a relationship between the first user and a second user who permits the disclosure of the personal information;
An access control rule management means for managing an access control rule in which a disclosure condition of the personal information of the first user is set in association with the user relationship information;
When an information acquisition request including identification information of the first and second users is sent from the terminal, the user relationship management is performed based on the first and second identification information included in the information acquisition request. The user relation information and the access control rule of the corresponding user are read from the means and the access control rule management means, respectively, and the first user for the second user based on the read user relation information and the access control rule Access permission determination means for determining permission of disclosure of personal information,
Means for reading out the corresponding personal information from the database based on the identification information of the first user and transmitting it to the acquisition requesting terminal when information disclosure is permitted as a result of the determination. An information access control system. Among the means included in the information access control system according to claim 1,
A user relationship management server device comprising user relationship management means for managing user relationship information representing a relationship between the first user and a second user who permits the disclosure of personal information.   When an acquisition request for user relation information related to the second user is sent from the terminal, the user relation management means applies the user relation information corresponding to the second user identification information included in the acquisition request. 3. The user relationship management server apparatus according to claim 2, further comprising means for searching for and transmitting the request to the requesting terminal. Among the means included in the information access control system according to claim 1,
A personal information database storing personal information of the first user;
An access control rule management means for managing an access control rule in which a disclosure condition of the personal information of the first user is set in association with the user relationship information;
When an information acquisition request including identification information of the first and second users is sent from the terminal, the user relationship management is performed based on the first and second identification information included in the information acquisition request. The user relation information and the access control rule of the corresponding user are read from the means and the access control rule management means, respectively, and the first user for the second user based on the read user relation information and the access control rule Access permission determination means for determining permission of disclosure of personal information,
Means for reading out the corresponding personal information from the database based on the identification information of the first user and transmitting it to the acquisition requesting terminal when information disclosure is permitted as a result of the determination. A data provider server device characterized by the above. The access control rule management means designates a disclosure target item or a non-disclosure target item among a plurality of items constituting the second user attribute information, information specifying a disclosure period or a non-disclosure period, and personal information. Managing an access control rule that further includes at least one of the information as a disclosure condition;
The access permission / rejection determination unit includes attribute information of the second user included in the access control rule as a disclosure condition, information specifying a disclosure period or a non-disclosure period, or information indicating a disclosure target item or a non-disclosure target item. 5. The data provider server device according to claim 4, wherein whether to disclose the personal information of the first user to the second user is determined. Information access used in a system in which the user relationship management server device according to claim 2, the data provider server device according to claim 3, and a terminal used by the second user can be connected via a network. A control method,
The data provider server device manages an access control rule in which a disclosure condition for the personal information of the first user is set in association with the user relation information by using an access control rule database;
When the data provider server sends an information acquisition request including identification information of the first and second users from the terminal, based on the first and second identification information included in the information acquisition request. The user relation information and the access control rule of the corresponding user are read from the user relation management server device and the access control rule database, respectively, and the second user is read based on the read user relation information and the access control rule. Determining whether to permit disclosure of personal information of the first user;
If the data provider server is permitted to disclose information as a result of the determination, the data provider server reads out the corresponding personal information from the database based on the identification information of the first user and transmits it to the acquisition requesting terminal. And an information access control method.   When the user relationship management server device sends a user relationship acquisition request including identification information of the second user from the terminal, based on the identification information of the second user included in the user relationship acquisition request, 7. The method according to claim 6, further comprising a step of retrieving corresponding user relationship information managed by the user relationship management means and transmitting the retrieved user relationship information to a requesting terminal. Information access control method. The process of managing the access control rule includes the second user attribute information, information specifying a disclosure period or a non-disclosure period, and a disclosure target item or a non-disclosure target item among a plurality of items constituting personal information. Managing an access control rule that further includes at least one of the specified information as a disclosure condition;
The process of determining whether or not to disclose the personal information includes the attribute information of the second user included in the access control rule as a disclosure condition, information specifying a disclosure period or a non-disclosure period, a disclosure target item, or a non-disclosure target item 8. The information access control method according to claim 6, wherein whether or not the second user is allowed to disclose personal information of the first user is determined in consideration of information representing When the user relationship management server device receives a search request for user relationship information related to the first user transmitted from the terminal, reads the corresponding user relationship information and transmits it to the requesting terminal When,
When the data provider server device receives information indicating a new access control rule that is transmitted from the terminal and is edited based on the user relationship information transmitted from the user relationship management server device. 9. The information access control method according to claim 6, further comprising a step of storing information representing the new access control rule in the access control rule database.

Images