WO2023188135A1 - System, distribution control server, control method for distribution control server, and recording medium - Google Patents

Abstract

Provided is a system which enables a user to confirm the content of data to be distributed. The system comprises a service server and a distribution control server that controls the data distribution. The service server is operated by a service provider and accumulates a plurality of pieces of data generated by providing the service to the user. When data to be distributed among the plurality of pieces of accumulated data is distributed from the service server to a server of a provider that is different from the service provider, the distribution control server presents, to the user, the data to be distributed.

Description

System, distribution control server, distribution control server control method, and storage medium

The present invention relates to a system, a distribution control server, a distribution control server control method, and a storage medium.

There are information distribution systems that provide personal information held by hospitals, etc., to equipment provided by information providers, such as businesses, based on the consent of the individual.

For example, the information transaction device of Patent Document 1 stores catalog information that includes detailed information regarding one or more datasets that include personal information that can be provided from an information source device to an information destination device. The information transaction device receives a data set provision request from the information provision destination device. The information transaction device outputs a request to transmit the data set indicated by the provision request to the information provider device.

Patent Document 2 states that information regarding the user's health condition is provided. The information providing system of Patent Document 2 includes a vital data acquisition means, an urgency determination means, a usefulness determination means, a consent determination means, and an information transmission means. The vital data acquisition means acquires the user's vital data. The urgency determining means determines whether or not the user has a symptom that requires an emergency, based on the vital data acquired by the vital data acquiring means. The usefulness determining means determines, for each destination, whether or not it is useful to transmit the information regarding the user's health condition to the destination, taking into consideration the determination result by the urgency determining means. The consent determination means determines whether the user has consented to transmitting information regarding his or her health condition to the destination determined to be useful by the usefulness determination means. The information transmitting means transmits information regarding the user's health condition to the recipient whose consent has been determined by the consent determination means.

International Publication No. 2021/085061 Japanese Patent Application Publication No. 2018-124853

As disclosed in Patent Document 1 and Patent Document 2, when providing personal data to a third party, the consent of the user is required. Here, in many information distribution systems, personal data is passed from the information provider to the information provider using an API (Application Programming Interface) prepared by the information provider. That is, personal data is distributed using an API prepared in advance.

However, due to restrictions on APIs used to distribute personal data, it is difficult for users to individually check their data. That is, it is difficult for the user to confirm the contents of each data entity. Unless users know the specific content of the data being distributed, they cannot decide whether or not to consent to the distribution of the data.

The main purpose of the present invention is to provide a system, a distribution control server, a control method for a distribution control server, and a storage medium that contribute to enabling users to check the contents of data to be distributed.

According to a first aspect of the present invention, there is a service server operated by a service provider that accumulates a plurality of data generated by providing services to users, and a distribution control server that controls data distribution. , the distribution control server distributes at least one data subject to the data distribution from among the plurality of accumulated data from the service server to a server of a different service provider than the service provider. A system is provided that presents the user with at least one piece of data to be distributed.

According to a second aspect of the present invention, there is provided a communication control section that is operated by a service provider and that communicates with a service server that accumulates a plurality of pieces of data generated by providing services to users; When at least one or more pieces of data from among the accumulated data are distributed from the service server to a server of a different service provider than the service provider, at least one or more pieces of data that are the target of the data distribution are distributed from the service server to a server of a different service provider than the service provider. A distribution control server is provided, comprising: a data distribution control unit that presents the data to the user.

According to a third aspect of the present invention, a distribution control server communicates with a service server that is operated by a service provider and accumulates a plurality of data generated by providing services to users. When at least one or more pieces of data from among the accumulated data are distributed from the service server to a server of a different service provider than the service provider, at least one or more pieces of data that are the target of the data distribution are distributed from the service server to a server of a different service provider than the service provider. Provided is a distribution control server control method for presenting data to the user.

According to the fourth aspect of the present invention, a computer installed in a distribution control server communicates with a service server operated by a service provider and which accumulates a plurality of data generated by providing services to users. and when distributing at least one data subject to data distribution from the plurality of accumulated data from the service server to a server of a different service provider than the service provider. A computer-readable storage medium is provided that stores a program for executing a process of presenting at least one piece of data to the user.

According to each aspect of the present invention, a system, a distribution control server, a control method for a distribution control server, and a storage medium are provided that contribute to enabling a user to check the contents of data to be distributed. Note that the effects of the present invention are not limited to the above. According to the present invention, other effects may be achieved instead of or in addition to the above effects.

FIG. 1 is a diagram for explaining an overview of one embodiment. FIG. 2 is a flowchart illustrating an example of the operation of one embodiment. FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment. FIG. 4 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 5 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 6 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 7 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 8 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 9 is a diagram illustrating an example of a display on a terminal according to the first embodiment. FIG. 10 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 11 is a diagram showing an example of catalog information according to the first embodiment. FIG. 12 is a diagram for explaining the operation of the information distribution system according to the first embodiment. FIG. 13 is a diagram illustrating an example of a display on a terminal according to the first embodiment. FIG. 14 is a diagram illustrating an example of the processing configuration of the distribution control server according to the first embodiment. FIG. 15 is a diagram showing an example of a part of the user information database according to the first embodiment. FIG. 16 is a diagram illustrating an example of the location information database according to the first embodiment. FIG. 17 is a diagram illustrating an example of the processing configuration of the service server according to the first embodiment. FIG. 18 is a diagram showing an example of the customer information database according to the first embodiment. FIG. 19 is a diagram showing an example of the processing configuration of the transaction server according to the first embodiment. FIG. 20 is a diagram illustrating an example of an account opener list according to the first embodiment. FIG. 21 is a diagram illustrating an example of a processing configuration of a terminal according to the first embodiment. FIG. 22 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. FIG. 23 is a sequence diagram showing an example of the operation of the information distribution system according to the first embodiment. FIG. 24 is a diagram illustrating an example of a display on a terminal according to Modification 2 of the first embodiment. FIG. 25 is a diagram illustrating an example of a display on a terminal according to Modification 3 of the first embodiment. FIG. 26 is a diagram illustrating an example of a display on a terminal according to modification 4 of the first embodiment. FIG. 27 is a diagram illustrating an example of the hardware configuration of a distribution control server according to the present disclosure.

First, an overview of one embodiment will be described. Note that the drawing reference numerals added to this summary are added to each element for convenience as an example to aid understanding, and the description of this summary is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks depicted in each drawing represent the configuration of functional units rather than the configuration of hardware units. Connection lines between blocks in each figure include both bidirectional and unidirectional connections. The unidirectional arrows schematically indicate the main signal (data) flow, and do not exclude bidirectionality. Note that, in this specification and the drawings, elements that can be explained in the same manner may be designated by the same reference numerals, so that redundant explanation can be omitted.

The system according to one embodiment includes a service server 101 and a distribution control server 102 that controls data distribution (see FIG. 1). The service server 101 is operated by a service provider and accumulates a plurality of data generated by providing services to users (step S1 in FIG. 2). The distribution control server 102 distributes data to be distributed from among a plurality of accumulated data from the service server 101 to a server of a business other than the service provider. The data is presented to the user (step S2).

When the distribution control server 102 distributes the data accumulated by the service server 101 to another business operator, the distribution control server 102 acquires the data to be distributed from the service server 101. The distribution control server 102 presents the acquired data (the data itself to be distributed) to the user and obtains the user's consent for the distribution of the data. In this way, the distribution control server 102 allows the user to confirm the contents of the data to be distributed.

Specific embodiments will be described in more detail below with reference to the drawings.

[First embodiment]
The first embodiment will be described in more detail using the drawings.

[System configuration]
FIG. 3 is a diagram showing an example of a schematic configuration of the information distribution system according to the first embodiment. As shown in FIG. 3, participating members (actors) of the information distribution system include information distribution businesses, service businesses, data utilization businesses, and trading businesses.

An information distribution business is a business that provides a platform for data distribution services (information distribution services) for personal data accumulated by service providers. The information distribution business operator controls data distribution between businesses (service businesses, data utilization businesses). The information distribution business includes a distribution control server 10.

The distribution control server 10 is a device that controls data distribution. The distribution control server 10 is a server device that controls (realizes) data distribution between service providers and controls data distribution between service providers and data utilization providers. The distribution control server 10 realizes an information distribution service for data held by a service provider.

A service provider is an entity that provides services to individuals. The service provider may be a private company or a public institution. Examples of service providers include medical institutions (hospitals, pharmacies, etc.) that provide medical services to users, insurance companies that sell insurance products, retailers, and educational providers that teach language, sports, art, etc. to customers. is exemplified.

Each service provider includes a service server 20 for providing services to customers. The service server 20 is managed and operated by a service provider. The service server 20 holds (stores) data generated when a service provider provides a service to a user, data necessary for providing a service to a user, and the like.

Service providers maintain user data related to services provided to users. The service server 20 is operated by a service provider and accumulates a plurality of data generated by providing services to users.

A data utilization business is an entity that does not provide services directly to individuals. Examples of data utilization businesses include businesses such as pharmaceutical companies. For example, a pharmaceutical company develops a new drug using data obtained from a service provider.

In addition, in this disclosure, an entity that does not provide services to individuals will be treated as a "data utilization business entity" and explained, but when a data utilization business entity provides services to users, it will be referred to as a "service business entity". It is natural to behave. That is, depending on the business form of the data utilization business, the data utilization business can also become a service provider.

The data utilization business is equipped with a data utilization server 30 for acquiring and utilizing data from the service business.

A transaction business operator is an entity that realizes a transaction between a service business operator and a data utilization business operator. Transaction operators realize data distribution between data generators (service operators) and data consumers (data utilization operators).

The transaction business operator is equipped with a transaction server 40 for realizing the data distribution.

A user who uses the information distribution system uses a terminal 50.

The devices shown in FIG. 3 are interconnected via a network. For example, the distribution control server 10 and the service server 20 are connected by wired or wireless communication means and configured to be able to communicate with each other.

The configuration shown in FIG. 3 is an example, and is not intended to limit the configuration of the information distribution system disclosed herein. For example, an information distribution business may include two or more distribution control servers 10. Furthermore, regarding trading businesses and data utilization businesses, the information distribution system includes data usage servers 30 and transaction servers 40 according to the number of businesses participating in the system.

[Summary system operation]
Next, the general operation of the information distribution system according to the first embodiment will be explained.

　Users conclude individual contracts with the service providers they wish to receive services from. For example, a user requests to enter into a new contract (a contract for enjoying a service) with a service provider while providing his/her name, etc. to the service provider.

For example, a user who wants to visit a hospital submits his or her health insurance card with his or her name written on it to the hospital. Alternatively, a user who wishes to purchase an insurance product accesses the service server 20 operated by the insurance company and registers as a member. Alternatively, for an EC (Electronic Commerce) business that provides services related to online shopping, the user accesses the service server 20 operated by the EC business and creates an account.

The service provider generates a "personal identification ID" for identifying new customers (users). For example, a hospital assigns a consultation ticket number for managing users (patients) and generates the consultation ticket number as a personal identification ID. Insurance companies and EC businesses generate membership numbers and the like as personal identification IDs for managing customers. The service server 20 stores the generated personal identification ID (eg, medical card number, membership number, etc.) in a database or the like.

Once the personal identification ID is generated, the user can receive services from the service provider. For example, a user receives medical services (health checkup, medical examination, etc.) from a hospital. Alternatively, the user purchases insurance products from an insurance company.

In order to make user data generated by service providers providing services to users, etc., subject to data distribution, it is necessary to "accumulate" the data. Data accumulation means that a service provider (user data provider) registers user data in an information distribution system as data that can be provided to a third party. The distribution control server 10 controls data accumulation so that data related to services provided to users by a data accumulator (service provider) is targeted for data distribution.

The accumulated data will be subject to data distribution. Furthermore, the accumulation of user data requires the consent of the user (the user from whom the user data was generated) (consent to data accumulation).

"Storage" is the subject of information distribution (data distribution) to user data held by a service provider, and a fee is paid to the user who consents to the storage.

"Sharing" and "providing" exist as means of data distribution in an information distribution system.

"Sharing" is a means for service providers to acquire data accumulated by other service providers. The distribution control server 10 controls data sharing for a first service provider to acquire data stored in a second service provider. For example, data distribution through "sharing" is used when an EC business acquires data generated by a hospital providing services to users. Through data sharing, insurance companies use data obtained from hospitals to provide better services to users.

"Sharing" is used to improve the convenience of service users themselves, so no compensation is paid to users for data distribution (compensation to users). This is because "sharing" is used to utilize data accumulated by other service providers in order for users to receive better services from service providers.

"Provision" is a means for a data utilization business to acquire data accumulated by other service businesses. The distribution control server 10 controls data provision for data utilization businesses to acquire data accumulated by service businesses. For example, when a pharmaceutical company obtains the results of a medical examination or medical examination from a hospital, data distribution through "provision" is used. Pharmaceutical companies use the data they obtain from hospitals to help develop new drugs.

"Provision" is a method used by data utilization businesses that do not directly provide services to users, so compensation for data distribution (compensation for users) is incurred. That is, when "provision" is performed, consideration is paid to the user.

The distribution control server 10 controls data sharing for a data sharing destination (a service provider receiving data supply) to acquire data accumulated at a data sharing source. The distribution control server 10 controls data provision for a data provider (a data utilization business to which data is supplied) to acquire data accumulated at a data provider.

<Creating a system account>
Users of the information distribution system must register in advance (user registration, system registration). More specifically, the user accesses the distribution control server 10 and performs procedures for creating an account. In the following description, the account generated in the information distribution system will be referred to as a "system account."

In order to generate a system account, the user operates the terminal 50 in his possession to access the distribution control server 10. In response to the access from the terminal 50, the distribution control server 10 displays a WEB page for generating a system account.

The user performs an operation (for example, pressing a predetermined button) to generate a system account. At this time, the distribution control server 10 acquires information necessary for generating the user's system account. Specifically, the distribution control server 10 acquires the user's login information (login ID, password) and personal information (name, date of birth, contact information, account information, etc.).

Upon acquiring login information, personal information, etc., the distribution control server 10 generates a user ID (Identifier) for uniquely identifying the user in the information distribution system.

The distribution control server 10 associates and stores the generated user ID, login information, personal information (for example, name, date of birth, contact information), etc. of the user. The distribution control server 10 stores this information in a "user information database." Details of the user information database will be described later.

The distribution control server 10 issues the generated user ID to the user (terminal 50). The terminal 50 stores the issued user ID.

<ID cooperation>
As mentioned above, "data accumulation" is required in order to make user data held by a service provider the subject of data distribution. In order to realize data accumulation, it is necessary to link the system account ID (user ID) and the ID (personal identification ID) generated by the service provider.

For example, as shown in FIG. 4, a user goes to a hospital counter and tells hospital staff that he or she wishes to utilize user data held by the hospital (applies for data utilization). The hospital staff inputs the user's personal identification information, the user's personal identification ID (eg, medical card number), and the company code into the hospital terminal 60.

Note that personal identification information is information for identifying the user. Examples of the personal identification information include the user's name or a combination of name and date of birth.

Further, the business code is identification information (ID) for identifying a service business that participates in the information distribution system. For example, hospitals and insurance companies are assigned different codes. The business code is shared among system participants (information distribution business, service business, data utilization business) by any means. For example, when a service provider participates in an information distribution system, the information distribution provider generates a provider code to be assigned to the service provider. The information distribution business operator notifies the service business operator, etc. of the generated business code.

The hospital terminal 60 transmits an "ID cooperation request" including the acquired personal identification information, personal identification ID, and business code to the distribution control server 10.

Alternatively, a user who wishes to utilize the user data of an EC company operates the terminal 50 to access the service server 20 of the EC company (see FIG. 5). The user logs into the EC company's account and applies for data utilization on the account. In response to the application, the service server 20 transmits an "ID cooperation request" including the user's personal identification information, personal identification ID, and business code to the distribution control server 10.

The distribution control server 10 receives, from the hospital terminal 60 and the service server 20, the personal identification information of the person requesting ID cooperation, the personal identification ID, and the company code of the service provider (for example, hospital, e-commerce company) that is the target of ID cooperation. get.

The distribution control server 10 identifies the service provider targeted for ID cooperation from the provider code. Further, the distribution control server 10 identifies the user registered in the system account from the individual identification information, and associates the service provider and the individual identification ID in the account of the identified user.

Once the personal identification ID is registered in the system account (ID linkage is completed), the service provider targeted for ID linkage will be able to "accumulate" user data of users who wish to utilize the data.

Note that a user's "application for data utilization" to a service provider can be interpreted as consent for the service provider to accumulate user data.

<Data accumulation>
When a service provider provides a service to a user, the service provider stores the user's personal identification ID and user data (personal data) in association with each other.

For users who have completed ID linkage (users who have applied for data utilization), the service provider will provide "location information" each time it stores user data (data resulting from service provision, data necessary for service provision). " is sent to the distribution control server 10.

For example, as shown in FIG. 6, when a hospital provides medical services to each of the users U1 to U3, the hospital maintains the results for each user. For example, the hospital holds the medical examination results (disease names; for example, data on stomach cancer, lung cancer, etc.) for each of the users U1 to U3.

The service provider (service server 20) associates and stores each user's personal identification ID and user data obtained as a result of service provision. For example, in the example of FIG. 6, the service server 20 uses a "customer information database" to store the personal identification IDs and medical examination results of each of the users U1 to U3 in association with each other. Note that details of the customer information database will be described later.

The service provider transmits "location information" to the distribution control server 10 every time it stores user data regarding a user who has consented to data storage. The location information is information regarding the storage location of user data (data storage entity; service provider), etc. The location information includes a personal identification ID, a business code, an ID and type of data to be held, and the like.

The distribution control server 10 stores the acquired location information in the "location information database." Details of the location information database will be described later. The location information database stores personal identification ID, business code, data ID, data type, etc. in association with each other.

<Browsing accumulated data>
The user can request the information distribution system to view the data accumulated by each service provider. Specifically, the user logs into the portal site provided by the distribution control server 10.

The user operates the terminal 50 to request the distribution control server 10 to view the stored data (see FIG. 7). At that time, the distribution control server 10 may acquire requirements (data requirements) that define the stored data that the user desires to view.

For example, the user may request to view data by specifying the type of data to be viewed and the requirements for the data to be supplied. For example, the user specifies the type of data and the data search period as requirements for the data supplied from the data accumulator (data requirements).

The "data type" included in the data requirements is set to the disease name, etc. The data search period specifies a period for searching for at least one piece of data to be distributed among a plurality of pieces of accumulated data. In this way, data requirements include data type and data search period. For example, the distribution control server 10 receives data requirements (requirements for data supplied from the service server 20) such as "disease names accumulated between January 1, 2021 and December 31, 2021" from the user. ;supply data requirements).

The distribution control server 10 uses the user's user ID and data type (in the above example, disease name) to identify the data storage person who has stored the data that the user desires to view. The distribution control server 10 transmits to the service server 20 an "accumulated data transmission request" including the personal identification ID corresponding to the specified data accumulator and data requirements (data type and data search period specified by the user).

The service server 20 identifies the user from the personal identification ID included in the stored data transmission request, and the data requirements (data type, data search period) specified in the stored data transmission request among the stored data of the specified user. Identify accumulated data that matches.

The service server 20 transmits the specified accumulated data to the distribution control server 10. The distribution control server 10 displays the acquired accumulated data on the user's terminal 50.

In this way, the distribution control server 10 transmits to the service server 20 a stored data transmission request that includes data requirements that define the data that the user desires to view. The distribution control server 10 presents accumulated data obtained from the service server 20 (for example, specific disease names such as stomach cancer) to the user.

As explained above, the distribution control server 10 has a function that allows users to check their own data holding status. That is, the distribution control server 10 includes a "data management function" that allows users to check their own data contents as needed.

<Data sharing>
A service provider who wishes to acquire data accumulated by another service provider (user data generated as a result of other service providers providing services to users) obtains the data through "sharing."

Here, with reference to FIG. 8, a case will be described in which insurance company C acquires user U1's data accumulated in hospitals A and B by "sharing". Note that hospital A includes a service server 20-1, and hospital B includes a service server 20-2. Furthermore, insurance company C includes a service server 20-3.

First, the user U1 operates the terminal 50 to access the WEB page of the insurance company C and purchases an insurance product. Insurance products sold by insurance company C have "benefits" attached to them. Specifically, benefits include ``discount on insurance premiums if you submit all test results'' and ``discount on initial fees if you submit the name of your previous year's disease.''

When the user U1 purchases an insurance product with the above-mentioned benefits, the insurance company C requests the distribution control server 10 to "share" the data (test results, disease name) set as conditions for granting the above-mentioned benefits. do. Specifically, insurance company C (service server 20-3) transmits a "sharing request" to distribution control server 10 (step S11).

The sharing request includes the personal identification ID of user U1 who is the subject of data distribution, the code of the data sharing partner, data requirements for the data for which data sharing is requested (data type, data search period), and data sharing requirements. Contains accompanying information that explains the purpose, etc.

In the above example of "discount on insurance premiums by submitting all test results," insurance company C uses the personal identification ID (for example, membership number) that manages user U1, the data type "test results," and the data search period. "Not specified" and the accompanying information "Insurance premium discount" are included in the sharing request. In addition, in the example of "Discount on initial fee by submitting last year's disease name", user U1's personal identification ID, data type "disease name", and data search period "January 1, 2021 to December 31, 2021" , the accompanying information ``Discount on initial fee by submitting last year's disease name'' is included in the sharing request. Note that the date on which the user purchases the insurance product is any day in 2022.

In the following explanation, we will use the example of ``discounting the initial fee by submitting the name of the disease from the previous year.''

Based on the information included in the sharing request, the distribution control server 10 identifies the user U1 who is the target of data distribution and the data accumulators (hospital A, hospital B) of the data to be distributed.

The distribution control server 10 acquires the specific content (user data) of the data type for which data sharing is requested from the data accumulators (hospital A, hospital B). Specifically, the distribution control server 10 transmits an "accumulated data transmission request" to the service servers 20-1 and 20-2 of hospitals A and B, respectively (step S12).

The distribution control server 10 obtains the disease names of the user U1 (the disease names accumulated within the data search period) accumulated by each of hospitals A and B in response to the accumulated data transmission request (step S13).

The distribution control server 10 transmits an inquiry regarding data sharing to the terminal 50 owned by the user U1 (step S14).

The terminal 50 that has received the data sharing inquiry acquires the user U1's intention regarding data sharing. For example, the terminal 50 uses a GUI (Graphical User Interface) to acquire the intention of the user U1.

In the above example, the terminal 50 displays the specific disease name of the user U1 (the name of the disease diagnosed in the previous year) and displays a GUI for acquiring the user's intention (see FIG. 9). .

The user U1 confirms the content of the specific data presented and decides whether or not to agree to data sharing. The terminal 50 acquires the intention of the user U1 (agreeing to data sharing or not) using the GUI.

The terminal 50 transmits a response to the data sharing inquiry (agreeing to data sharing or refusing data sharing) to the distribution control server 10 (step S15).

If the consent of the user U1 is obtained, the distribution control server 10 transmits a sharing instruction to the data accumulators (hospital A, hospital B) (step S16).

The service server 20-1 of hospital A and the service server 20-2 of hospital B, which received the sharing instruction, refer to the customer information database and select the service server that is the designated data sharing destination for the disease name of the target user U1. 20-3 (step S17).

Next, we will explain data distribution by "provision".

<Account opening>
Users who wish to receive compensation by providing data must open an account with a transaction operator. Opening an account for provision will be explained with reference to FIG.

The transaction business operator forms an alliance with at least one service business operator among the multiple service business operators participating in the information distribution system. For example, a trading company that handles medical data collaborates with medical institutions (hospitals, pharmacies, etc.). Alternatively, a trading business that handles education-related data collaborates with an education business. The transaction business operator stores a business code related to the partner service business operator.

Additionally, the transaction business operator stores the business code of the data utilization business operator. For example, when a trading business starts a transaction with a data utilization business, it generates a business code of the data utilization business. The business code of the data utilization business is shared among the information distribution business, transaction business, and data utilization business by any method.

The trading business operator sells user data (accumulated data) held by the affiliated service business operator to the data utilization business operator. For example, if the affiliated service provider shown in FIG. 10 is a medical institution, the transaction provider sells data held by the affiliated medical institution to a pharmaceutical company or the like. All or part of the consideration obtained from the sale of data will be paid to the users involved in the provided data.

As mentioned above, a user who wishes to obtain consideration by providing data through a transaction operator needs to open an account with the transaction operator (transaction server 40). Among the users who participate in the information distribution system, those who wish to earn profits by providing data open an "information account" in the transaction server 40.

The user presents the user ID issued by the distribution control server 10 to the transaction server 40 and opens an information account. Transaction server 40 stores the acquired user ID. The transaction server 40 manages user IDs of users who have opened accounts using an account opener list.

<Catalog information>
In order to realize data distribution by "provision", information distribution businesses prepare catalog information. The person in charge (system administrator) of the information distribution business defines catalog information that describes data that can be sold (see FIG. 11). Catalog information is information indicating details of data that the information distribution system can sell to data utilization businesses.

The data set name included in the catalog information shown in FIG. 11 is information for identifying the catalog information. For example, a data set related to a medical examination is given a data set name such as "Examination Results 1", and a data set related to medical examination results is given a data set name such as "Examination Results 1".

The catalog information includes the operator code of the service provider that handles the dataset. The data type indicates the type of data held by the service provider (accumulated data that can be provided to a third party). For example, information such as "height", "weight", and "blood pressure" in the medical examination results, and "disease name", "medication taking", and "examination results" in the medical examination results correspond to the data type. The data format defines the format in which data is provided.

The data utilization business obtains catalog information through the transaction business. More specifically, the data utilization server 30 transmits a “catalog information presentation request” to the transaction server 40.

Upon receiving the catalog information presentation request, the transaction server 40 transmits a "catalog information transmission request" to the distribution control server 10.

In response to receiving the catalog information transmission request, the distribution control server 10 transmits catalog information defined by the information distribution business to the transaction server 40.

The transaction server 40 selects catalog information regarding the partner service provider and transmits it to the data utilization server 30. For example, in the above example, the transaction server 40 selects catalog information related to the business of a pharmaceutical company and transmits it to the data utilization business. The data utilization business views the received catalog information and identifies the catalog information necessary for its own business.

<Data distribution by provision>
A data utilization business that wishes to acquire data accumulated by a service business will acquire the data through "provision."

Here, with reference to FIG. 12, a case will be described in which pharmaceutical company D acquires accumulated data (disease names) of hospitals A and B regarding users U1 to U3 by "providing".

First, a person in charge at pharmaceutical company D refers to the catalog information presented by the business operator and identifies necessary catalog information. Thereafter, the data utilization server 30, in accordance with the instructions of the person in charge, provides information including information on the data utilization business, a data set name of at least one specified catalog information, and data requirements regarding the data to be provided. The request is sent to the transaction server 40 (step S21).

The information on the data utilization business includes the name of the data utilization business, the business code, the data provider (data destination address), etc. The data requirements include data types, data search period, required amount of data, etc., such as "data of 100 or more disease names accumulated in 2021".

The transaction server 40 examines the obtained provision request. If no problem is found through the examination, the transaction server 40 transmits the obtained provision request and list of account openers to the distribution control server 10 (step S22).

The distribution control server 10 identifies the personal identification ID of the user who is listed in the account opener list and is related to the requested catalog information. In the example of FIG. 12, the distribution control server 10 specifies the personal identification ID for each of the users U1 to U3.

Thereafter, the distribution control server 10 acquires specific user data that matches the data for which data provision is requested from the data accumulators (hospital A, hospital B). Specifically, the distribution control server 10 sends an "accumulated data transmission request" including a personal identification ID and data requirements (data type, data search period) to the service servers 20-1 and 20-2 of Hospital A and Hospital B, respectively. (Step S23).

The distribution control server 10 obtains the disease names of the users U1 to U3 stored in each of hospitals A and B in response to the stored data transmission request (step S24).

The distribution control server 10 sends an inquiry regarding data provision to the contact information (email addresses that can be received by the terminal 50) of the users U1 to U3 (step S25).

The data provision inquiry includes information on the data provision requestor (pharmaceutical company D), information on the data accumulators (hospital A, hospital B), and the specific content of the data requested to be provided.

The terminal 50 that has received the inquiry for data provision displays a GUI for acquiring each user's intention regarding data provision. For example, the terminal 50 displays a GUI as shown in FIG. 13. The terminal 50 uses the GUI to obtain the user's intention (agree or disapprove to data provision).

The terminal 50 transmits a response to the data provision inquiry (agreeing to the data provision or refusing the data provision) to the distribution control server 10 (step S26).

The distribution control server 10 transmits a provision instruction to the data accumulators (hospital A, hospital B) regarding the users whose consent has been obtained (step S27). For example, as described above, when the provision of disease name data for 100 or more cases is requested, the distribution control server 10 sends information to the service server 20-1 regarding the disease name data of 100 or more users who have agreed to provide the data. , 20-2.

The service servers 20 of Hospital A and Hospital B, which have received the provision instruction, refer to the customer information database and transmit the user data of the consenting users to the designated data provision destination (Step S28). In the above example, if each of the users U1 to U3 agrees to provide data, the disease name data of the users including the users U1 to U3 is transmitted to the data utilization server 30.

In this way, the distribution control server 10, when distributing at least one or more data to be data distributed from among the plurality of data accumulated in the service server 20, is presented to the user. More specifically, the distribution control server 10 transmits an accumulated data transmission request to the service server 20, which includes data requirements that define at least one piece of data to be distributed among a plurality of accumulated data. . In response to receiving the stored data transmission request, the service server 20 identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server 10. The distribution control server 10 presents the acquired data to the user and acquires the user's intention regarding the distribution of the data (agree or refuse the data distribution).

Next, details of each device included in the information distribution system according to the first embodiment will be explained.

[Distribution control server]
FIG. 14 is a diagram showing an example of a processing configuration (processing module) of the distribution control server 10 according to the first embodiment. Referring to FIG. 14, the distribution control server 10 includes a communication control section 201, a user registration section 202, an ID cooperation section 203, a location information management section 204, an accumulated data acquisition section 205, and a data distribution control section 206. , a catalog information management section 207 , and a storage section 208 .

The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the service server 20. Furthermore, the communication control unit 201 transmits data to the service server 20. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.

The user registration unit 202 is a means for realizing the above-mentioned user registration (user system registration). The user registration unit 202 acquires personal information (name, date of birth, contact information, account information, etc.) from the user's terminal 50.

Upon acquiring the personal information, the user registration unit 202 generates a user ID for identifying the user. For example, the user registration unit 202 assigns a unique number each time a user registers with the system, and uses the assigned value as the user ID.

The user registration unit 202 stores the user ID and personal information in the user information database (see FIG. 15). Note that, as shown in FIG. 15, the user information database stores user IDs, personal information, and personal identification IDs for each service provider in association with each other. Further, the user information database shown in FIG. 15 is an example, and is not intended to limit the items to be stored. For example, the date and time of user registration may be registered in the user information database.

The user registration unit 202 transmits the generated user ID to the terminal 50.

The ID cooperation unit 203 is a means for realizing the above-mentioned ID cooperation. The ID collaboration unit 203 receives an “ID collaboration request” from a service provider's terminal (for example, the hospital terminal 60) or the service server 20. The ID cooperation request includes personal identification information, personal identification ID, and company code of the user who desires ID cooperation (registration of service provider).

The ID collaboration unit 203 searches the user information database using personal identification information (user's name, combination of name and date of birth, etc.) as a key, and identifies the corresponding user. The ID cooperation unit 203 sets the personal identification ID included in the ID cooperation request in the field corresponding to the business code in the personal identification ID field of the specified user. That is, the ID cooperation unit 203 identifies the user registered in the system account from the personal identification information, and associates the service provider with the personal identification ID in the account of the identified user.

The location information management unit 204 is a means for managing location information obtained from a service provider. The location information management unit 204 stores the location information acquired from each service server 20 in the location information database (see FIG. 16). As shown in FIG. 16, the location information database stores personal identification ID, business code, data ID, data type, and data storage date (location information processing date) in association with each other.

Note that the location information database shown in FIG. 16 is an example, and is not intended to limit the items to be stored. In the drawings including FIG. 16, for ease of understanding, the provider code is expressed using the name of the service provider.

The accumulated data acquisition unit 205 is a means for controlling viewing of accumulated data. When a user logs into a portal site and performs a predetermined operation on the portal site, the accumulated data acquisition unit 205 controls the user's viewing of accumulated data.

The accumulated data acquisition unit 205 determines the type of data that the user wishes to view (for example, disease name, test results, etc.) and the period during which the user wishes to view the data (viewing period), depending on the user's operations on the portal site. Obtain data requirements (for example, data search period), etc.

The accumulated data acquisition unit 205 searches the user information database using the user's user ID (the user ID of the logged-in user) as a key, and identifies the corresponding entry. The accumulated data acquisition unit 205 acquires the personal identification ID of each service provider from the personal identification ID field of the specified entry.

The accumulated data acquisition unit 205 searches the location information database using the acquired personal identification ID and the type of data that the user desires to view as keys, and identifies the corresponding entry. The accumulated data acquisition unit 205 acquires the operator code of the service operator that holds the user data that the user desires to view from the operator code field of the specified entry.

In Figures 15 and 16, when the user with the user ID "uID01" wishes to view user data of the data type "disease name", the business of Hospital A and Hospital B is determined based on the personal identification IDs "HL01" and "HL11". The user code is identified.

The accumulated data acquisition unit 205 transmits an "accumulated data transmission request" to the service server 20 corresponding to the specified operator code. The stored data transmission request includes the user's personal identification ID (personal identification ID managed by the specified service provider; medical card number, etc.), data requirements regarding the stored data that the user wishes to view (e.g. , data type, data search period), etc.

The accumulated data acquisition unit 205 receives accumulated data (user data) from the service server 20 that sent the accumulated data transmission request. The accumulated data acquisition unit 205 displays the acquired accumulated data on the user's terminal 50 (displays it on the portal site).

The data distribution control unit 206 is a means for controlling data distribution by "sharing" or "providing".

First, we will explain data distribution related to "sharing".

The data distribution control unit 206 receives a sharing request from the service server 20. The sharing request includes the personal identification ID of the user whose data is to be obtained, the code of the provider sending the sharing request, the data requirements for the data you wish to obtain (data type, data search period), the purpose of data sharing, etc. Includes accompanying information etc.

In the example of FIG. 8, the personal identification ID generated by insurance company C (service server 20-3) for user U1, the operator code of insurance company C, "disease name" as the data type, and the data search period (2021 1 year) and accompanying information will be included in the sharing request.

The data distribution control unit 206 identifies the data distribution target based on the personal identification ID and business code included in the sharing request. Specifically, the data distribution control unit 206 refers to the user information database shown in FIG. 15 and identifies the target person. In the above example, upon receiving a sharing request including the personal identification ID "EC01" from insurance company C, the data distribution control unit 206 determines that the user U1 is the target of data distribution from the entry in the first line shown in FIG. Understand that.

Thereafter, the data distribution control unit 206 uses the identified user's personal identification ID and the data type included in the sharing request to identify the service provider that has accumulated the data for which data sharing is requested. Specifically, the data distribution control unit 206 refers to the location information database shown in FIG. 16 and identifies a service provider that accumulates data corresponding to the data type included in the sharing request. In the above example, Hospital A and Hospital B are specified based on the personal identification IDs "HL01" and "HL11" of the user U1 and the data type "disease name" included in the sharing request.

Note that if the combination of the user's personal identification ID and the data type included in the sharing request is not stored in the location information database, the data distribution control unit 206 instructs the sender of the sharing request that data sharing is not possible. send a negative response indicating In the above example, if the combination of user U1's personal identification ID "HL01" or "HL11" and data type "disease name" is not registered in the location information database, a negative response will be sent to insurance company C (service server 20-3). ) will be sent to.

When the data distribution target and the data storage person to be distributed are identified, the data distribution control unit 206 acquires the specific content (user data) of the stored data for which data sharing is requested from the data storage person. .

In the above example, the data distribution control unit 206 acquires accumulated data from the service servers 20-1 and 20-2 of hospital A and hospital B. Specifically, the data distribution control unit 206 transmits a "request for transmitting stored data" to the service servers 20-1 and 20-2 of hospitals A and B, respectively.

In this case, the data distribution control unit 206, like the accumulated data acquisition unit 205, sends an accumulated data transmission request that includes the user's personal identification ID, data requirements included in the sharing request (data type, data search period), etc. Send to server 20.

The data distribution control unit 206 acquires the accumulated data accumulated by the service provider in response to the accumulated data transmission request. In the above example, the data distribution control unit 206 retrieves the specific disease name (for example, urticaria, getting sinusitis, depression).

Thereafter, the data distribution control unit 206 inquires about data sharing to the data distribution target. Specifically, the data distribution control unit 206 sends an inquiry regarding data sharing to the contact information of the data distribution target person. In the above example, the inquiry is sent to the terminal 50 owned by the user U1.

In addition, the data sharing inquiry includes the source of the data sharing request (data sharing destination), the data storage party, the specific content of the data to be shared (the stored data itself), and any accompanying information included in the sharing request. It will be done. In the above example, the data sharing inquiry includes insurance company C as the data sharing requester, hospitals A and B as the data accumulators, and the specific disease name (urticaria, etc.) of the user U1.

The data distribution control unit 206 receives a response to the data sharing inquiry from the terminal 50.

If the user refuses data sharing, the data distribution control unit 206 notifies the data sharing requester that data sharing is not possible. In the above example, the data distribution control unit 206 transmits a negative response to the sharing request to the insurance company C's service server 20-3.

If the user agrees to data sharing, the data distribution control unit 206 sends a sharing instruction to the data accumulator. In the above example, the sharing instruction is sent to the service servers 20-1 and 20-2 of hospital A and hospital B, which are data accumulators.

The sharing instruction includes the personal identification ID generated by the data accumulator, information regarding the data sharing destination, data requirements for the data sharing target (data type, data search period), etc. In the above example, the sharing includes the personal identification ID "HL01" of user U1, the address of insurance company C's service server 20-3, the data type "disease name", and the data search period "one year of 2021". The instruction is sent to hospital A's service server 20-1. An instruction to share similar content is sent to the service server 20-2 of hospital B.

In this way, the data distribution control unit 206 transmits a sharing instruction that includes the personal identification ID of the user (target person) who has consented to data sharing and is generated by the data accumulator.

Next, we will explain data distribution related to "provision".

The data distribution control unit 206 receives the request for provision and the list of account openers from the transaction server 40.

The data distribution control unit 206 identifies the catalog information that is requested to be provided from the dataset name included in the provision request.

The data distribution control unit 206 refers to the location information database and specifies the data type and personal identification ID corresponding to the business code included in the specified catalog information. In the example of FIG. 12, personal identification IDs corresponding to each of users U1 to U3 are specified.

The data distribution control unit 206 identifies the user who corresponds to the identified personal identification ID and is listed in the account opener list. The data distribution control unit 206 refers to the user information database and controls each user (at least one data distribution target person) who is the user corresponding to the identified personal identification ID and who is listed in the account opener list. ).

Once the data distribution target is specified, the data distribution control unit 206 transmits a stored data transmission request to the service server 20, as in the case of data sharing. The data distribution control unit 206 acquires the specific contents (user data) of the accumulated data for which data provision is requested from the data accumulator.

After that, the data distribution control unit 206 makes an inquiry to the data distribution target person about providing the data. Specifically, the data distribution control unit 206 sends an inquiry regarding data provision to the contact information of the data distribution target person. In the above example, if each of the users U1 to U3 has opened an information account with a trading company, an inquiry for data provision is sent to the terminal 50 owned by each user.

The data provision inquiry includes information regarding the source of the data provision request, information regarding the data storage person, and the specific content of the data requested to be provided.

The data distribution control unit 206 sends a provision instruction to the data storage person regarding the user whose consent has been obtained. The provision instructions include the personal identification ID of the user who has agreed to provide the data, information regarding the data provider (e.g., business name, business code, address of the data utilization server 30), and data requirements for the data to be provided. (data type, data search period), etc.

In this way, the data distribution control unit 206 transmits at least one piece of data to be distributed, which is acquired in response to transmitting the stored data transmission request to the service server 20, to the terminal 50 owned by the user. . The data distribution control unit 206 acquires from the terminal 50 whether or not the user has consented to at least one piece of data to be distributed. If the user agrees to make the data subject to data distribution the subject of data distribution, the data distribution control unit 206 transmits the data subject to data distribution to the service server 20 to the sharing destination and the providing destination. instruct them to do so.

The catalog information management unit 207 is a means for managing catalog information. Catalog information management unit 207 stores catalog information created by a system administrator in storage unit 208.

The catalog information management unit 207 receives a “catalog information transmission request” from the transaction server 40. In response to receiving the request, the catalog information management unit 207 transmits the catalog information stored in the storage unit 208 to the transaction server 40.

The storage unit 208 stores information necessary for the operation of the distribution control server 10. A user information database is constructed in the storage unit 208. Furthermore, a database or the like is constructed in the storage unit 208 in which service provider names and provider codes are stored in association with each other.

[Service server]
FIG. 17 is a diagram illustrating an example of a processing configuration (processing module) of the service server 20 according to the first embodiment. Referring to FIG. 17, the service server 20 includes a communication control section 301, an ID cooperation control section 302, a data distribution request section 303, a data accumulation control section 304, a transmission request processing section 305, and a data distribution section 306. , and a storage unit 307.

The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 301 transmits data to the distribution control server 10. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.

The ID cooperation control unit 302 is a means for controlling user ID cooperation. The ID cooperation control unit 302 obtains a request for ID cooperation from a user who is logged into an account using a GUI (Graphical User Interface) or the like. In response to a request from a user, the ID linkage control unit 302 provides information such as " "ID cooperation request" is sent to the distribution control server 10.

Note that the user's personal identification ID, personal identification information, user data, etc. are managed using a customer information database (see FIG. 18). As shown in FIG. 18, the customer information database holds information (flag) indicating whether or not user ID linkage has been completed. When the ID linkage is completed, the ID linkage control unit 302 sets a flag in the ID linkage status field of the corresponding user (in FIG. 18, a circle is set).

The data distribution request unit 303 is a means for requesting data distribution (data sharing) regarding user data to an information distribution business. The data distribution request unit 303 transmits a sharing request to the distribution control server 10 in response to an operation by a staff member of the service provider. Specifically, the data distribution request unit 303 sends information such as the personal identification ID of the user whose data is to be acquired, the operator code of the own device, and data requirements regarding the data desired to be acquired (data type, data search period), etc. A sharing request containing the information is sent to the distribution control server 10.

The data accumulation control unit 304 is a means for controlling the accumulation of user data resulting from providing services to users. The data accumulation control unit 304 associates the user's personal identification ID with the user's user data (data generated as a result of providing a service to the user, or data necessary for the service provided to the user). and stored in the customer information database.

As shown in FIG. 18, the data accumulation control unit 304 stores user data in a field corresponding to the type of generated data (stores specific data contents). At this time, the data accumulation control unit 304 generates a data ID for identifying the user data, and stores it in association with the user data and the data accumulation date. Note that FIG. 18 shows an example of a customer information database built in the service server 20-1 of hospital A.

Here, regarding users for whom ID linkage has been completed, the data storage control unit 304 transmits location information to the distribution control server 10 every time user data is stored in the customer information database. For example, consider a case where a service is provided to a user with personal identification ID "HL01" and disease name data is generated as a medical examination result. In this case, location information including the personal identification ID "HL01", the business code "Hospital A", the data ID "HLD01", and the data type "Disease name" is transmitted to the distribution control server 10.

The transmission request processing unit 305 is a means for processing the accumulated data transmission request received from the distribution control server 10.

The transmission request processing unit 305 searches the customer information database using the personal identification ID included in the stored data transmission request as a key, and identifies the corresponding entry. Further, the transmission request processing unit 305 reads the data ID and user data corresponding to the data requirements (data type, data search period) included in the accumulated data transmission request from the specified entry.

If the transmission request processing unit 305 succeeds in reading the user data, it transmits an acknowledgment including the read user data and data ID to the distribution control server 10. If the transmission request processing unit 305 fails to read the user data, it transmits a negative response to the distribution control server 10 indicating that the stored data transmission request cannot be processed normally.

The data distribution unit 306 is a means for realizing data distribution by "sharing" or "providing". The data distribution unit 306 processes the “sharing instruction” or “provision instruction” received from the distribution control server 10.

When receiving a sharing instruction, the data distribution unit 306 refers to the customer information database and identifies an entry corresponding to the personal identification ID, data type, and data search period included in the sharing instruction. For example, when receiving a sharing instruction including the personal identification ID "HL01", the data type "disease name", and the data search period "January 1, 2021 to December 31, 2021", the data distribution unit 306: The entries shown in the top and second rows of FIG. 18 are identified.

The data distribution unit 306 transmits the user data written in the corresponding data type field of the identified entry to the data sharing destination specified by the sharing instruction. In the example of FIG. 8, "hives" and "sinusitis" are transmitted to insurance company C's service server 20-3.

The data distribution unit 306 processes the provision instruction in the same way as the sharing instruction. The data distribution unit 306 transmits user data determined by the personal identification ID, data type, and data search period included in the provision instruction to the data provision destination specified by the provision instruction.

Note that the data distribution unit 306 may assign an ID to the supplied data so that the business operator receiving the data can associate the obtained data. For example, the data distribution unit 306 calculates a hash value of the user's personal identification information (for example, name or a combination of name and date of birth), and sends the hash value as the user's ID to the data distribution destination. Good too.

The storage unit 307 stores information necessary for the operation of the service server 20. For example, the storage unit 307 stores account information of each actor (service provider, user, information distribution provider), provider code, personal identification ID, etc. in association with each other.

[Data utilization server]
The processing configuration of the data utilization server 30 can be the same as that of the service server 20. The data distribution requesting unit 303 of the data utilization server 30 may present information to the user (such as an employee of a data utilization business) and accept operations from the user. Specifically, the data distribution request unit 303 displays a list of catalog information acquired from the transaction server 40, and sends a provision request including the data set name and data requirements of the catalog information selected by the user to the transaction server 40. You can send it to.

[Transaction server]
FIG. 19 is a diagram showing an example of a processing configuration (processing module) of the transaction server 40 according to the first embodiment. Referring to FIG. 19, the transaction server 40 includes a communication control section 401, an account opening section 402, a catalog information request section 403, a provision request processing section 404, and a storage section 405.

The communication control unit 401 is a means for controlling communication with other devices. For example, the communication control unit 401 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 401 transmits data to the distribution control server 10. Communication control unit 401 passes data received from other devices to other processing modules. The communication control unit 401 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 401. The communication control unit 401 has a function as a receiving unit that receives data from another device, and a function as a transmitting unit that transmits data to the other device.

The account opening unit 402 is a means for opening an account for a user who wishes to distribute data by provision. The account opening unit 402 acquires the user ID from the user's terminal 50. The account opening unit 402 adds the acquired user ID to the account opening person list (see FIG. 20).

The catalog information requesting unit 403 is a means for transmitting a "catalog information transmission request" to the distribution control server 10.

Upon receiving the “catalog information presentation request” from the data utilization server 30, the catalog information requesting unit 403 transmits a “catalog information transmission request” to the distribution control server 10.

In response to sending the request, the catalog information requesting unit 403 acquires the catalog information stored in the distribution control server 10. The catalog information requesting unit 403 selects catalog information related to a service provider with which the device itself is affiliated, and transmits it to the data utilization provider (data utilization server 30). Note that the catalog information requesting unit 403 selects catalog information regarding the affiliated service provider based on the operator code of the affiliated service provider and the operator code included in the catalog information.

The provision request processing unit 404 is a means for processing a provision request received from the data utilization server 30. The provision request processing unit 404 examines data requirements included in the provision request. Specifically, the provision request processing unit 404 examines the consistency between the data usage purpose of the data utilization business and the usage purpose of the target data type. For example, if the content is ``purpose of use: development of new drugs, data type: name of disease,'' the review will pass. In other words, the data utilization business operator (data utilization server 30) inputs the above-mentioned purpose of use and data type into the transaction server 40 at the time of requesting data provision.

If it passes the examination, the provision request processing unit 404 transmits the account opener list to the distribution control server 10 along with the provision request obtained from the data utilization server 30.

The storage unit 405 stores information necessary for the operation of the transaction server 40. The storage unit 405 stores the company code of the partner service provider.

[Terminal]
FIG. 21 is a diagram illustrating an example of a processing configuration (processing module) of the terminal 50 according to the first embodiment. Referring to FIG. 21, the terminal 50 includes a communication control section 501, a personal information input section 502, an inquiry processing section 503, an account information input section 504, and a storage section 505.

The communication control unit 501 is a means for controlling communication with other devices. For example, the communication control unit 501 receives data (packets) from the distribution control server 10. Furthermore, the communication control unit 501 transmits data to the distribution control server 10. Communication control unit 501 passes data received from other devices to other processing modules. The communication control unit 501 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 501. The communication control unit 501 has a function as a reception unit that receives data from another device, and a function as a transmission unit that transmits data to the other device.

The personal information input unit 502 is a means for inputting personal information into the distribution control server 10 during user registration. The personal information input unit 502 inputs personal information (name, date of birth, contact information, account information, etc.) into the distribution control server 10 using any means. For example, the personal information input unit 502 uses the GUI to obtain the above-mentioned personal information from the user, and transmits the obtained personal information to the distribution control server 10.

The personal information input unit 502 stores the user ID issued by the distribution control server 10 in the storage unit 505.

The inquiry processing unit 503 is a means for processing inquiries received from the distribution control server 10 during data distribution by sharing or data distribution by provision. The inquiry processing unit 503 displays a GUI that matches the content of the inquiry (data sharing, data provision). For example, the inquiry processing unit 503 displays the GUI shown in FIGS. 9 and 13 to obtain the user's intention (agree or disagree with data distribution). The inquiry processing unit 503 transmits a response including the user's intention to the distribution control server 10.

The account information input unit 504 is a means for inputting into the transaction server 40 information for opening an information account, which is necessary when distributing data by provision. Account information input unit 504 transmits the user ID of the user to transaction server 40 .

The storage unit 505 stores information necessary for the operation of the terminal 50.

[Hospital terminal]
Examples of the hospital terminal 60 include mobile terminal devices such as smartphones and tablets, computers (personal computers, notebook computers), and the like. The hospital terminal 60 can be any equipment or device as long as it accepts operations from hospital staff and can communicate with the distribution control server 10 and the like. Further, since the configuration of the hospital terminal 60 is obvious to those skilled in the art, detailed explanation will be omitted.

The hospital terminal 60 may send an ID cooperation request to the distribution control server 10 in response to an operation by a hospital staff member. The hospital terminal 60 also transmits the ID cooperation request to its own service server 20. The service server 20 (ID linkage control unit 302) sets a flag in the ID linkage status field of the user entry (customer information database entry) corresponding to the personal identification ID included in the ID linkage request.

[System operation]
Next, the operation of the information distribution system according to the first embodiment will be explained. FIG. 22 is a sequence diagram illustrating an example of the operation of the information distribution system according to the first embodiment. The operation of the system during data sharing will be described with reference to FIG. 22.

The service server 20 that is the data sharing destination transmits a sharing request to the distribution control server 10 (step S31).

The distribution control server 10 acquires accumulated data (user data; for example, specific disease name) of the data distribution target person (step S32).

The distribution control server 10 makes an inquiry to the data distribution target person about data sharing including the acquired accumulated data (step S33).

When consent for data sharing is obtained from the data distribution target, the distribution control server 10 transmits a sharing instruction to the service server 20 that is the data sharing source (step S34).

In response to receiving the sharing instruction, the service server 20 transmits the accumulated data of the data distribution target to the service server 20 of the data sharing destination (step S35).

FIG. 23 is a sequence diagram showing an example of the operation of the information distribution system according to the first embodiment. The operation of the system during data sharing will be explained with reference to FIG.

The transaction server 40 transmits a request for provision etc. to the distribution control server 10 (step S41).

The distribution control server 10 acquires the accumulated data of the data distribution target (step S42).

The distribution control server 10 makes an inquiry to the data distribution target person about providing data including the acquired accumulated data (step S43).

When consent for data provision is obtained from the data distribution target, the distribution control server 10 transmits a provision instruction to the service server 20 of the data provider (step S44).

In response to receiving the provision instruction, the service server 20 transmits the accumulated data of the data distribution target to the data provision destination (step S45).

<Modification 1 according to the first embodiment>
In the embodiment described above, the case where the data search period is included in the data requirements has been explained as an example. However, the data requirements may include other information instead of or in addition to the data search period. For example, the data requirements may include the number of pieces of data to be acquired from the data accumulator. For example, information such as "three accumulated data" may be included in the data requirements.

Alternatively, the data requirements may include the data search period and the number of data items. For example, the data requirements may include information such as "three disease names obtained in the year 2021."

<Modification 2 according to the first embodiment>
In the embodiment described above, the distribution control server 10 transmits a stored data transmission request to the service server 20 before inquiring the user regarding data distribution. However, the distribution control server 10 may transmit a stored data transmission request to the service server 20 when the user wishes to know the details of the stored data. That is, the distribution control server 10 may transmit a stored data transmission request to the service server 20 after making an inquiry about data distribution.

Specifically, the user's terminal 50 does not display the details of the data supplied to the outside (shared data, provided data) on the consent acquisition screen shown in FIGS. 9 and 13, but displays the type of data ( For example, disease name). At this time, the terminal 50 displays a button (for example, a details display button) for obtaining details of the supply data (see FIG. 24).

When the details display button is pressed, the terminal 50 notifies the distribution control server 10 of this fact. Specifically, the terminal 50 transmits a “supply data transmission request” to the distribution control server 10.

In response to receiving the supply data transmission request, the distribution control server 10 transmits a stored data transmission request to the service server 20. The distribution control server 10 transmits the accumulated data acquired from the service server 20 to the terminal 50 as a response to the supply data transmission request.

The terminal 50 displays the acquired accumulated data (details of the supplied data). Specifically, the terminal 50 displays a GUI as shown in FIG. 9 using the details of the acquired accumulated data.

In this way, the information distribution system presents the types of data that are subject to data distribution to the user, and when the user wishes to know the specific content (details) of the data that is subject to data distribution. In such cases, the specific details (specific disease name such as urticaria) may be presented. That is, if the user cannot decide whether or not to consent to data sharing, etc. by simply understanding the type of data for which data sharing, etc. is requested, the user can input that fact into the distribution control server 10. Based on a request from a user, the distribution control server 10 may present the user with detailed information regarding the data held by the user.

That is, when the user desires to view at least one piece of data to be distributed, the distribution control server 10 presents the data to be distributed to the user. Specifically, when a user wishes to view data subject to data distribution, the distribution control server 10 sends an accumulated data transmission request to the service server 20, including data requirements such as data type and data search period. Send. In response to receiving the stored data transmission request, the service server 20 identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server 10. The distribution control server 10 presents the transmitted data to a user who wishes to view the data.

<Modification 3 according to the first embodiment>
In the second modification of the first embodiment, the terminal 50 indicates the data type (“disease name” in the example of FIG. 24) regarding the data (shared data, provided data) that is scheduled to be supplied to the outside on the consent acquisition screen. I explained that it would be displayed.

On the consent acquisition screen, the terminal 50 may display the data type of the data scheduled to be supplied to the outside, and also display the information of the data accumulator of the data scheduled to be supplied to the outside. For example, the terminal 50 may perform a display as shown in FIG. 25. When the details display button shown in FIG. 25 is pressed, the terminal 50 transmits a “supply data transmission request” to the distribution control server 10.

Note that in order to realize the display shown in FIG. 25, the distribution control server 10 refers to the location information database and obtains the service provider and data storage date corresponding to the personal identification ID and data type. The distribution control server 10 may send an inquiry (data sharing inquiry, data provision inquiry) including the acquired service provider information and data storage date to the terminal 50.

In this way, the distribution control server 10 uses information (in the example of FIG. 25, the name of the hospital) of the service provider that accumulates at least one piece of data that is the subject of data distribution before sending the accumulated data transmission request. It may be presented to the person.

<Modification 4 according to the first embodiment>
In the above embodiment, the case where the user only needs to know the specific contents of the data supplied to the outside has been described. However, the externally supplied data may be selectable by the user.

In this case, the data sharing destination and data providing destination will set content such as "names of two diseases diagnosed in the year 2021" as data requirements.

The distribution control server 10 that receives the sharing request or provision request that includes the data requirements described above sets the data search period to "January 1, 2021 to December 31, 2021" and services the stored data transmission request. Send to server 20.

The distribution control server 10 transmits a data distribution inquiry including the data ID of the received accumulated data, accumulated data, etc. by transmitting an accumulated data transmission request to the terminal 50.

In response to receiving the inquiry, the terminal 50 displays a GUI as shown in FIG. 26. When the user selects two of the three disease names and presses the consent button, the terminal 50 not only indicates that the user has agreed to data sharing, but also sends the data ID of the stored data that the user has agreed to share to the distribution control server 10. Send.

The distribution control server 10 instructs the service server 20 that stores data corresponding to the acquired data ID to distribute data (data sharing, data provision). In the example of FIG. 26, the distribution control server 10 notifies hospital A of the data ID corresponding to "hives" and instructs hospital A to share the disease name (hives). Similarly, the distribution control server 10 notifies Hospital B of the data ID corresponding to "depression" and instructs it to share the disease name (depression).

As described above, the information distribution system according to the first embodiment includes a "data management function" that realizes user management regarding accumulated data. The user uses the data management function to check the details of his/her own accumulated data. That is, as described in the location information database of FIG. 16, the database only describes the data type, but does not describe the specific content (specific disease name such as urticaria). The data management function is a function that allows the user to check specific data contents. Furthermore, when acquiring user consent regarding data distribution (data sharing, data provision), the distribution control server 102 acquires specific content in units of data from the service server 101. The distribution control server 102 presents the acquired data (accumulated data itself; data to be distributed to other businesses) to the user. The user can confirm the specific data presented and consent to the distribution of the data (the data is acquired by a company other than the data accumulator). That is, since the user can make a decision after actually confirming the contents of the data to be distributed, it is possible to prevent data not intended by the user from being handed over to a business other than the data accumulator.

Here, existing data distribution systems are scope-type systems, and in many cases only data types such as "disease name" are provided to third parties. In this regard, the data distribution system disclosed in the present application is of an "entity type", and allows data to be provided to a third party for each data entity such as "depression." Further, the data distribution system disclosed in the present application employs data distributed management. In this regard, in a normal PDS (Personal Data Store), the PDS operator holds the data themselves and authorizes the data based on the consent of the user. In contrast, in the data distribution system disclosed in the present application, while the provider retains the data, the data distribution operator retains the data location information and authorizes the provision of the data to a third party based on the consent of the individual. As a result, a safer system is provided in which information leakage from data distribution companies is unlikely.

Next, the hardware of each device that makes up the information distribution system will be explained. FIG. 27 is a diagram showing an example of the hardware configuration of the distribution control server 10.

The distribution control server 10 can be configured by an information processing device (so-called computer), and has the configuration illustrated in FIG. 27. For example, the distribution control server 10 includes a processor 311, a memory 312, an input/output interface 313, a communication interface 314, and the like. The components such as the processor 311 are connected by an internal bus or the like and are configured to be able to communicate with each other.

However, the configuration shown in FIG. 27 is not intended to limit the hardware configuration of the distribution control server 10. The distribution control server 10 may include hardware that is not shown, and may not include the input/output interface 313 if necessary. Further, the number of processors 311 and the like included in the distribution control server 10 is not limited to the example shown in FIG. 27; for example, a plurality of processors 311 may be included in the distribution control server 10.

The processor 311 is, for example, a programmable device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs including an operating system (OS).

The memory 312 is a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. The memory 312 stores OS programs, application programs, and various data.

The input/output interface 313 is an interface for a display device or input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device such as a keyboard or a mouse that receives user operations.

The communication interface 314 is a circuit, module, etc. that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card).

The functions of the distribution control server 10 are realized by various processing modules. The processing module is realized, for example, by the processor 311 executing a program stored in the memory 312. Further, the program can be recorded on a computer-readable storage medium. The storage medium can be non-transitory, such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. That is, the present invention can also be implemented as a computer program product. Furthermore, the above program can be updated via a network or by using a storage medium that stores the program. Furthermore, the processing module may be realized by a semiconductor chip.

It should be noted that the service server 20, transaction server 40, etc. can also be configured by an information processing device in the same way as the distribution control server 10, and the basic hardware configuration is the same as that of the distribution control server 10, so a description thereof will be omitted. .

The distribution control server 10, which is an information processing device, is equipped with a computer, and the functions of the distribution control server 10 can be realized by having the computer execute a program. Further, the distribution control server 10 executes the control method of the distribution control server 10 using the program.

[Modified example]
Note that the configuration, operation, etc. of the information distribution system described in the above embodiments are merely examples, and are not intended to limit the configuration, etc. of the system.

In the above embodiment, a case has been described in which the user information database is configured inside the distribution control server 10, but the database may be configured in an external database server or the like. That is, some functions of the distribution control server 10 may be implemented in another server. More specifically, the above-described "data distribution control unit (data distribution control means)" etc. may be implemented in any device included in the system.

The form of data transmission and reception between each device (distribution control server 10, service server 20, etc.) is not particularly limited, but data transmitted and received between these devices may be encrypted. Personal information of users is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable that encrypted data be transmitted and received.

Although a plurality of steps (processes) are described in order in the flowcharts (flowcharts, sequence diagrams) used in the above description, the order in which the steps are executed in the embodiment is not limited to the order in which they are described. In the embodiment, the order of the illustrated steps can be changed within a range that does not affect the content, such as executing each process in parallel, for example.

The above embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all the configurations described above are necessary. Further, when a plurality of embodiments are described, each embodiment may be used alone or in combination. For example, it is also possible to replace a part of the configuration of the embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of the embodiment. Furthermore, it is possible to add, delete, or replace some of the configurations of the embodiments with other configurations.

The industrial applicability of the present invention is clear from the above description, and the present invention is suitably applicable to an information distribution system that distributes accumulated data regarding services provided to users.

Part or all of the above embodiments may be described as in the following additional notes, but are not limited to the following.
[Additional note 1]
A service server operated by a service provider and which accumulates multiple pieces of data generated by providing services to users;
A distribution control server that controls data distribution;
including;
The distribution control server, when distributing at least one data subject to the data distribution from the plurality of accumulated data from the service server to a server of a business other than the service business, A system that presents to the user at least one piece of data to be distributed.
[Additional note 2]
The distribution control server transmits an accumulated data transmission request to the service server, including a data requirement that defines at least one piece of data to be distributed among the plurality of accumulated data,
In response to receiving the stored data transmission request, the service server identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server. The system described in Appendix 1 for transmitting.
[Additional note 3]
The system according to supplementary note 2, wherein the data requirements include at least one data type of data that is a target of the data distribution.
[Additional note 4]
The system according to appendix 3, wherein the data requirements include a data search period that specifies a period for searching for at least one piece of data to be distributed among the plurality of stored data.
[Additional note 5]
The distribution control server is
transmitting at least one piece of data subject to the data distribution acquired in response to transmitting the stored data transmission request to the service server to a terminal owned by the user;
The method according to any one of Supplementary Notes 2 to 4, wherein information is obtained from the terminal as to whether or not the user has consented to at least one or more pieces of data to be subject to the data distribution. system.
[Additional note 6]
If the user agrees to make at least one or more data subject to the data distribution subject to the data distribution, the distribution control server sends at least one data subject to the data distribution to the service server. The system according to appendix 5, wherein the system instructs to send the data to a server of a different service provider than the service provider.
[Additional note 7]
7. The system according to any one of Supplementary Notes 1 to 6, wherein the distribution control server controls data sharing for a first service provider to acquire data stored in a second service provider.
[Additional note 8]
The system according to appendix 7, wherein the distribution control server controls data provision for a data utilization business to acquire data accumulated by the second service business.
[Additional note 9]
The distribution control server transmits the accumulated data transmission request including the data requirements defining data that the user desires to view to the service server, and presents the data obtained from the service server to the user. The system according to any one of Supplementary Notes 2 to 4.
[Additional note 10]
The distribution control server presents the user with at least one or more data to be distributed when the user desires to view at least one or more data to be distributed to the data. The system described in Appendix 1.
[Additional note 11]
When the user desires to view at least one piece of data to be distributed, the distribution control server may browse at least one piece of data to be distributed among the plurality of accumulated data. Sending a stored data transmission request to the service server, including data requirements that define data;
In response to receiving the stored data transmission request, the service server identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server. send,
The system according to appendix 10, wherein the distribution control server presents the transmitted data to the user who desires to view the data.
[Additional note 12]
Supplementary note 11, wherein the distribution control server presents the user with information on the service provider that accumulates at least one piece of data that is subject to the data distribution, before transmitting the accumulated data transmission request. system.
[Additional note 13]
a communication control unit that communicates with a service server operated by a service provider and that accumulates multiple pieces of data generated by providing services to users;
When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. a data distribution control unit that presents at least one piece of data to the user;
Distribution control server equipped with.
[Additional note 14]
In the distribution control server,
Communicate with a service server operated by a service provider and accumulate multiple data generated by providing services to users,
When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. A method for controlling a distribution control server, the method comprising presenting at least one piece of data to the user.
[Additional note 15]
On the computer installed in the distribution control server,
A process of communicating with a service server operated by a service provider and accumulating multiple pieces of data generated by providing services to users;
When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. a process of presenting at least one piece of data to the user;
A computer-readable storage medium that stores a program for executing.

Furthermore, each disclosure of the cited prior art documents mentioned above shall be incorporated into this document by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are illustrative only and that various modifications can be made without departing from the scope and spirit of the invention. That is, it goes without saying that the present invention includes the entire disclosure including the claims and various modifications and modifications that can be made by those skilled in the art in accordance with the technical idea.

10 Distribution control server 20 Service server 20-1 Service server 20-2 Service server 20-3 Service server 30 Data utilization server 40 Transaction server 50 Terminal 60 Hospital terminal 101 Service server 102 Distribution control server 201 Communication control unit 202 User registration Section 203 ID cooperation section 204 Location information management section 205 Accumulated data acquisition section 206 Data distribution control section 207 Catalog information management section 208 Storage section 301 Communication control section 302 ID cooperation control section 303 Data distribution request section 304 Data accumulation control section 305 Transmission request Processing unit 306 Data distribution unit 307 Storage unit 311 Processor 312 Memory 313 Input/output interface 314 Communication interface 401 Communication control unit 402 Account opening unit 403 Catalog information request unit 404 Provision request processing unit 405 Storage unit 501 Communication control unit 502 Personal information input unit 503 Inquiry processing section 504 Account information input section 505 Storage section

Claims (15)

1. A service server operated by a service provider and which accumulates multiple pieces of data generated by providing services to users;
   A distribution control server that controls data distribution;
   including;
   The distribution control server, when distributing at least one data subject to the data distribution from the plurality of accumulated data from the service server to a server of a business other than the service business, A system that presents to the user at least one piece of data to be distributed.
2. The distribution control server transmits an accumulated data transmission request to the service server, including a data requirement that defines at least one piece of data to be distributed among the plurality of accumulated data,
   In response to receiving the stored data transmission request, the service server identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server. The system of claim 1, wherein the system transmits.
3. 3. The system according to claim 2, wherein the data requirements include at least one data type of data targeted for the data distribution.
4. 4. The system according to claim 3, wherein the data requirements include a data search period that specifies a period for searching for at least one piece of data to be distributed among the plurality of stored data.
5. The distribution control server is
   transmitting at least one piece of data subject to the data distribution acquired in response to transmitting the stored data transmission request to the service server to a terminal owned by the user;
   5. The method according to any one of claims 2 to 4, wherein information is obtained from the terminal as to whether or not the user has consented to at least one piece of data to be subjected to the data distribution. system.
6. If the user agrees to make at least one or more data subject to the data distribution subject to the data distribution, the distribution control server sends at least one data subject to the data distribution to the service server. The system according to claim 5, wherein the system instructs to send the data to a server of a different service provider than the service provider.
7. The system according to any one of claims 1 to 6, wherein the distribution control server controls data sharing for a first service provider to acquire data accumulated in a second service provider.
8. The system according to claim 7, wherein the distribution control server controls data provision for a data utilization business to acquire data accumulated by the second service business.
9. The distribution control server transmits the accumulated data transmission request including the data requirements defining data that the user desires to view to the service server, and presents the data obtained from the service server to the user. 5. The system according to any one of claims 2 to 4.
10. The distribution control server presents the user with at least one or more data to be distributed when the user desires to view at least one or more data to be distributed to the data. The system according to claim 1.
11. When the user desires to view at least one piece of data to be distributed, the distribution control server may browse at least one piece of data to be distributed among the plurality of stored data. Sending a stored data transmission request to the service server, including data requirements that define data;
    In response to receiving the stored data transmission request, the service server identifies data that matches the data requirements from among the plurality of stored data, and transmits the identified data to the distribution control server. send,
    The system according to claim 10, wherein the distribution control server presents the transmitted data to the user who desires to view the data.
12. 12. The distribution control server, before transmitting the stored data transmission request, presents the user with information about the service provider that stores at least one piece of data to be distributed. system.
13. a communication control unit that communicates with a service server operated by a service provider and that accumulates multiple pieces of data generated by providing services to users;
    When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. a data distribution control unit that presents at least one piece of data to the user;
    Distribution control server equipped with.
14. In the distribution control server,
    Communicate with a service server operated by a service provider and accumulate multiple data generated by providing services to users,
    When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. A method for controlling a distribution control server, the method comprising presenting at least one piece of data to the user.
15. On the computer installed in the distribution control server,
    A process of communicating with a service server operated by a service provider and accumulating multiple pieces of data generated by providing services to users;
    When at least one or more data to be data distributed from among the plurality of accumulated data is distributed from the service server to a server of a different service provider than the service provider, the data becomes the target of the data distribution. a process of presenting at least one piece of data to the user;
    A computer-readable storage medium that stores a program for executing.

Images