System

Abstract

The present invention enables an information distribution system to be sustained. The system comprises a distribution control server and a management server. The distribution control server controls data accumulation for making, as data to be distributed, data pertaining to a service provided by a data accumulator to a user. The distribution control server controls data sharing for a data provision destination to acquire the accumulated data. The distribution control server controls data provision for the data provision destination to acquire the accumulated data. A management server charges a data accumulator an accumulation platform use fee pertaining to the data accumulation. The management server charges a data sharing destination a sharing platform use fee pertaining to data sharing. The management server charges the data provision destination a provision platform use fee pertaining to the data provision.

Description

Technical Field

[0001] The present invention relates to a system, a management server, a control method for the management server, and a storage medium.

Background Art

[0002] There is an information distribution system that provides personal information held in a hospital or the like to an information receiving device of a service provider or the like based on the consent of the individual.

[0003] For example, Patent Document 1 discloses an information trading device connected to an information holding device that stores personal information. The information trading device includes a sharing approval receiving unit, a providing approval receiving unit, a sharing instruction unit, and a providing instruction unit. The sharing approval receiving unit receives approval of sharing of personal information from a user associated with the personal information by an information sharing destination device. The providing approval receiving unit receives approval of providing, which is transmission of personal information to an information receiving destination device, from a user associated with the personal information. The sharing instruction unit instructs sharing to the information sharing destination device when the sharing approval receiving unit receives approval of sharing. The providing instruction unit instructs providing to the information holding device when the providing approval receiving unit receives approval of providing.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] As disclosed in Patent Document 1, actors in the information distribution system include an information holder that stores personal information (personal data), an information receiving destination that acquires personal information by sharing, and an information receiving destination that acquires personal information by providing. Furthermore, there is also an information distribution business operator that provides the platform of the information distribution system.

[0006] Here, the operation of the information circulation system requires costs, and each actor needs to bear the operation costs. However, if the burden of the costs is biased towards any actor, there is a possibility that the information circulation system will not be continuously operated.

[0007] Note that this problem cannot be solved even by applying the technology disclosed in Patent Document 1. In Patent Document 1, the operation costs of the information circulation system are not considered.

[0008] The main object of the present invention is to provide a system, a management server, a control method of the management server, and a storage medium that contribute to making the information circulation system sustainable.

Means for Solving the Problems

[0009] According to a first aspect of the present invention, there is provided a system including: a circulation control server that controls data storage for making data related to services provided from a data accumulator to a user the target of data circulation, controls data sharing for a data sharing destination to acquire the stored data, and controls data provision for a data provision source to acquire the stored data; and a management server that bills the data accumulator for storage platform usage fees related to the data storage, bills the data sharing destination for sharing platform usage fees related to the data sharing, and bills the data provision source for provision platform usage fees related to the data provision.

[0010] According to a second aspect of the present invention, a transaction history control unit is provided that acquires a data storage history related to data storage for making data related to services provided from a data accumulator to a user the subject of data circulation, acquires a data sharing history related to data sharing for a data sharing destination to acquire the stored data, and acquires a data provision history related to data provision for a data provision source to acquire the stored data; and a transaction settlement control unit that calculates a storage platform usage fee related to the data storage based on the data storage history and bills the calculated storage platform usage fee to the data accumulator, calculates a sharing platform usage fee related to the data sharing based on the data sharing history and bills the calculated sharing platform usage fee to the data sharing destination, and calculates a provision platform usage fee related to the data provision based on the data provision history and bills the calculated provision platform usage fee to the data provision source. A management server is provided that includes these units.

[0011] According to a third aspect of the present invention, a control method for a management server is provided, which acquires a data storage history related to data storage for making data related to services provided from a data accumulator to a user the subject of data circulation, acquires a data sharing history related to data sharing for a data sharing destination to acquire the stored data, and acquires a data provision history related to data provision for a data provision source to acquire the stored data in the management server, calculates a storage platform usage fee related to the data storage based on the data storage history and bills the calculated storage platform usage fee to the data accumulator, calculates a sharing platform usage fee related to the data sharing based on the data sharing history and bills the calculated sharing platform usage fee to the data sharing destination, and calculates a provision platform usage fee related to the data provision based on the data provision history and bills the calculated provision platform usage fee to the data provision source.

[0012] According to a fourth aspect of the present invention, a computer mounted on a management server acquires a data storage history regarding data storage for making data related to a service provided from a data accumulator to a user be an object of data circulation, acquires a data sharing history regarding data sharing for a data sharing destination to acquire the stored data, and acquires a data provision history regarding data provision for a data provision destination to acquire the stored data, and a process of calculating an accumulation platform usage fee regarding the data storage based on the data storage history and billing the calculated accumulation platform usage fee to the data accumulator, calculating a sharing platform usage fee regarding the data sharing based on the data sharing history and billing the calculated sharing platform usage fee to the data sharing destination, and calculating a provision platform usage fee regarding the data provision based on the data provision history and billing the calculated provision platform usage fee to the data provision destination, and a computer-readable storage medium storing a program for causing the above to be executed is provided.

Effect of the Invention

[0013] According to each aspect of the present invention, a system, a management server, a control method of the management server, and a storage medium that contribute to making an information circulation system sustainable are provided. Note that the effects of the present invention are not limited to the above. Instead of or together with the above effects, other effects may be achieved by the present invention.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

MODE FOR CARRYING OUT THE INVENTION

[0015] First, an overview of an embodiment will be described. Note that the reference numerals in the drawings appended to this overview are for convenience attached to each element as an example to assist understanding, and the description of this overview is not intended to be limiting in any way. Also, unless otherwise specified, the blocks described in each drawing represent a configuration of functional units rather than a configuration of hardware units. The connection lines between blocks in each figure include both bidirectional and unidirectional ones. For a unidirectional arrow, it schematically shows the flow of the main signal (data) and does not exclude bidirectionality. In this specification and the drawings, for elements that can be similarly described, duplicate description may be omitted by assigning the same reference numerals.

[0016] The system according to an embodiment includes a distribution control server 101 and a management server 102 (see FIG. 1). The distribution control server 101 controls data accumulation for making data related to services provided from data accumulators to users the target of data distribution. The distribution control server 101 controls data sharing for acquiring data accumulated by data sharing destinations. The distribution control server 101 controls data provision for acquiring data accumulated by data provision sources. The management server 102 bills the data accumulator for the usage fee of the accumulation platform (PF; Platform) related to data accumulation (step S1 in FIG. 2). The management server 102 bills the data sharing destination for the usage fee of the sharing platform related to data sharing (step S2). The management server 102 bills the data provision source for the usage fee of the provision platform related to data provision (step S3).

[0017] The management server 102 determines the platform usage fee so that the operating costs necessary for the operation of the information circulation system are shared among the three parties: the data accumulator, the data sharing destination, and the data providing destination, and bills these three parties for the payment of the usage fee. By dividing the operating costs into three usage fees, the management server 102 can give preferential treatment to a specific entity or burden a specific entity with more costs. For example, in the information circulation system, data sharing and data provision do not occur if there is no accumulated data. Therefore, the management server 102 determines the accumulation platform usage fee so as to give preferential treatment to the data accumulator. The data accumulator with the preferential usage fee will accumulate more data and be able to supply more data to the data sharing destination and the data providing destination. The data sharing destination and the data providing destination increase their profits by providing better services to users using the data obtained through data circulation. Therefore, each actor can increase its profit, and concerns such as each actor forming the information circulation system withdrawing from the system are eliminated. As a result, the information circulation system is continuously operated (the information circulation system becomes sustainable).

[0018] The following describes specific embodiments in more detail with reference to the drawings.

[0019] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.

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

[0021] An information circulation operator is an operator that provides a platform for data circulation services (information circulation services) for personal data accumulated by service providers. The information circulation operator controls data circulation among operators (service providers, data utilization operators). The information circulation operator includes a circulation control server 10 and a management server 11.

[0022] The circulation control server 10 is a server device that controls (realizes) data circulation among service providers or controls data circulation between a service provider and a data utilization operator. The circulation control server 10 realizes information circulation services for data held by service providers.

[0023] The management server 11 is a server device responsible for management related to the operation of the information circulation system. The management server 11 mainly conducts management in terms of finance such as the costs required for the operation of the information circulation system, the fees collected from service providers participating in the information circulation system, and the rewards for data circulation.

[0024] A service provider is a entity that provides services to individuals. The service provider may be a private operator or a public institution. Examples of service providers include medical institutions (hospitals, pharmacies, etc.) that provide medical services to users, retailers, and educational institutions that teach languages, sports, arts, etc. to customers.

[0025] Each service provider includes a service server 20 for providing services to customers. The service server 20 is managed and operated by the service provider. The service server 20 holds (stores) data generated by the service provider providing services to users, data necessary for providing services to users, etc. The service provider holds user data related to the services provided to users.

[0026] Data utilization operators are entities that do not directly provide services to individuals. Examples of data utilization operators include entities such as pharmaceutical companies. For example, a pharmaceutical company develops new drugs using data obtained from service providers.

[0027] In the present disclosure, entities that do not provide services to individuals are treated as "data utilization operators" and described. However, when a data utilization operator provides services to users, it naturally acts as a "service provider". That is, depending on the business form of the data utilization operator, the data utilization operator can also become a service provider.

[0028] Data utilization operators are equipped with a data utilization server 30 for acquiring and utilizing data from service providers.

[0029] Transaction operators are entities that realize transactions between service providers and data utilization operators. Transaction operators realize the data flow between data generators (service providers) and data consumers (data utilization operators).

[0030] Transaction operators are equipped with a transaction server 40 for realizing the data flow.

[0031] Users who use the information circulation system use a terminal 50.

[0032] Each device shown in FIG. 3 is connected to each other via a network. For example, the circulation 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.

[0033] The configuration shown in FIG. 3 is an example and is not intended to limit the configuration of the information circulation system of the present disclosure. For example, the information circulation operator may include two or more circulation control servers 10. Also, regarding transaction operators and data utilization operators, data utilization servers 30 and transaction servers 40 corresponding to the number of operators participating in the system are included in the information circulation system.

[0034] [Overview of System Operation] Next, the overview of the operation of the information circulation system according to the first embodiment will be described.

[0035] The user concludes an individual contract with the service provider for which the user desires to receive services. For example, while providing the service provider with personal information such as name, the user requests to conclude a new contract (a contract for enjoying the service) with the service provider.

[0036] For example, a user who wishes to visit a hospital submits a health insurance card or the like with their name and other information to the hospital. Alternatively, for an EC (Electronic Commerce) service provider that provides services related to online shopping, the user accesses the service server 20 operated by the EC service provider to generate an account.

[0037] The service provider generates a "personal identification ID" for identifying a new customer (user). For example, the hospital assigns a medical record number for managing the user (patient) and generates the medical record number as the personal identification ID. The EC service provider generates a membership number or the like for managing customers as the personal identification ID. The service server 20 stores the generated personal identification ID (for example, a medical record number or a membership number) in a database or the like.

[0038] Once the personal identification ID is generated, the user can receive services from the service provider. For example, the user receives medical services (such as health check-ups and consultations) from the hospital. Alternatively, the user conducts online shopping using the EC service provider.

[0039] In order for user data generated by a service provider providing services to users, etc. to be the subject of data circulation, "accumulation" of data is necessary. Data accumulation means that the service provider (the provider of user data) registers the user data as data that can be provided to a third party in the information circulation system. The circulation control server 10 controls data accumulation for making data related to services provided from the data accumulator (service provider) to users be the subject of data circulation.

[0040] The accumulated data becomes the subject of data circulation. Also, for the accumulation of user data, the consent of the user (the user who was the source of the generation of user data) (consent to data accumulation) is required.

[0041] "Sharing" and "providing" exist as means of data circulation in the information circulation system.

[0042] "Sharing" is a means for a service provider to obtain data accumulated by another service provider. For example, when an e-commerce operator obtains data generated by a hospital providing services to users, data circulation by "sharing" is used. The e-commerce operator uses the data obtained from the hospital by data sharing to provide better services to users.

[0043] "Providing" is a means for a data utilization business operator to obtain data accumulated by another service provider. For example, when a pharmaceutical company obtains the results of a health check or a medical examination from a hospital, data circulation by "providing" is used. The pharmaceutical company uses the data obtained from the hospital by data provision for the development of new drugs.

[0044] The circulation control server 10 controls data sharing for a data sharing destination (a service provider that receives data supply) to obtain the accumulated data. The circulation control server 10 controls data provision for a data provision destination (a data utilization business operator that receives data supply) to obtain the accumulated data.

[0045] <Generation of System Account> Users of the information distribution system need to perform pre-registration (user registration, system registration). More specifically, the user accesses the distribution control server 10 and performs procedures for account generation. In the following description, the account generated in the information distribution system is referred to as a "system account".

[0046] To generate a system account, the user operates the possessed terminal 50 to access the distribution control server 10. In response to the access of the terminal 50, the distribution control server 10 displays a WEB (web) page for generating a system account.

[0047] The user performs an operation for generating a system account (for example, pressing a predetermined button) to generate a system account. At this time, the distribution control server 10 acquires information necessary for the user to generate a 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.).

[0048] After acquiring the 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.

[0049] The distribution control server 10 stores the generated user ID of the user, login information, and personal information (for example, name, date of birth, contact information) in association with each other. The distribution control server 10 stores these information in the "user information database". Details of the user information database will be described later.

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

[0051] <Linkage of IDs> As described above, in order to make the user data held by service providers the subject of data circulation, "data accumulation" is necessary. To achieve data accumulation, it is necessary to link the ID of the system account (user ID) and the ID (personal identification ID) generated by the service provider.

[0052] For example, as shown in FIG. 4, the user conveys to the hospital staff at the hospital reception desk that they wish to utilize the user data held by the hospital (submit an application for data utilization). The hospital staff inputs the user's personal identification information, the user's personal identification ID (for example, the medical record number), and the business operator code into the hospital terminal 60.

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

[0054] In addition, the business operator code is identification information (ID) for identifying service providers participating in the information circulation system. For example, different codes are assigned to hospitals and EC operators. The business operator code is shared among system participants (information circulation operators, service providers, data utilization operators) by any means. For example, when a service provider participates in the information circulation system, the information circulation operator generates a business operator code assigned to the service provider. The information circulation operator notifies the generated business operator code to the service provider, etc.

[0055] The hospital terminal 60 transmits an "ID linking request" including the acquired personal identification information, personal identification ID, and business operator code to the circulation control server 10.

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

[0057] The distribution control server 10 acquires the personal identification information of the ID linkage applicant, the personal identification ID, and the operator code of the service operator (e.g., hospital, EC operator) that is the target of ID linkage from the hospital terminal 60 or the service server 20.

[0058] The distribution control server 10 identifies the service operator that is the target of ID linkage from the operator code. In addition, the distribution control server 10 identifies the user registered in the system account from the personal identification information, and associates the service operator with the personal identification ID in the account of the identified user.

[0059] When the personal identification ID is registered in the system account (when ID linkage is completed), the service operator that is the target of ID linkage can "accumulate" the user data of the user who wishes to utilize the data.

[0060] Note that the "application for data utilization" by the user to the service operator can be regarded as a commitment (agreement) for the service operator to accumulate user data. In addition, the service operator (service server 20) acquires the account information (e.g., bank account, credit card information) of the ID linkage applicant and stores it in association with the personal identification ID and the like.

[0061] <Data Accumulation> When the service operator provides a service to the user, the service operator stores the personal identification ID of the user in association with the user data (personal data).

[0062] For users whose ID linking has been completed (users who have applied for data utilization), whenever the service provider stores user data (data generated as a result of service provision, data necessary for service provision), the "location information" is sent to the circulation control server 10.

[0063] For example, as shown in Fig. 6, when a hospital provides medical services to each of users U1 - U3, the hospital retains the results for each user. For example, the hospital retains the examination results (disease names; data such as gastric cancer, lung cancer, etc.) for each of users U1 - U3.

[0064] The service provider (service server 20) stores the personal identification ID of each user in association with the user data obtained as a result of service provision. For example, in the example of Fig. 6, the service server 20 uses the "customer information database" to store the personal identification IDs of users U1 - U3 in association with their examination results. The details of the customer information database will be described later.

[0065] Whenever the service provider stores user data regarding users who have consented to data accumulation, the "location information" is sent to the circulation control server 10. The location information is information regarding the storage location of the user data (the entity accumulating the data; the service provider), etc. The location information includes the personal identification ID, the operator code, the type of data to be retained, etc.

[0066] The circulation control server 10 stores the acquired location information in the "location information database". The details of the location information database will be described later. The said location information database stores the personal identification ID, the operator code, and the data type, etc. in association with each other.

[0067] <Data sharing> A service provider wishing to obtain data accumulated by another service provider (user data generated as a result of another service provider providing services to users) obtains the said data through "sharing".

[0068] Here, with reference to FIG. 7, the case where EC business operator B obtains the data (examination results) of users stored in hospital A through "sharing" will be described. The hospital is equipped with service server 20-1, and the EC business operator is equipped with service server 20-2.

[0069] EC business operator B (service server 20-2) sends a "sharing request" to distribution control server 10 (step S11).

[0070] Based on the sharing request, distribution control server 10 identifies the data accumulator (hospital A) of the data to be distributed to user U1, who is the target of data distribution. Distribution control server 10 sends an inquiry regarding data sharing to the terminal 50 owned by the identified target (step S12).

[0071] Upon receiving the inquiry regarding data sharing, terminal 50 obtains the intention of user U1 regarding data sharing. For example, terminal 50 obtains the intention of user U1 using a GUI (Graphical User Interface). In the above example, terminal 50 displays a GUI with content such as "By sharing the hospital's examination results with the EC business operator, you can receive better services. Do you want to share?" and obtains the intention of user U1 (agreement or disagreement to data sharing).

[0072] Terminal 50 sends a response to the inquiry regarding data sharing (agreement to data sharing or rejection of data sharing) to distribution control server 10 (step S13).

[0073] If the consent of user U1 is obtained, distribution control server 10 sends a sharing instruction to the data accumulator (hospital A) (step S14).

[0074] Upon receiving the sharing instruction, hospital A (service server 20-1) refers to the customer information database and sends the examination results of the target user U1 to service server 20-2, which is the designated data sharing destination (step S15).

[0075] Next, the data circulation by "provision" will be explained.

[0076] <Account opening> Users who want to obtain consideration through data provision need to open an account with a trading business operator. With reference to Fig. 8, the account opening for provision will be explained.

[0077] The trading business operator forms an alliance with at least one of the multiple service providers participating in the information circulation system. For example, a trading business operator handling medical data forms an alliance with medical institutions (hospitals, pharmacies, etc.). Alternatively, a trading business operator handling educational data forms an alliance with educational institutions. The trading business operator stores the business code of the partner service provider.

[0078] In addition, the trading business operator stores the business code of the data utilization business operator. For example, when starting a transaction with a data utilization business operator, the trading business operator generates the business code of the data utilization business operator. The business code of the data utilization business operator is shared among the information circulation business operator, the trading business operator, and the data utilization business operator by any method.

[0079] The trading business operator sells the data (accumulated data) held by the partner service provider to the data utilization business operator. For example, if the partner service provider shown in Fig. 8 is a medical institution, the trading business operator sells the data held by the partner medical institution to a pharmaceutical company or the like. All or part of the consideration obtained from the data sale is paid to the users involved in the provided data.

[0080] As described above, users who want to obtain consideration through data provision via a trading business operator need to open an account with the trading business operator (trading server 40). Among the users participating in the information circulation system, users who want to obtain profits through data provision open an "information account" with the trading server 40.

[0081] The user presents the user ID issued by the distribution control server 10 to the transaction server 40 and opens an information account. The transaction server 40 stores the acquired user ID. The transaction server 40 manages the user IDs of the users who have opened accounts in the account opening list.

[0082] <Catalog Information> In order to realize data distribution by "provision", the information distribution operator prepares catalog information. The person in charge (system administrator) of the information distribution operator defines the catalog information describing the sellable data (see Fig. 9). The catalog information is information indicating the details of the data that the information distribution system can sell to data utilization operators.

[0083] The dataset name included in the catalog information shown in Fig. 9 is information for identifying the catalog information. For example, the dataset name "Examination Result 1" is assigned to the dataset related to the medical examination, and the dataset name "Examination Result 1" is assigned to the dataset related to the examination result.

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

[0085] The data utilization operator acquires the catalog information through the trading operator. More specifically, the data utilization server 30 sends a "Catalog Information Presentation Request" to the transaction server 40.

[0086] Upon receiving the catalog information presentation request, the transaction server 40 sends a "Catalog Information Transmission Request" to the distribution control server 10.

[0087] In response to receiving a catalog information transmission request, the distribution control server 10 transmits catalog information defined by the information distribution operator to the transaction server 40.

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

[0089] <Data distribution by provision> A data utilization operator that wishes to obtain data accumulated by a service provider obtains the data by "provision".

[0090] Here, with reference to FIG. 10, a case where pharmaceutical company C obtains the accumulated data (examination results) of hospital A by "provision" will be described.

[0091] First, a person in charge of a pharmaceutical company, etc. refers to the catalog information presented by the trading operator and identifies the necessary catalog information. Thereafter, the data utilization server 30 transmits a provision request including information on the data utilization operator, the dataset name of the identified catalog information, and the conditions required for the provided data to the transaction server 40 according to the instructions of the person in charge (step S21). In the following description, the conditions required for the provided data are referred to as "search conditions".

[0092] The information on the data utilization operator includes the name of the data utilization operator, the operator code, the data destination (data transmission destination address), etc. The search conditions include, for example, "100 or more pieces of data on disease names".

[0093] The transaction server 40 examines the obtained provision request. If no problems are found through the examination, the transaction server 40 transmits the obtained provision request and the account opener list to the distribution control server 10 (step S22).

[0094] The distribution control server 10 identifies the personal identification ID of the user described in the account opening applicant list and related to the requested catalog information. The distribution control server 10 sends an inquiry regarding data provision to the contact information (email address that the terminal 50 can receive) of the user corresponding to the identified personal identification ID (step S23).

[0095] The inquiry regarding data provision includes information on the requester of data provision (pharmaceutical company C in the example of FIG. 10), information on the data accumulator (hospital A in the example of FIG. 10), and the type of data for which provision is desired (for example, disease name).

[0096] The terminal 50 that has received the inquiry regarding data provision displays a GUI for obtaining the intention of each user regarding data provision. The terminal 50 uses the GUI to obtain the intention of the user (agreement or disagreement to data provision).

[0097] The terminal 50 sends a response to the inquiry regarding data provision (agreement to data provision or rejection of data provision) to the distribution control server 10 (step S24).

[0098] The distribution control server 10 sends a provision instruction to the data accumulator (hospital A) for the users who have given consent (step S25). For example, as described above, when provision of 100 or more disease name data is requested, the distribution control server 10 sends a provision instruction to the service server 20-1 regarding the disease name data of 100 or more users who have agreed to data provision.

[0099] The hospital A (service server 20-1) that has received the provision instruction refers to the customer information database and sends the user data of the users who have given consent to the designated data provision destination (step S26). In the above example, if each of the users U1 to U3 has agreed to data provision, the disease name data of the users including the users U1 to U3 is sent to the data utilization server 30.

[0100] <Occurrence of Consideration> Here, the consideration associated with the operation (use) of the information circulation system will be described.

[0101] "Accumulation" targets the user data held by the service provider for information circulation (data circulation), and a consideration is paid to the users who have consented to such accumulation. Also, a consideration is paid to the service provider that holds the accumulated data (user data of users who have consented to data utilization).

[0102] "Sharing" is used to improve the convenience of the service users themselves, so no consideration (consideration for users) for data circulation is paid to the users. "Sharing" is used because the users utilize the data accumulated by other service providers in order to receive better services from the service provider. However, when "sharing" is carried out, a consideration is paid from the data acquirer (data sharing recipient) to the data sharer (data accumulator).

[0103] "Provision" is a means used by data utilization business operators who do not directly provide services to users, so a consideration (consideration for users) for data circulation occurs. That is, when "provision" is carried out, a consideration is paid to the users. Also, similar to sharing, when "provision" is carried out, a consideration is paid from the data acquirer (data provision recipient) to the data provider (data accumulator).

[0104] In addition, in this application disclosure, for the sake of convenience, it is explained that no consideration (commission) occurs for the trading business operator. In reality, a part of the consideration paid from the data provider to the data provider and the users is paid to the trading business operator as "commission".

[0105] <Finances of the Information Circulation Service> FIG. 11 is a diagram showing the situation regarding the finances of the information circulation system. FIG. 11 is a diagram showing the flow of money (usage fees, consideration) centered around the service provider that holds the accumulated data (user data of users who have consented to data utilization).

[0106] The service provider 70-1 that retains the accumulated data obtains service fees from the users. Also, the service provider 70-1 distributes the consideration for "accumulation" to the users who have consented to data accumulation, and distributes the consideration for "provision" to the users who have consented to data provision.

[0107] The service provider 70-1 pays platform (PF) usage fees to the information distribution provider 71. Also, the service provider 70-1 obtains the consideration for "accumulation" from the information distribution provider.

[0108] When the service provider 70-1 supplies the accumulated data to other service providers through data sharing, the service provider 70-1 obtains the consideration for "sharing" from the data sharing destination service provider 70-2.

[0109] Similarly, when the service provider 70-1 supplies the accumulated data to the data utilization business operator through data provision, the service provider 70-1 obtains the consideration for "provision" from the data utilization business operator 72 that is the data provision destination.

[0110] When the service provider 70-1 obtains the accumulated data from other service providers through data sharing, the service provider 70-1 pays the consideration for "sharing" to the data sharing source service provider 70-3.

[0111] Similarly, when the service provider 70-1, as a data utilization business operator, obtains the accumulated data from other service providers through data provision, the service provider 70-1 pays the consideration for "provision" to the data provision source service provider 70-4.

[0112] <Transmission of Transaction History> When the service provider performs data accumulation (when transmitting location information), the service provider stores the history related to the data accumulation (data accumulation history). Also, when the service provider performs data distribution (data sharing, data provision), the service provider stores the history related to the data distribution (data sharing history, data provision history).

[0113] The service server 20 transmits the above history (data accumulation history, data sharing history, data provision history) to the information distribution operator (management server 11) at regular intervals or at a predetermined timing. For example, the service server 20 transmits the above transaction history to the management server 11 at every predetermined period (see FIG. 12). For example, the service server 20 transmits the transaction history to the management server 11 at the end of the month.

[0114] In this way, the service provider (service server 20) reports the transaction history in the data transaction to the information distribution operator. Specifically, the service server 20 reports the details of the transaction to the information distribution operator for each of accumulation, sharing, and provision.

[0115] <Payment of consideration> As shown in FIG. 13, the management server 11 pays the consideration for accumulation to each service provider at a predetermined timing (for example, the beginning of the month). More specifically, after the management server 11 transmits the accumulation consideration payment statement to the service server 20, it pays the consideration for accumulation to the service provider.

[0116] In addition, the management server 11 calculates the consideration for sharing and provision that each service provider (data utilization service provider) pays to other service providers, and instructs the service provider to pay the consideration (issues a payment instruction for data distribution). In the following description, the payment instruction for data sharing is referred to as a "sharing consideration payment instruction", and the payment instruction for data provision is referred to as a "provision consideration payment instruction". The calculation method for the consideration for each transaction will be described later.

[0117] <Operating cost of information distribution system> The operation of the information distribution system incurs costs. The information distribution system collects platform usage fees (PF usage fees) from each of the data accumulator (data holding actor) that holds the accumulated data, the data sharing destination (sharing destination actor), and the data provision destination (provision destination actor).

[0118] Hereinafter, the usage fee paid by the data accumulator will be denoted as the "accumulation PF usage fee", the usage fee paid by the data sharing destination will be denoted as the "sharing PF usage fee", and the usage fee paid by the data providing destination will be denoted as the "providing PF usage fee". The information circulation operator will cover the system operation costs with these usage fees (accumulation PF usage fee, sharing PF usage fee, providing PF usage fee). As described above, the information circulation operator pays the consideration for accumulation to the data accumulator.

[0119] In this way, the information circulation operator (management server 11) bills the data accumulator for the accumulation platform usage fee related to data accumulation. The management server 11 bills the data sharing destination for the sharing platform usage fee related to data sharing. The management server 11 bills the data providing destination for the providing platform usage fee related to data providing.

[0120] Here, the information circulation operator (management server 11) holds information on the ratio borne by each actor for the operation costs. For example, the management server 11 holds a ratio such as "accumulation burden ratio: sharing burden ratio: providing burden ratio = 0.2:0.4:0.4". Alternatively, the management server 11 holds a ratio such as "accumulation burden ratio: sharing burden ratio: providing burden ratio = 0.1:0.2:0.7".

[0121] Note that the accumulation burden ratio is the ratio at which each data accumulator participating in the information circulation system bears the operation costs. The sharing burden ratio is the ratio at which each data sharing destination participating in the information circulation system bears the operation costs. The providing burden ratio is the ratio at which each data providing destination participating in the information circulation system bears the operation costs.

[0122] The example of "accumulation burden ratio: sharing burden ratio: providing burden ratio = 0.2:0.4:0.4" above indicates that the data accumulator bears 20% of the operation costs, and each of the data sharing destination and the data providing destination bears 40% of the operation costs.

[0123] The management server 11 calculates the PF usage fees to be billed to service providers (each actor) using the ratio of each burden to the above operating costs. The management server 11 calculates the storage PF usage fees based on the number of times the data accumulator has performed data accumulation and the storage burden ratio that determines the burden ratio of data accumulation. The management server 11 calculates the sharing PF usage fees based on the number of times the data sharing destination has performed data sharing and the sharing burden ratio that determines the burden ratio of data sharing. The management server 11 calculates the sharing PF usage fees based on the number of times the data provider has provided data and the provision burden ratio that determines the burden ratio of data provision. Note that a more specific calculation method of the PF usage fees will be described later.

[0124] The management server 11 bills each service provider for the calculated PF usage fees (issues a bill regarding the PF usage fees). In the following description, the bill regarding the PF usage fees is referred to as the "PF usage fee bill". Also, the calculation method of the PF usage fees will be described later.

[0125] <Calculation of the burden ratio> The management server 11 calculates the burden ratios (storage burden ratio, sharing burden ratio, provision burden ratio) based on the income and expenditure of each service provider. The calculation of the burden ratio is performed every predetermined period. For example, the management server 11 recalculates the burden ratio applied to the calculation of the PF usage fees every six months (every half-year, every first half-year and second half-year).

[0126] At that time, the management server 11 calculates the burden ratio so that the profit of the entire information circulation system is improved. For example, since the source of profit in the information circulation system lies in the stored data, the management server 11 may calculate the burden ratio so as to give preferential treatment to the data accumulator (for example, lower the storage burden ratio).

[0127] In this way, the management server 11 determines the storage burden ratio, the sharing burden ratio, and the provision burden ratio based on the income and expenditure of the data accumulator, the data sharing destination, and the data provider respectively. At that time, the management server 11 may determine the storage burden ratio, the sharing burden ratio, and the provision burden ratio so as to give preferential treatment to the data accumulator.

[0128] <Disclosure of Burden Ratio> The information distribution operator (management server 11) discloses the calculated burden ratio. Each service operator (each actor) uses the disclosed burden ratio to consider the cost burden and consider strategies for the next period (next term).

[0129] In this way, the management server 11 periodically recalculates the accumulated burden ratio, shared burden ratio, and provided burden ratio. The management server 11 discloses the recalculated accumulated burden ratio, shared burden ratio, and provided burden ratio to the data accumulator, data sharing destination, and data providing destination.

[0130] Subsequently, details of each device included in the information distribution system according to the first embodiment will be described.

[0131] [Circulation Control Server] FIG. 14 is a diagram showing an example of the processing configuration (processing module) of the circulation control server 10 according to the first embodiment. Referring to FIG. 14, the circulation control server 10 includes a communication control unit 201, a user registration unit 202, an ID cooperation unit 203, a location information management unit 204, a data circulation control unit 205, a catalog information management unit 206, and a storage unit 207.

[0132] 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. Also, the communication control unit 201 transmits data to the service server 20. The communication control unit 201 delivers the data received from other devices to other processing modules. The communication control unit 201 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 201. The communication control unit 201 has a function as a receiving unit for receiving data from other devices and a function as a transmitting unit for transmitting data to other devices.

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

[0134] When the user registration unit 202 acquires the personal information, it generates a user ID for identifying the user. For example, each time the user registration unit 202 registers a user in the system, it assigns a unique value, and uses the assigned value as the user ID.

[0135] The user registration unit 202 stores the user ID and the personal information in the user information database (see FIG. 15). As shown in FIG. 15, the user information database stores the user ID, the personal information, and the personal identification ID for each service provider in association with each other. Also, 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 when the user was registered may be registered in the user information database.

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

[0137] The ID linking unit 203 is a means for realizing the above-mentioned ID linking. The ID linking unit 203 receives an "ID linking request" from the terminal of the service provider (for example, the hospital terminal 60) or the service server 20. The ID linking request includes the personal identification information, the personal identification ID, and the business operator code of the user who wishes to perform ID linking (registration of the service provider).

[0138] The ID linking unit 203 searches the user information database using the personal identification information (such as the user's name, the combination of the name and the date of birth, etc.) as a key, and identifies the corresponding user. The ID linking unit 203 sets the personal identification ID included in the ID linking request in the field corresponding to the business operator code among the personal identification ID fields of the identified user. That is, the ID linking 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.

[0139] The location information management unit 204 is a means for managing location information obtained from service providers. The location information management unit 204 stores the location information obtained from each service server 20 in a location information database (see FIG. 16). As shown in FIG. 16, the location information database stores by associating a personal identification ID, a business operator code, and a data type.

[0140] Note that the location information database shown in FIG. 16 is an example and is not intended to limit the items to be stored. For example, the date and time when the location information was registered may be registered in the location information database. Also, in the drawings including FIG. 16, for ease of understanding, the business operator code is represented using the name of the service provider.

[0141] The data flow control unit 205 is a means for controlling data flow by "sharing" or "providing".

[0142] First, the data flow regarding "sharing" will be described.

[0143] The data flow control unit 205 receives a sharing request from the service server 20. The sharing request includes the personal identification ID of the user who is the target of data acquisition, the business operator code of the transmission source of the sharing request, and the data type for which acquisition is desired. In the example of FIG. 7, the personal identification ID generated by the EC business operator B (service server 20-2) for the user U1, the business operator code of the EC business operator B, and "disease name" as the data type are included in the sharing request.

[0144] The data flow control unit 205 identifies the target person of the data flow based on the personal identification ID and business operator code included in the sharing request. Specifically, the data flow control unit 205 refers to the user information database shown in FIG. 15 to identify the target person. In the above example, when receiving a sharing request including the personal identification ID of "EC01" from the EC business operator B, the data flow control unit 205 grasps from the first row entry shown in FIG. 15 that the user U1 is the target person of the data flow.

[0145] After that, the data circulation control unit 205 identifies the service provider that stores the necessary data using the personal identification ID of the specified user and the data types included in the sharing request. Specifically, the data circulation control unit 205 refers to the location information database shown in FIG. 16 and identifies the service provider that stores the data corresponding to the data types included in the sharing request. In the above example, based on the personal identification ID "HL01" of the user U1 and the data type "disease name" included in the sharing request, Hospital A is identified.

[0146] If the combination of the user's personal identification ID and the data types included in the sharing request is not stored in the location information database, the data circulation control unit 205 sends a negative response indicating that data sharing is not possible to the sender of the sharing request. In the above example, if the combination of the personal identification ID "HL01" of the user U1 and the data type "disease name" is not registered in the location information database, a negative response is sent to the EC operator B (service server 20-2).

[0147] When the data circulation target and the accumulator of the data to be circulated are identified, the data circulation control unit 205 makes an inquiry about data sharing to the data circulation target. Specifically, the data circulation control unit 205 sends an inquiry regarding data sharing to the contact information of the data circulation target. In the above example, the above inquiry is sent to the terminal 50 owned by the user U1.

[0148] The inquiry about data sharing includes information such as the requester of data sharing, the data accumulator, and the data types to be shared. In the above example, the EC operator B is set as the requester of data sharing, Hospital A is set as the data accumulator, and "disease name" is set as the data type to be shared.

[0149] The data circulation control unit 205 receives a response to the inquiry about data sharing from the terminal 50.

[0150] If the user rejects data sharing, the data circulation control unit 205 notifies the data sharing requester that data sharing is not possible. In the above example, the data circulation control unit 205 sends a negative response to the sharing request to the service server 20-2 of EC operator B.

[0151] If the user agrees to data sharing, the data circulation control unit 205 sends a sharing instruction to the data accumulator. In the above example, a sharing instruction is sent to the service server 20-1 of hospital A, which is the data accumulator.

[0152] The sharing instruction includes the personal identification ID generated by the data accumulator, information about the data sharing destination, and the data type of the data to be shared. In the above example, a sharing instruction including the personal identification ID "HL01" of user U1, the address of the service server 20-2 of EC operator B, and the data type "disease name" is sent to the service server 20-1 of hospital A.

[0153] In this way, the data circulation control unit 205 sends a sharing instruction including the personal identification ID generated by the data accumulator, which is the personal identification ID of the user (subject) who has agreed to data sharing.

[0154] Subsequently, the data circulation regarding "provision" will be described.

[0155] The data circulation control unit 205 receives a provision request and an account opener list from the transaction server 40.

[0156] The data circulation control unit 205 identifies the catalog information for which provision is desired from the dataset name included in the provision request.

[0157] The data circulation control unit 205 refers to the location information database and identifies the personal identification IDs corresponding to the data types and business operator codes included in the identified catalog information. In the example of FIG. 10, the personal identification IDs "HL01" to "HL03" corresponding to users U1 to U3 respectively are identified.

[0158] The data circulation control unit 205 identifies the users corresponding to the above-specified personal identification ID and who are listed in the account opening user list. The data circulation control unit 205 refers to the user information database and identifies the users corresponding to the above-specified personal identification ID and who are each listed in the account opening user list (at least one or more data circulation target persons).

[0159] When the data circulation target person is identified, the data circulation control unit 205 makes an inquiry about data provision to the data circulation target person. Specifically, the data circulation control unit 205 sends an inquiry regarding data provision to the contact information of the data circulation target person. In the above example, if each of the users U1 to U3 has opened an information account with the trading company, an inquiry about data provision is sent to the terminal 50 held by each user.

[0160] The inquiry about data provision includes information about the requester of data provision, information about the data accumulator, and the type of data for which provision is requested. In the above example, an inquiry including the pharmaceutical company C as the requester of data provision, the hospital A as the data accumulator, and the "disease name" as the type of data for which provision is requested is sent to each terminal 50.

[0161] The data circulation control unit 205 sends a provision instruction to the data accumulator regarding the users who have given consent. The provision instruction includes the personal identification ID of the user who has consented to data provision, information about the data provision destination (for example, the company name, company code, address of the data utilization server 30), and the type of data to be provided.

[0162] The catalog information management unit 206 is a means for managing catalog information. The catalog information management unit 206 stores the catalog information created by the system administrator in the storage unit 207.

[0163] The catalog information management unit 206 receives a "catalog information transmission request" from the transaction server 40. In response to the reception of the request, the catalog information management unit 206 sends the catalog information stored in the storage unit 207 to the transaction server 40.

[0164] The storage unit 207 stores information necessary for the operation of the distribution control server 10. A user information database is constructed in the storage unit 207. Further, a database or the like that stores the names of service providers and the provider codes in association with each other is constructed in the storage unit 207.

[0165] [Service Server] FIG. 17 is a diagram showing an example of the processing configuration (processing modules) of the service server 20 according to the first embodiment. Referring to FIG. 17, the service server 20 includes a communication control unit 301, an ID linking control unit 302, a data distribution request unit 303, a data storage control unit 304, a data distribution unit 305, a transaction history reporting unit 306, a transaction settlement unit 307, and a storage unit 308.

[0166] 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. Also, the communication control unit 301 transmits data to the distribution control server 10. The communication control unit 301 delivers the data received from other devices to other processing modules. The communication control unit 301 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0167] The ID linking control unit 302 is a means for controlling the ID linking of users. The ID linking control unit 302 acquires a request for ID linking from a user who has logged in to an account using a GUI (Graphical User Interface) or the like. The ID linking control unit 302 transmits an "ID linking request" including personal identification information (such as the name of the logged-in user), a personal identification ID (such as the member number of the user), and a provider code to the distribution control server 10 according to the request from the user.

[0168] Note that the user's personal identification ID, personal identifying 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 (a flag) indicating whether or not the ID linking of the user is completed. When the ID linking is completed, the ID linking control unit 302 sets a flag in the ID linking status field of the corresponding user (in Fig. 18, "○" is set).

[0169] The data circulation request unit 303 is a means for requesting an information circulation operator for data circulation (data sharing) regarding the user's data. The data circulation request unit 303 transmits a sharing request to the circulation control server 10 in response to an operation by a staff member of the service provider or the like. Specifically, the data circulation request unit 303 transmits a sharing request including the personal identification ID of the user to be the target of data acquisition, the operator code of its own device, and the type of data to be acquired to the circulation control server 10.

[0170] The data accumulation control unit 304 is a means for performing control regarding the accumulation of user data resulting from providing a service to the user. The data accumulation control unit 304 associates the personal identification ID of the user with the user data of the user (data generated as a result of providing a service to the user or data necessary for the service to be provided to the user) and stores it in the customer information database.

[0171] As shown in Fig. 18, the data accumulation control unit 304 stores the user data in a field corresponding to the type of data generated (stores the specific data content). Note that Fig. 18 shows an example of a customer information database constructed in the service server 20-1 of Hospital A.

[0172] Here, for users for whom ID linking is complete, every time the data storage control unit 304 stores user data in the customer information database, it transmits the location information to the distribution control server 10. For example, when a service is provided to a user with the personal identification ID "HL01" and data on the disease name is generated as a diagnosis result, location information including the personal identification ID "HL01", the business operator code "Hospital A", and the data type "disease name" is transmitted to the distribution control server 10.

[0173] The data storage control unit 304 stores the transmission history of the location information in the data storage history database (see FIG. 19). As shown in FIG. 19, the data storage history database stores by associating the transmission date of the location information, the personal identification ID notified by the location information, the data type, etc. Note that FIG. 19 shows an example of the data storage history database constructed in the service server 20-1 of Hospital A.

[0174] The data distribution unit 305 is a means for realizing data distribution by "sharing" or "providing". The data distribution unit 305 processes the "sharing instruction" or "providing instruction" received from the distribution control server 10.

[0175] When receiving a sharing instruction, the data distribution unit 305 refers to the customer information database and identifies the entry corresponding to the personal identification ID and data type included in the sharing instruction. For example, when receiving a sharing instruction including the personal identification ID "HL01" and the data type "disease name", the data distribution unit 305 identifies the entry shown in the uppermost row of FIG. 18.

[0176] The data distribution unit 305 transmits the user data described 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. 7, "stomach cancer" is transmitted to the service server 20-2 of EC operator B.

[0177] The data distribution unit 305 processes the provision instruction in the same way as the sharing instruction. The data distribution unit 305 transmits the user data determined by the personal identification ID and data type included in the provision instruction to the data provision destination specified by the provision instruction.

[0178] Each time the data distribution unit 305 processes a sharing instruction or a provision instruction, it stores the history of the data distribution transaction. Specifically, when processing a sharing instruction, the data distribution unit 305 stores the details of the data sharing in the data sharing history database shown in FIG. 20. FIG. 20 shows an example of the data sharing history database constructed in the service server 20-1 of Hospital A.

[0179] Also, when processing a provision instruction, the data distribution unit 305 stores the details of the data provision in the data provision history database shown in FIG. 21. FIG. 21 shows an example of the data provision history database constructed in the service server 20-1 of Hospital A.

[0180] The transaction history reporting unit 306 is a means for reporting the history of transactions (data accumulation history, data sharing history, data provision history). The transaction history reporting unit 306 transmits the history information for a predetermined period to the management server 11 at regular intervals or at a predetermined timing. For example, the transaction history reporting unit 306 transmits the history information for the current month (corresponding entries in the above three databases) to the management server 11 at the end of the month. At that time, the transaction history reporting unit 306 also notifies the management server 11 of its own business operator code.

[0181] Specifically, the transaction history reporting unit 306 refers to the transmission date and time field of each database to identify the entries to be transmitted (reported). The transaction history reporting unit 306 transmits the identified entries (at least one or more entries) and the business operator code to the management server 11.

[0182] The transaction settlement unit 307 is a means for settling transactions such as those related to data accumulation and data circulation. The transaction settlement unit 307 receives from the management server 11 a statement regarding data accumulation (accumulation consideration payment statement). Based on the transaction details included in the statement, the transaction settlement unit 307 calculates the consideration to be paid to each user (customer). The transaction settlement unit 307 calculates the consideration (total consideration) to be paid to each user by multiplying the consideration of the transaction details by the accumulation consideration distribution rate, and pays it to each user. Note that the accumulation consideration distribution rate will be described later.

[0183] The transaction settlement unit 307 receives from the management server 11 a payment instruction regarding data circulation (shared consideration payment instruction, provided consideration payment instruction). Regarding the shared consideration payment instruction, the transaction settlement unit 307 calculates the consideration to be paid to each data sharing destination based on the transaction details included in the instruction. The transaction settlement unit 307 sums up the consideration of the transaction details for each data sharing destination and calculates the consideration (total consideration) to be paid to each data sharing destination. The transaction settlement unit 307 pays the calculated consideration to each data sharing destination.

[0184] Regarding the provided consideration payment instruction, the transaction settlement unit 307 calculates the consideration to be paid to each data providing destination based on the transaction details included in the instruction. The transaction settlement unit 307 sums up the consideration of the transaction details for each data providing destination and calculates the consideration (total consideration) to be paid to each data providing destination. The transaction settlement unit 307 pays the calculated consideration to each data providing destination.

[0185] Note that the transaction settlement unit 307 notifies each data providing destination of the part related to each data providing destination among the provided consideration payment instructions received from the circulation control server 10. The transaction settlement unit 307 of the data providing destination pays the consideration to the users who have agreed to data provision based on the transaction details included in the notification. The transaction settlement unit 307 calculates the consideration to be paid to each user by multiplying the received provided consideration by the provided consideration distribution rate, and pays the calculated consideration to the users. Note that the provided consideration distribution rate will be described later.

[0186] When the transaction settlement unit 307 receives a bill regarding the PF usage fee from the management server 11, it pays the PF usage fee (accumulated PF usage fee, shared PF usage fee, provided PF usage fee) described in the bill to the information distribution business operator.

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

[0188] [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 request unit 303 of the data utilization server 30 only needs to present information to the user (such as a staff member of the data utilization business operator) and accept operations from the user. Specifically, the data distribution request unit 303 only needs to display a list of catalog information obtained from the transaction server 40 and send a provision request including the dataset name and search conditions of the catalog information selected by the user to the transaction server 40.

[0189] In addition, the transaction settlement unit 307 of the data utilization server 30 may pay a part of the consideration to be paid to the data provider to the transaction business operator.

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

[0191] 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. Also, the communication control unit 401 transmits data to the distribution control server 10. The communication control unit 401 delivers the data received from other devices to other processing modules. The communication control unit 401 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 401. The communication control unit 401 has a function as a receiving unit for receiving data from other devices and a function as a transmitting unit for transmitting data to other devices.

[0192] The account opening unit 402 is a means for opening an account for a user who wishes for data distribution by provision. The account opening unit 402 acquires a user ID from the user's terminal 50. The account opening unit 402 adds the acquired user ID to the account opener list (see Fig. 23).

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

[0194] When the catalog information request unit 403 receives a "catalog information presentation request" from the data utilization server 30, it transmits a "catalog information transmission request" to the distribution control server 10.

[0195] In response to transmitting the said request, the catalog information request unit 403 acquires the catalog information stored in the distribution control server 10. The catalog information request unit 403 selects the catalog information related to the service providers with which the own device is affiliated and transmits it to the data utilization business operator (data utilization server 30). Note that the catalog information request unit 403 selects the catalog information related to the affiliated service provider based on the business operator code of the affiliated service provider and the business operator code included in the catalog information.

[0196] The provision request processing unit 404 is a means for processing provision requests received from the data utilization server 30. The provision request processing unit 404 examines the search conditions included in the provision request. Specifically, the provision request processing unit 404 examines the consistency between the data utilization purpose of the data utilization business operator and the utilization purpose of the target data type. For example, if the content is "Utilization purpose: Development of new drugs, Data type: Disease name", the examination will pass. In other words, the data utilization business operator (data utilization server 30) also inputs the above utilization purpose and data type to the transaction server 40 at the time of requesting data provision.

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

[0198] The storage unit 405 stores information necessary for the operation of the transaction server 40. The storage unit 405 stores the business operator code of the partner service business operator.

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

[0200] 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. Also, the communication control unit 501 transmits data to the distribution control server 10. The communication control unit 501 delivers the data received from other devices to other processing modules. The communication control unit 501 transmits the data obtained from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 501. The communication control unit 501 has a function as a receiving unit for receiving data from other devices and a function as a transmitting unit for transmitting data to other devices.

[0201] The personal information input unit 502 is a means for inputting personal information to the circulation control server 10 when a user registers. The personal information input unit 502 inputs personal information (such as name, date of birth, contact information, account information, etc.) to the circulation control server 10 using any means. For example, the personal information input unit 502 acquires the above personal information from the user using a GUI and transmits the acquired personal information to the circulation control server 10.

[0202] The personal information input unit 502 stores the user ID issued by the circulation control server 10 in the storage unit 505.

[0203] The inquiry processing unit 503 is a means for processing inquiries received from the circulation control server 10 during data circulation by sharing or during data circulation by provision. The inquiry processing unit 503 acquires the intention of the user (agree or disagree to data circulation) using a GUI according to the content of the inquiry (data sharing, data provision). The inquiry processing unit 503 transmits a response including the intention of the user to the circulation control server 10.

[0204] The account information input unit 504 is a means for inputting information for opening an information account, which is necessary during data circulation by provision, to the transaction server 40. The account information input unit 504 transmits the user ID of the user to the transaction server 40.

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

[0206] [Hospital Terminal] Examples of the hospital terminal 60 include mobile terminal devices such as smartphones and tablets, and computers (personal computers, notebook computers). The hospital terminal 60 can be any device or apparatus as long as it can receive the operation of hospital staff and communicate with the circulation control server 10 or the like. Also, since the configuration of the hospital terminal 60 and the like are obvious to those skilled in the art, detailed description is omitted.

[0207] The hospital terminal 60 may transmit an ID linkage request to the distribution control server 10 according to the operation of hospital staff. In addition, the hospital terminal 60 also transmits the ID linkage 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 (entry in the customer information database) corresponding to the personal identification ID included in the ID linkage request.

[0208] [Management Server] FIG. 25 is a diagram showing an example of the processing configuration (processing modules) of the management server 11 according to the first embodiment. Referring to FIG. 25, the management server 11 includes a communication control unit 601, a transaction history control unit 602, a transaction settlement control unit 603, a burden ratio management unit 604, an information disclosure unit 605, and a storage unit 606.

[0209] The communication control unit 601 is a means for controlling communication with other devices. For example, the communication control unit 601 receives data (packets) from the service server 20. In addition, the communication control unit 601 transmits data to the service server 20. The communication control unit 601 delivers the data received from other devices to other processing modules. The communication control unit 601 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 601. The communication control unit 601 has a function as a receiving unit for receiving data from other devices and a function as a transmitting unit for transmitting data to other devices.

[0210] The transaction history control unit 602 is a means for controlling the history of transactions performed in the information distribution system. The transaction history control unit 602 stores the history information (data accumulation history, data sharing history, data provision history) received from the service server 20 in a database.

[0211] Specifically, the transaction history control unit 602 stores the data accumulation history in the accumulation history database, stores the data sharing history in the sharing history database, and stores the data provision history in the provision history database (see FIGS. 26, 27, and 28). At that time, the transaction history control unit 602 stores the business code of the source of the history information (data accumulator, data sharing source, data provision source) in each database.

[0212] The transaction settlement control unit 603 is a means for performing control related to the settlement of transactions occurring in the information circulation system. For example, the transaction settlement control unit 603 calculates the consideration received by each service provider at a predetermined timing (for example, the beginning of the month).

[0213] <Calculation of Accumulation Consideration> The transaction settlement control unit 603 refers to the accumulation history database and calculates the accumulation consideration for each entry belonging to the consideration payment target period (for example, one month). In the example of the first row shown in FIG. 26, the consideration for the hospital A to accumulate the "disease name" of the user corresponding to the personal identification ID "HL11" is calculated. The transaction settlement control unit 603 calculates the consideration for each data accumulator by summing up the considerations calculated for each entry in the consideration payment target period (for example, one month) for each data accumulator.

[0214] The consideration for data accumulation is calculated by Equation (1). As shown in Equation (1), the accumulation consideration is determined by the accumulation price of the data set and the number of new transactions. Also, "i" is an index indicating the data set. "j" is an index indicating the user involved in the accumulation.

[0215]

Equation

[0216] The transaction settlement control unit 603 calculates the accumulated price according to the calculation formula shown in the following formula (2). As shown in formula (2), the accumulated price is determined by the data price, the sharing demand coefficient, and the offering demand coefficient. The sharing demand coefficient and the offering demand coefficient are coefficients indicating the strength of demand for sharing and offering, respectively. Usually, the demand for "disease name" is often stronger than that for "weight" or "height", and the sharing demand coefficient and the offering demand coefficient for "disease name" are set higher than the coefficients such as "weight".

[0217]

Number

[0218] The transaction settlement control unit 603 calculates the data price according to the calculation formula shown in the following formula (3). As shown in formula (3), the data price is determined by the evaluation amount of the data set and the holding source coefficient. The holding source coefficient is a parameter that the service provider accumulating the data can freely determine. Each service provider sets the holding source coefficient in consideration of its own concept of "accumulation". The holding source count is notified from each service provider to the information distribution business operator (management server 11).

[0219]

Number

[0220] The transaction settlement control unit 603 calculates the evaluation amount according to the calculation formula shown in the following formula (4). As shown in formula (4), the evaluation amount is determined by the reference price and the accuracy coefficient. The reference price is determined by the information distribution operator with reference to the difficulty level, management cost, etc. when generating the data set. For example, since the diagnosis of a disease is more difficult than the measurement of weight, height, etc., the reference price of "disease name" is set higher than the reference price of "weight" etc. The accuracy coefficient is determined by the accuracy of each data compared with other data sets within the same category. For example, in various measurement data such as "weight", "height", "blood pressure", "heart rate", etc., the accuracy coefficient is determined by the accuracy of each data. For example, since "blood pressure" is greatly affected by the situation at the time of measurement, the accuracy coefficient is set low. Note that "I" in formula (4) is an index indicating the category.

[0221]

Number

[0222] In this way, the accumulated consideration is calculated according to the parameters determined by the information distribution operator and the parameters determined by the service provider.

[0223] <Calculation of sharing consideration> The transaction settlement control unit 603 refers to the sharing history database and calculates the sharing consideration for each entry belonging to the consideration payment target period (for example, one month). The transaction settlement control unit 603 calculates the consideration for each data sharing source by summing up the consideration calculated for each entry in the consideration payment target period for each data sharing source.

[0224] The sharing consideration is calculated according to the calculation formulas shown in the following formulas (5) and (6). Formula (5) shows the consideration obtained by sharing, and formula (6) shows the consideration to be paid by sharing. As shown in formulas (5) and (6), the sharing consideration is determined by the sharing price and the number of transactions. Note that "k" is an index indicating the trading partner of data circulation.

[0225]

Number

[0226]

Number

[0227] The transaction settlement control unit 603 calculates the sharing price according to the calculation formula shown in the following formula (7). As shown in formula (7), the sharing price is determined by the data price, the sharing demand coefficient, and the sharing source coefficient. Among these three parameters, the sharing source coefficient is a parameter that the data sharing source (the service provider that holds the accumulated data) can freely determine. For example, a data sharing source that wants to keep the sharing price low and achieve many transactions sets the sharing source coefficient low. The service provider determines the sharing source coefficient and notifies the information distribution provider.

[0228]

Number

[0229] <Calculation of Consideration for Provision> The transaction settlement control unit 603 refers to the provision history database and calculates the consideration for each entry belonging to the consideration payment target period (for example, one month). The transaction settlement control unit 603 calculates the consideration for each data provider by summing up the consideration calculated for each entry in the consideration payment target period for each data provider.

[0230] The consideration for provision is calculated according to the calculation formulas shown in the following formulas (8) and (9). Formula (8) shows the consideration obtained by provision, and formula (9) shows the consideration paid by provision. As shown in formulas (8) and (9), the consideration for provision is determined by the provision price and the number of transactions.

[0231]

Number

[0232]

Number

[0233] The transaction settlement control unit 603 calculates the offering price according to the calculation formula shown in the following formula (10). As shown in formula (10), the offering price is determined by the data price, the offering demand coefficient, and the offering source coefficient. Among these three parameters, the offering source coefficient is a parameter that the data provider (service provider that holds the accumulated data) can freely determine. The service provider determines the offering source coefficient and notifies the information distribution operator of it.

[0234]

Number

[0235] The transaction settlement control unit 603 creates a payment statement regarding the consideration paid from the information distribution operator to the service provider for each service provider's accumulation. The transaction settlement control unit 603 creates a payment statement (accumulation consideration payment statement) that includes the consideration for each transaction of data accumulation, for example, as shown in FIG. 29.

[0236] Note that as described above, when data accumulation is performed, consideration is distributed to the users who participated in the data accumulation. The transaction settlement control unit 603 describes the distribution rate of the consideration (accumulation consideration distribution rate) in the payment statement. FIG. 29 shows an example in which 10% of the accumulation consideration paid from the information distribution operator to Hospital A is distributed to the users.

[0237] In addition, the transaction settlement control unit 603 creates a payment instruction (sharing consideration payment instruction) for the consideration that each service provider pays to other service providers regarding data sharing for each service provider. For example, the transaction settlement control unit 603 creates a payment instruction as shown in FIG. 30.

[0238] Similarly, for each service provider, the transaction settlement control unit 603 creates a payment instruction form (provision consideration payment instruction form) for the consideration that the service provider pays to other service providers for data provision. For example, the transaction settlement control unit 603 creates a payment instruction form as shown in FIG. 31.

[0239] As described above, when data provision is performed, consideration is distributed to the users involved in the data provision. The transaction settlement control unit 603 describes the distribution rate of the consideration (provision consideration distribution rate) in the payment instruction form. FIG. 31 shows an example in which 20% of the provision consideration paid from the pharmaceutical company to the hospital is distributed to the users.

[0240] The transaction settlement control unit 603 transmits the generated accumulated consideration payment statement and payment instruction forms (shared consideration payment instruction form, provision consideration payment instruction form) to the service servers 20 of each service provider and the data utilization servers 30 of each data utilization business operator.

[0241] In this way, the transaction history control unit 602 acquires the data accumulation history regarding the data accumulation transaction from the data accumulator. Also, the transaction settlement control unit 603 calculates the accumulated consideration to be paid to the data accumulator based on the data accumulation history, and pays the calculated accumulated consideration to the data accumulator.

[0242] <Billing of PF Usage Fees> The transaction settlement control unit 603 is a means for billing each service provider for the payment of PF usage fees. The transaction settlement control unit 603 calculates the PF utilization rate for each data accumulator, data sharing destination, and data provision destination during a predetermined period (consideration payment target period; for example, one month).

[0243] For example, when Hospital A is a data accumulator and a data sharing destination, accumulated PF usage fees and shared PF usage fees are billed to Hospital A. Also, when Pharmaceutical Company C does not accumulate data and is only limited to the use of data provision, provision PF usage fees are billed to Pharmaceutical Company C.

[0244] The transaction settlement control unit 603 calculates the storage PF usage fees for each data accumulator according to the calculation formula shown in the following formula (11). Note that the PF cost is the cost such as labor costs and equipment costs required to operate the information circulation system. Also, as described above, the storage burden ratio, the sharing burden ratio, and the provision burden ratio are values that have already been determined at the time of calculating the PF usage fee.

[0245]

Number

[0246] In formula (11), the total number of accumulations is the total number of data accumulations generated during a predetermined period (for example, one month). For example, if 1000 accumulations occur during the above-mentioned predetermined period and 10 of them are accumulations of Hospital A, 1% of the amount obtained by multiplying the PF cost by the storage burden ratio will be the storage PF usage fee of Hospital A.

[0247] The transaction settlement control unit 603 calculates the sharing PF usage fees for the data sharing destination according to the calculation formula shown in the following formula (12).

[0248]

Number

[0249] The transaction settlement control unit 603 calculates the provision PF usage fees for the data provision source according to the calculation formula shown in the following formula (13).

[0250]

Number

[0251] In this way, the transaction settlement control unit 603 calculates the PF usage fees to be billed to the service providers (each actor) by using the "storage", "sharing", and "provision" burden ratios for the operation cost of the information circulation system. The transaction settlement control unit 603 bills the calculated PF usage fees to each service provider and data utilization business operator (issues a PF usage fee invoice).

[0252] For example, in the above example, since Hospital A is a data accumulator and a data sharing destination, the transaction settlement control unit 603 bills Hospital A for the accumulated PF usage fee and the shared PF usage fee. Similarly, the transaction settlement control unit 603 bills Pharmaceutical Company C for the provided PF usage fee.

[0253] <Generation of Income and Expense Management Document> Based on the generated accumulated consideration payment details, shared consideration payment instructions, and provided consideration payment instructions, the transaction settlement control unit 603 generates an income and expense management document indicating the income and expenses of each actor. Specifically, for each actor, the transaction settlement control unit 603 stores the income and expenses for each predetermined period (consideration payment target period) in the income and expense management database (see FIG. 32). The income and expense management database shown in FIG. 32 is an example and is not intended to limit the items to be stored.

[0254] Regarding the income and expenses of accumulation, the transaction settlement control unit 603 calculates the accumulated income based on the accumulated consideration paid to the service provider and the accumulated consideration distribution rate. The portion of the accumulated consideration paid to the service provider that is distributed to the service provider becomes the "accumulated income". Also, the accumulated expense is the PF usage fee (accumulated PF usage fee) that the service provider pays to the information circulation provider.

[0255] Regarding the income and expenses of sharing, the transaction settlement control unit 603 calculates the consideration paid to the service provider as the "shared income". Also, the transaction settlement control unit 603 calculates the combined value of the consideration paid to other service providers and the PF usage fee (shared PF usage fee) paid to the information circulation provider as the "shared expense" of the service provider.

[0256] Regarding the income and expenses of provision, the transaction settlement control unit 603 calculates the provided income based on the provided consideration paid to the service provider and the provided consideration distribution rate. The portion of the provided consideration paid to the service provider that is distributed to the service provider becomes the "provided income". Also, the transaction settlement control unit 603 calculates the combined value of the consideration paid to other service providers and the PF usage fee (provided PF usage fee) paid to the information circulation provider as the "provided expense" of the service provider.

[0257] <Calculation of Burden Ratio> The burden ratio management unit 604 is a means for managing the burden ratio related to the calculation of PF usage fees. The burden ratio management unit 604 calculates the burden ratios (accumulated burden ratio, shared burden ratio, provided burden ratio) based on the revenue and expenditure of each service provider. The calculation of the said burden ratio is performed every predetermined period (burden ratio review period; for example, 6 months, 1 year).

[0258] Specifically, the burden ratio management unit 604 re-determines each of the above-mentioned burden ratios after the expiration of the above-mentioned burden ratio review period. That is, the burden ratio management unit 604 recalculates the burden ratios to be applied in the next period (the next 6 months, 1 year) every predetermined period (for example, every 6 months, 1 year).

[0259] At that time, the burden ratio management unit 604 calculates the burden ratio so as to improve the profit of the entire information circulation system. For example, since the source of profit in the information circulation system lies in the accumulated data, the burden ratio management unit 604 calculates the burden ratio so as to give preferential treatment to the data accumulator (for example, lower the accumulated burden ratio).

[0260] For example, the burden ratio management unit 604 applies candidates for new burden ratios to the current period's performance (the accumulated, shared, and provided performance of each actor) to calculate the revenue and expenditure of each actor (the total of the revenue and expenditure of accumulation, sharing, and provision respectively). Then, the burden ratio management unit 604 selects a burden ratio such that the revenue and expenditure of as many actors as possible are in the black, and determines the three burden ratios to be applied in the next period.

[0261] At that time, if it is not possible to make the revenue and expenditure of all actors in the black, the burden ratio management unit 604 selects an accumulated burden ratio that gives preferential treatment to the data accumulator. In this case, when one service provider becomes multiple entities such as a data accumulator, a data sharing destination, and a data providing destination, the burden ratio management unit 604 calculates the burden ratio so that the revenue and expenditure of the service provider as the data accumulator are in the black.

[0262] For example, when Hospital A is both a data accumulator and a data sharing destination, the burden ratio management unit 604 determines the accumulation burden ratio so that the revenue and expenditure related to the data accumulation of Hospital A is in the black. That is, the burden ratio management unit 604 calculates the revenue and expenditure of the data accumulator by subtracting the accumulation PF usage fee from the accumulation consideration paid to the data accumulator. Furthermore, the burden ratio management unit 604 recalculates the accumulation burden ratio so that the revenue and expenditure of the data accumulator is in the black.

[0263] Note that if the data accumulator is given preferential treatment, usually the accumulation burden ratio will be lower than other burden ratios, and the sharing burden ratio and the provision burden ratio will be higher. If the accumulation burden ratio decreases, the revenue and expenditure related to the data sharing of Hospital A will deteriorate, and it is also assumed that the overall revenue and expenditure will be negative. However, it is highly likely that Hospital A is increasing its profits by leveraging data sharing, and such deterioration of revenue and expenditure is acceptable.

[0264] Alternatively, the burden ratio management unit 604 selects a provision burden ratio such that the data utilization business operator that utilizes the accumulated data bears more burden. As the provision burden ratio increases, other burden ratios (accumulation burden ratio, sharing burden ratio) decrease.

[0265] <Information Disclosure> The information disclosure unit 605 is a means for disclosing various information related to the operation of the information circulation system. For example, the information disclosure unit 605 discloses the above three determined burden ratios (accumulation burden ratio, sharing burden ratio, provision burden ratio) to each actor (service provider, data utilization business operator). Specifically, the information disclosure unit 605 transmits the three burden ratios to the service server 20 and the data utilization server 30.

[0266] Each actor considers the cost burden using the disclosed burden ratio and considers strategies for the next period (next term), etc.

[0267] In addition, the information disclosure department 605 may disclose parameters (such as sharing demand coefficients, provision demand coefficients, etc.) for determining the consideration for data accumulation, data sharing, and data provision respectively. Each actor may consider data trading strategies and the like using the disclosed data. For example, an actor may refer to the data sets and transaction amounts provided by other companies and handle similar data sets in its own company or determine the prices (holding source coefficients, sharing source coefficients, provision source coefficients) of existing data sets.

[0268] The storage unit 606 stores information necessary for the operation of the management server 11.

[0269] The operation of the management server 11 according to the first embodiment will be described with reference to a flowchart. FIG. 33 is a flowchart showing an example of the operation of the management server 11 according to the first embodiment.

[0270] The management server 11 receives a transaction history from a service provider (step S101).

[0271] The management server 11 calculates the consideration to be paid to each service provider at a predetermined timing (step S102).

[0272] The management server 11 calculates the PF usage fee to be billed to the service provider and the data utilization business operator (step S103).

[0273] The management server 11 issues invoices (payment details, payment instructions, invoices, etc.) to the service provider and the data utilization business operator (step S104).

[0274] The management server 11 recalculates the burden ratio at regular intervals or at a predetermined timing (step S105).

[0275] The management server 11 discloses the recalculated burden ratio (step S106).

[0276] As described above, in the information circulation system according to the first embodiment, each actor reports the transaction history in a predetermined period (for example, one month) to the information circulation operator, which is the platform operation organization. Based on the acquired history, the information circulation operator calculates the PF usage fees for each type of transaction form (accumulation, sharing, and provision) of each actor. In addition, the information circulation operator calculates the income and expenditure of each actor. The information circulation operator calculates the burden ratios for accumulation, sharing, and provision, respectively, considering the income and expenditure of each actor so that the operation cost burden of the information circulation system is equal. More specifically, the information circulation operator determines the platform usage fees so that the operation costs required for the operation of the information circulation system are shared among the three parties: the data accumulator, the data sharing destination, and the data providing destination, and bills these three parties for the payment of the usage fees. By dividing the operation costs into the three usage fees, the information circulation operator can control the income and expenditure of each actor to a certain extent. For example, in the information circulation system, data sharing and data provision do not occur if there is no accumulated data. Therefore, the information circulation operator determines the accumulation platform usage fees to give preferential treatment to the data accumulator. The data accumulator with preferential usage fees will accumulate more data and be able to supply more data to the data sharing destination and the data providing destination. With a large amount of accumulated data registered in the information circulation system, data circulation becomes active, and the data sharing destination and the data providing destination can provide better services to users using the data obtained through data circulation. As a result, a sustainable information circulation system is constructed.

[0277] Subsequently, the hardware of each device constituting the information circulation system will be described. FIG. 34 is a diagram showing an example of the hardware configuration of the management server 11.

[0278] The management server 11 can be configured by an information processing device (so-called computer) and has the configuration illustrated in FIG. 34. For example, the management server 11 includes a processor 311, a memory 312, an input / output interface 313, a communication interface 314, and the like. The components such as the above-mentioned processor 311 are connected by an internal bus or the like and are configured to be communicable with each other.

[0279] However, the configuration shown in FIG. 34 is not intended to limit the hardware configuration of the management server 11. The management server 11 may include hardware not shown, and may not be provided with the input / output interface 313 as necessary. Also, the number of processors 311 and the like included in the management server 11 is not intended to be limited to the example shown in FIG. 34. For example, a plurality of processors 311 may be included in the management server 11.

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

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

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

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

[0284] The functions of the management server 11 are realized by various processing modules. The processing modules are 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 embodied as a computer program product. Further, the above program can be downloaded via a network or updated using a storage medium storing the program. Furthermore, the above processing module may be realized by a semiconductor chip.

[0285] Note that the distribution control server 10, the service server 20, etc. can also be configured by an information processing apparatus in the same manner as the management server 11, and the basic hardware configuration is not different from that of the management server 11, so the description thereof is omitted.

[0286] The management server 11, which is an information processing apparatus, is equipped with a computer, and the functions of the management server 11 can be realized by causing the computer to execute a program. Further, the management server 11 executes a control method of the management server 11 according to the program.

[0287] [Modification Example] Note that the configuration, operation, etc. of the information distribution system described in the above embodiment are examples and are not intended to limit the configuration of the system.

[0288] In the above embodiment, it has been described that the data sharing source and the data providing source transmit the transaction history to the management server 11, and the management server 11 calculates a consideration (sharing consideration, accumulation consideration) based on the history. However, the data sharing destination and the data providing destination may also transmit the transaction history to the management server 11. The management server 11 may check the consistency regarding the transaction history of each of the data sharing destination and the data sharing source, and calculate a consideration for the transactions that are consistent.

[0289] In the above embodiment, the configuration in which the information distribution operator includes the distribution control server 10 and the management server 11 has been described. However, the operations of the information distribution operator may be performed by a single server device. Specifically, the distribution control server 10 may include the functions of the management server 11, or the management server 11 may include the functions of the distribution control server 10.

[0290] In the above embodiment, the case where the user information database is configured inside the distribution control server 10 has been described. However, the database may be constructed 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, as long as the "data distribution control unit (data distribution control means)" or the like described above is implemented in any of the devices included in the system.

[0291] The form of data transmission and reception between each device (distribution control server 10, management server 11, service server 20, etc.) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Between these devices, personal information of users and the like are transmitted and received, and in order to appropriately protect these information, it is desirable that encrypted data be transmitted and received.

[0292] In the flowcharts (flowcharts, sequence diagrams) used in the above description, a plurality of steps (processes) are described in order, but the execution order of the steps executed in the embodiment is not limited to the described order. In the embodiment, for example, each process can be executed in parallel, and the order of the illustrated steps can be changed within a range that does not affect the content.

[0293] The above-described embodiments have been described in detail for ease of understanding of the disclosure of the present application, and it is not intended that all the configurations described above are necessary. Also, when multiple 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 one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace other configurations for a part of the configuration of one embodiment.

[0294] From the above description, the industrial applicability of the present invention is clear, but the present invention is suitably applicable to an information distribution system that distributes accumulated data related to services provided to users, etc.

[0295] Some or all of the above-described embodiments may be described as follows in the following supplementary notes, but are not limited thereto. [Supplementary Note 1] A distribution control server that controls data accumulation for making data related to services provided from a data accumulator to a user the target of data distribution, controls data sharing for a data sharing destination to acquire the accumulated data, and controls data provision for a data providing source to acquire the accumulated data, and A management server that bills the data accumulator for an accumulation platform usage fee related to the data accumulation, bills the data sharing destination for a sharing platform usage fee related to the data sharing, and bills the data providing source for a provision platform usage fee related to the data provision, A system including the above. [Supplementary Note 2] The management server calculates the accumulation platform usage fee based on the number of times the data accumulator has performed the data accumulation and an accumulation burden ratio that determines the burden ratio of the data accumulation, calculates the sharing platform usage fee based on the number of times the data sharing destination has performed the data sharing and a sharing burden ratio that determines the burden ratio of the data sharing, The system according to Appendix 1, wherein the sharing platform usage fee is calculated based on the number of times the data provider has provided the data and the provision burden ratio that determines the burden ratio of the data provision. [Appendix 3] The management server The system according to Appendix 2, wherein the management server determines the storage burden ratio, the sharing burden ratio, and the provision burden ratio based on the respective revenues and expenditures of the data accumulator, the data sharer, and the data provider. [Appendix 4] The management server The system according to Appendix 3, wherein the management server determines the storage burden ratio, the sharing burden ratio, and the provision burden ratio so as to give preferential treatment to the data accumulator. [Appendix 5] The management server The system according to Appendix 4, wherein the management server acquires a data storage history regarding the data storage transaction from the data accumulator, calculates a storage consideration to be paid to the data accumulator based on the data storage history, and pays the calculated storage consideration to the data accumulator. [Appendix 6] The system according to Appendix 5, wherein the management server calculates the revenue and expenditure of the data accumulator by subtracting the storage platform usage fee from the storage consideration paid to the data accumulator. [Appendix 7] The system according to Appendix 6, wherein the management server determines the storage burden ratio so that the revenue and expenditure of the data accumulator is in the black. [Appendix 8] The system according to any one of Appendices 2 to 7, wherein the management server periodically recalculates the storage burden ratio, the sharing burden ratio, and the provision burden ratio. [Appendix 9] The system according to Appendix 8, wherein the management server discloses the recalculated storage burden ratio, sharing burden ratio, and provision burden ratio to the data accumulator, the data sharer, and the data provider. [Appendix 10] Obtain a data storage history related to data storage for making data related to services provided from a data accumulator to a user the target of data circulation, obtain a data sharing history related to data sharing for a data sharing destination to obtain the stored data, and obtain a data provision history related to data provision for a data provision destination to obtain the stored data, a transaction history control unit; Calculate an accumulation platform usage fee related to the data storage based on the data storage history and bill the calculated accumulation platform usage fee to the data accumulator, calculate a sharing platform usage fee related to the data sharing based on the data sharing history and bill the calculated sharing platform usage fee to the data sharing destination, and calculate a provision platform usage fee related to the data provision based on the data provision history and bill the calculated provision platform usage fee to the data provision destination, a transaction settlement control unit; A management server comprising the above. [Appendix 11] In a management server, Obtain a data storage history related to data storage for making data related to services provided from a data accumulator to a user the target of data circulation, Obtain a data sharing history related to data sharing for a data sharing destination to obtain the stored data, Obtain a data provision history related to data provision for a data provision destination to obtain the stored data, Calculate an accumulation platform usage fee related to the data storage based on the data storage history and bill the calculated accumulation platform usage fee to the data accumulator, Calculate a sharing platform usage fee related to the data sharing based on the data sharing history and bill the calculated sharing platform usage fee to the data sharing destination, Calculate a provision platform usage fee related to the data provision based on the data provision history and bill the calculated provision platform usage fee to the data provision destination, a control method of the management server. [Appendix 12] A computer installed in a management server, obtains a data storage history regarding data storage for making data related to a service provided from a data accumulator to a user be an object of data circulation, obtains a data sharing history regarding data sharing for a data sharing destination to obtain the stored data, and obtains a data provision history regarding data provision for a data provision source to obtain the stored data; and calculates an accumulation platform usage fee regarding the data storage based on the data storage history and bills the data accumulator for the calculated accumulation platform usage fee, calculates a sharing platform usage fee regarding the data sharing based on the data sharing history and bills the data sharing destination for the calculated sharing platform usage fee, and calculates a provision platform usage fee regarding the data provision based on the data provision history and bills the data provision source for the calculated provision platform usage fee; and A computer-readable storage medium storing a program for executing the above.

[0296] Note that each disclosure of the above-cited prior art documents is incorporated herein by reference. As described above, embodiments of the present invention have been described, but the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications can be made without departing from the scope and spirit of the present invention. That is, the present invention naturally includes all disclosures including the claims, various modifications and corrections that can be made by those skilled in the art according to the technical idea.

Explanation of Signs

[0297] 10 Circulation control server 11 Management server 20 Service server 20-1 Service server 20-2 Service server 30 Data utilization server 40 Transaction server 50 terminals 60 hospital terminals 70-1 service providers 70-2 service providers 70-3 service providers 70-4 service providers 71 information distribution providers 72 data utilization providers 101 distribution control server 102 management server 201 communication control unit 202 user registration unit 203 ID linkage unit 204 location information management unit 205 data distribution control unit 206 catalog information management unit 207 memory unit 301 communication control unit 302 ID linkage control unit 303 data distribution request unit 304 data storage control unit 305 data distribution unit 306 transaction history reporting unit 307 transaction settlement unit 308 memory 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 memory unit 501 communication control unit 502 personal information input unit 503 inquiry processing unit 504 account information input unit 505 memory unit 601 communication control unit 602 transaction history control unit 603 transaction settlement control unit 604 burden ratio management unit 605 Information Disclosure Department 606 Memory Department

Claims

A distribution control server that realizes a platform for a data distribution system in which data accumulation, data sharing, and data provision are performed by controlling data accumulation for making data related to services provided by a first service provider to a user subject to data distribution, controlling data sharing for a second service provider to obtain data accumulated by the first service provider in order to provide services to the user, and controlling data provision for a third service provider to obtain data accumulated by the first service provider for use in its own business, and A first server that is managed by the first service provider and, each time it stores data generated by providing services to the user, transmits the type of data generated by providing services to the user and location information including the user's ID to the distribution control server, A second server that is managed by the second service provider and transmits a sharing request including the user's ID and the type of data desired to be obtained by the data sharing to the distribution control server, A third server that is managed by the third service provider and transmits a provision request including search conditions required for the data provided by the data provision to the distribution control server, A management server that bills the first service provider for the accumulation platform usage fee related to the data accumulation, bills the second service provider for the sharing platform usage fee related to the data sharing, and bills the third service provider for the provision platform usage fee related to the data provision, including When receiving the location information, the distribution control server realizes the data accumulation by associating the user's ID with the type of the data included in the location information and storing them in a database, When the distribution control server receives the sharing request, it searches the database, reads out the type of data corresponding to the ID of the user included in the sharing request, and when consent from the user for the data of the type read out to be transmitted from the first server to the second server is obtained, it transmits a sharing instruction including the ID of the user and the type of data read out to the first server. The first server transmits to the second server the data that is stored in association with the ID of the user included in the sharing instruction and that corresponds to the type of data included in the sharing instruction. When the distribution control server receives the provision request, it searches the database to identify the ID of the user corresponding to the type of data that matches the search condition, and when consent from the user for the data of the type included in the provision request to be transmitted from the first server to the third server is obtained, it transmits a provision instruction including the type of data and the ID of the user read out to the first server. The first server transmits to the third server the data that is stored in association with the ID of the user included in the provision instruction and that corresponds to the type of data included in the provision instruction. The first server transmits to the management server a first transaction history including the number of times the location information has been transmitted during a predetermined period as the accumulated number of times. The second server transmits to the management server a second transaction history including the number of times the sharing request has been transmitted during the predetermined period as the number of sharing times. The third server transmits to the management server a third transaction history including the number of times the provision request has been transmitted during the predetermined period as the number of provision times. The management server Calculate the storage platform usage fee by multiplying the platform cost, which is the cost required to operate the platform, by the burden ratio of the data storage and the number of stored items, and send a first payment instruction including the calculated storage platform usage fee to the first server. Calculate the sharing platform usage fee by multiplying the platform cost, the burden ratio of the data sharing, and the number of shared items, and send a second payment instruction including the calculated sharing platform usage fee to the second server. Calculate the provision platform usage fee by multiplying the platform cost, the burden ratio of the data provision, and the number of provided items, and send a third payment instruction including the calculated provision platform usage fee to the third server. A system in which the sum of the burden ratio of the data storage, the burden ratio of the data sharing, and the burden ratio of the data provision is 1.

Images